Skip to content
  1. Jan 10, 2018
    • tzapu's avatar
      added a new RPC call trace_replayBlockTransactions (#7366) · df5d27d5
      tzapu authored
      * intial add trace_replayBlockTransactions
      
      * cleanup timing calls
      add execution proof
      
      * WIP implementing changes
      
      * fix for trace_replayBlockTransactions rpc call
      
      * cleanup comments
      
      * cleanup, proof,
      can't workout lifetime issues yet
      
      * Fix lifetimes issue.
      
      * naive rpc test
      
      * updated docs
      df5d27d5
  2. Jan 09, 2018
  3. Jan 08, 2018
  4. Jan 05, 2018
    • Afri Schoedon's avatar
      Expanse Byzantium update w/ correct metropolis difficulty increment divisor (#7463) · 36e230ee
      Afri Schoedon authored
      * Byzantium Update for Expanse
      
      Here the changes go. Hope I didnt miss anything.
      
      * expip2 changes - update duration limit
      
      * Fix missing EXPIP-2 fields
      
      * Format numbers as hex
      
      * Fix compilation errors
      
      * Group expanse chain spec fields together
      
      * Set metropolisDifficultyIncrementDivisor for Expanse
      
      * Revert #7437
      
      * Add Expanse block 900_000 hash checkpoint
      36e230ee
  5. Jan 03, 2018
    • 5chdn's avatar
      Remove expanse from available chains · 27d8befb
      5chdn authored
      27d8befb
    • André Silva's avatar
      Upgrade to RocksDB 5.8.8 and tune settings to reduce space amplification (#7348) · e114b0b2
      André Silva authored
      * kvdb-rocksdb: update to RocksDB 5.8.8
      
      * kvdb-rocksdb: tune RocksDB options
      
      * Switch to level-style compaction
      * Increase default block size (16K), and use bigger blocks for HDDs (64K)
      * Increase default file size base (64MB SSDs, 256MB HDDs)
      * Create a single block cache shared across all column families
      * Tune compaction settings using RocksDB helper functions, taking into account
        memory budget spread across all columns
      * Configure backgrounds jobs based on the number of CPUs
      * Set some default recommended settings
      
      * ethcore: remove unused config blockchain.db_cache_size
      
      * parity: increase default value for db_cache_size
      
      * kvdb-rocksdb: enable compression on all levels
      
      * kvdb-rocksdb: set global db_write_bufer_size
      
      * kvdb-rocksdb: reduce db_write_bufer_size to force earlier flushing
      
      * kvdb-rocksdb: use master branch for rust-rocksdb dependency
      e114b0b2
  6. Jan 02, 2018
  7. Dec 29, 2017
  8. Dec 26, 2017
    • Nicolas Ochem's avatar
      Fix #6209 - introduce standalone dir crate · 2e12a2db
      Nicolas Ochem authored
      * created the dir crate in util
      * moved code from ethstore/src/dir/paths.rs to dir crate
      * rename dir module in ethstore to accounts_dir to distinguish it
        from the dir crate
      * changes after @tomusdrw on #6952
      2e12a2db
  9. Dec 22, 2017
  10. Dec 21, 2017
    • Vlad Lupashevskyi's avatar
    • Tomasz Drwięga's avatar
      Don't check max. · d6f160e8
      Tomasz Drwięga authored
      d6f160e8
    • Tomasz Drwięga's avatar
      7d4e4c7a
    • Yurii Rashkovskii's avatar
      Problem: AuRa's unsafeties around step duration (#7282) · d5b81ead
      Yurii Rashkovskii authored
      Firstly, `Step.duration_remaining` casts it to u32, unnecesarily
      limiting it to 2^32. While theoretically this is "good enough" (at 3
      seconds steps it provides room for a little over 400 years), it is
      still a lossy way to calculate the remaining time until the next step.
      
      Secondly, step duration might be zero, triggering division by zero
      in `Step.calibrate`
      
      Solution: rework the code around the fact that duration is
      typically in single digits and never grows, hence, it can be represented
      by a much narrower range (u16) and this highlights the fact that
      multiplying u64 by u16 will only result in an overflow in even further
      future, at which point we should panic informatively (if anybody's
      still around)
      
      Similarly, panic when it is detected that incrementing the step
      counter wrapped around on the overflow of usize.
      
      As for the division by zero, prevent it by making zero an invalid
      value for step duration. This will make AuRa log the constraint
      mismatch and panic (after all, what purpose would zero step duration
      serve? it makes no sense within the definition of the protocol,
      as finality can only be achieved as per the specification
      if messages are received within the step duration, which would violate
      the speed of light and other physical laws in this case).
      d5b81ead
    • NikVolf's avatar
      ok_or -> ok_or_else · 516725ab
      NikVolf authored
      516725ab
    • Tomasz Drwięga's avatar
      Get rid of clippy remainings. · 00883e47
      Tomasz Drwięga authored
      00883e47
  11. Dec 15, 2017
  12. Dec 08, 2017
  13. Dec 07, 2017
  14. Dec 06, 2017
  15. Dec 05, 2017
  16. Dec 01, 2017
  17. Nov 24, 2017
  18. Nov 16, 2017
  19. Nov 10, 2017
  20. Nov 09, 2017
  21. Nov 07, 2017
  22. Nov 03, 2017
  23. Nov 02, 2017
  24. Nov 01, 2017