Skip to content
Snippets Groups Projects
Select Git revision
  • master
  • Vivakvo-master-patch-80805
  • patch-26
  • patch-19
  • patch-25
  • patch-24
  • patch-23
  • patch-22
  • patch-21
  • patch-18
  • patch-17
  • Vivakvo-master-patch-99327
  • patch-16
  • patch-15
  • patch-14
  • patch-13
  • patch-12
  • patch-11
  • patch-10
  • patch-9
  • v1.4.1
  • v1.4.0
  • v1.3.11
  • v1.3.10
  • v1.3.9
  • v1.3.8
  • v1.3.7
  • v1.3.6
  • v1.3.5
  • v1.3.4
  • v1.3.3
  • v1.3.2
  • v1.3.1
  • v1.3.0
  • v1.2.10
  • v1.2.9
  • v1.2.8
  • v1.2.7
  • v1.2.6
  • v1.2.5
40 results

README.md

Blame
  • Forked from clients / Cesium-grp / Cesium
    Source project has a limited visibility.
    replay-block.md 1007 B

    How to replay a block

    You can use try-runtime subcommand to replay a block against a real state from a live network.

    1. Checkout the git tag of the runtime version at the block you want to replay
    2. Build duniter with feature try-runtime: cargo build --features try-runtime
    3. Find the hash of the block to replay
    4. Choose an RPC endpoint without path (try-runtime not support path)
    5. Replay the block a first time to get the state:
    duniter try-runtime --execution=Native execute-block --block-at 0x2633026e3e428b010cfe08d215b6253843a9fe54db28748ca56de37e6a83c644 live -s tmp/snapshot1 -u ws://localhost:9944
    1. Then, replay the block as many times as you need against your local snapshot:
    duniter try-runtime --execution=Native execute-block --block-at 0x2633026e3e428b010cfe08d215b6253843a9fe54db28748ca56de37e6a83c644 --block-ws-uri ws://localhost:9944 snap -s tmp/snapshot1

    try-runtime does not allow (for now) to store the block locally, only the storage can be stored.