Skip to content
Snippets Groups Projects
Select Git revision
  • 49d092c4d4f2c223137ab14c1af98337e2facbc0
  • master default protected
  • 3-regression-l-onglet-network-reste-vide
  • v1.7.5 protected
  • v1.7.4 protected
  • v1.7.3 protected
  • v1.7.2 protected
  • v1.7.1 protected
  • v1.7.0 protected
  • v1.6.31 protected
  • v1.6.30 protected
  • v1.6.29 protected
  • v1.6.28 protected
  • v1.6.27 protected
  • v1.6.26 protected
  • v1.6.25 protected
  • v1.6.24 protected
  • v1.6.23 protected
  • v1.6.22 protected
  • v1.6.21 protected
  • v1.6.20 protected
  • v1.6.19 protected
  • v1.6.18 protected
23 results

release.sh

Blame
  • 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 --exectuion=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 --exectuion=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.