Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • update-docker-compose-rpc-squid-names
  • network/gdev-800 protected
  • fix-252
  • 1000i100-test
  • hugo/tmp-0.9.1
  • hugo/distance-pool-index
  • network/gdev-803 protected
  • hugo/endpoint-gossip
  • network/gdev-802 protected
  • hugo/distance-precompute
  • network/gdev-900 protected
  • tuxmain/anonymous-tx
  • debug/podman
  • hugo/195-doc
  • hugo/195-graphql-schema
  • hugo-tmp-dockerfile-cache
  • release/client-800.2 protected
  • release/runtime-800 protected
  • feature/show_milestone
  • gdev-900-0.10.0 protected
  • gdev-900-0.9.2 protected
  • gdev-800-0.8.0 protected
  • gdev-900-0.9.1 protected
  • gdev-900-0.9.0 protected
  • gdev-803 protected
  • gdev-802 protected
  • runtime-801 protected
  • gdev-800 protected
  • runtime-800-bis protected
  • runtime-800 protected
  • runtime-800-backup protected
  • runtime-701 protected
  • runtime-700 protected
  • runtime-600 protected
  • runtime-500 protected
  • v0.4.1 protected
  • runtime-401 protected
  • v0.4.0 protected
  • runtime-400 protected
40 results
Blame Permalink
  • Hugo Trentesaux's avatar
    ef73a0d0
    improve documentation (!101) · ef73a0d0
    Hugo Trentesaux authored and Éloïs's avatar Éloïs committed 
    * fix

* doc(end2end): detail test users

* doc(all): update docker tag

update docker image name from 0.2.0 to 0.3.0
use "docker compose" everywhere instead of "docker-compose"
improve table of content
fix layout

* doc(all): improve docs

add logo to readme
add table of content
rewording
complete

* doc(all): fix typos
    ef73a0d0
    History
    improve documentation (!101)
    Hugo Trentesaux authored and Éloïs's avatar Éloïs committed 
    * fix

* doc(end2end): detail test users

* doc(all): update docker tag

update docker image name from 0.2.0 to 0.3.0
use "docker compose" everywhere instead of "docker-compose"
improve table of content
fix layout

* doc(all): improve docs

add logo to readme
add table of content
rewording
complete

* doc(all): fix typos
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.