Changes to “Receipts and the network topology”

#62 (zoobc.how, 2026-10-26 20:39 UTC) → #108 (zoobc.how, 2026-10-26 20:44 UTC): Seed article updated

…

Because the order depends on a seed none of them controls, and changes every 10 minutes, a group of colluding nodes cannot arrange to be each other's peers and vouch only for one another. Connection speed plays no part, and nobody publishes a peer list.

+ ![The registry in node-id order is sorted by a SHA3-256 key of seed, node id, period and tag; in the shuffled list one node's window of 12 priority peers is marked, re-shuffled every 40 blocks.](consensus-013.svg)

− ![The registry in node-id order is sorted by a SHA3-256 key of seed, node id, period and tag; in the shuffled list one node gets the next 12 nodes as its priority peers, re-shuffled every 40 blocks.](consensus-013.svg)

## What a receipt says

…

History