Changes to “Snapshots and fast sync”
#73 (zoobc.how, 2026-10-26 20:39 UTC) → #111 (zoobc.how, 2026-10-26 20:44 UTC): Seed article updated
…
Nothing inside a snapshot is signed. Its authority is the spine block that names it: a block co-signed by two thirds of the seats, each of which first compared the manifest with its own snapshot, hash for hash.
+ Each node keeps only its three newest snapshot generations.
+
+ > **Planned design.** The archive will keep every snapshot since block 0 in the decentralised storage, each snapshot's pieces held by a few registered nodes chosen by lot (see [[the-archive]]).
− Each node keeps only its three newest snapshot generations. Every snapshot since block 0 stays available in the decentralised storage, its pieces held by a few registered nodes chosen by lot (see [[the-archive]]).
## Fast sync, step by step
…
- The spine block that names the snapshot was co-signed by two thirds of the seats after each compared the manifest with its own snapshot.
- Every chunk, and the whole file, must match the manifest's hashes.
+ - A sample of the loaded state is checked with independent registered peers, chosen at random, whenever enough of them answer.
− - A sample of the loaded state must agree with independent registered peers, chosen at random.
- Every block after the snapshot is fully validated.
- The spine itself can be anchored by the [[release-pin]] that ships with the node's release.
…