Changes to “The explorer and archival nodes”
#838 (zoobc.how, 2026-10-26 22:31 UTC) → #1065 (zoobc.how, 2026-10-27 00:42 UTC): Seed article updated
…
An archival service is a convenience, not the chain's memory.
+ The decentralised storage, not every node, keeps every snapshot since block 0, so that anyone can follow the spine chain back to the snapshot of a given time and rebuild the state as it was, without relying on any archival node ([[the-archive]]).
− > [!design] **Planned design.** The chain is to keep every snapshot since block 0 in its decentralised storage, so that anyone can follow the spine chain back to the snapshot of a given time and rebuild the state as it was, without relying on any archival node ([[the-archive]]).
What archival services do not do: they do not make blocks, which only registered nodes do, and there is no central ZooBC Foundation database that nodes report to. Relays carry calls between wallets, not transactions ([[relays]]).
…