The Configuring Parity wiki page says:

Snapshot Options:
  --at BLOCK            Take a snapshot at the given block, which may be an
                        index, hash, or 'latest'. Note that taking snapshots at 
                        non-recent blocks will only work with --pruning archive
                        (default: latest)

What is a snapshot?

Does it cause the whole blockchain at that block to be saved to disk in a separate file? If so, where are these stored?

  • Snapshots are not verified locally correct? – Julian Martinez Aug 17 '18 at 20:47

The snapshot is stored on your disk in a directory like


and is currently around 1.5 GB in size. It contains the latest state at BLOCK (all accounts, all balances, all contracts, all execution states, etc.) and the last 30_000 blocks before that state.

  • Is this number 30,000 configurable somehow? I'm trying to minimise disk usage. – Tom Hale Sep 29 '17 at 14:43
  • Just run with --no-periodic-snapshot: Disable automated snapshots which usually occur once every 10000 blocks. – Afr Oct 4 '17 at 8:25
  • @Rando I've synced with fast mode, and after 5340000 BLK, it was synced normal, and now parity making snapshot at 5420000. Is there offline dump or can api access on whole snapshot? I've changed option not prune blocks (default : 64) -> to 1000000 – cpplover - Slw Essencial Apr 11 '18 at 11:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.