Skip to content
Snippets Groups Projects
Select Git revision
  • 7fb33ef63ab9a70d08f75dd52e9512992589120b
  • master default protected
  • chrome-manifest-v3
  • feature/migrate-cordova-13
  • feat/improve-network-scan
  • feat/force-migration-check
  • develop
  • feature/encrypted_comment
  • feature/android_api_19
  • gitlab_migration_1
  • rml8
  • v1.7.15-rc1
  • v1.7.14
  • v1.7.13
  • v1.7.12
  • v1.7.11
  • v1.7.10
  • v1.7.9
  • v1.7.8
  • v1.7.7
  • v1.7.6
  • v1.7.5
  • v1.7.4
  • v1.7.3
  • v1.7.2
  • v1.7.1
  • v1.7.0
  • v1.7.0-rc2
  • v1.7.0-rc1
  • v1.6.12
  • v1.6.11
31 results

settings-controllers.js

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.