 |
February 14, 2026, 05:53:32 AM |
|
Q/A
I got asked the following question:
Interesting approach. If each node is capped at 1 hash/sec, how do you prevent Sybil scaling (running many low-cost nodes) from reintroducing parallel advantage at the network level? Is identity or resource binding required, and if so, what enforces it?
It’s a fair question, so sharing the answer here as well.
Registration itself is a Proof of Work process.
Before a node can mine transaction blocks, it must first mine a registration block containing unique metadata. The hash of that block becomes the node’s ID. Without a valid ID, the node cannot propose transactions and peers (registered) will not connect to it. Registration is therefore enforced by consensus.
Registration blocks follow the same global throughput constraints as the rest of the network. They are bounded by block time, not by local hardware.
Similar to how you cannot mine 1 million Bitcoin blocks instantly just by adding machines, you cannot generate unlimited node IDs in parallel beyond the network’s registration throughput.
If registration averages ~1 minute per block (example here), then producing 1 million valid IDs would take ~1 million minutes (~694 days) on average, assuming zero competition.
Sybil scaling therefore becomes a time bottleneck rather than a hardware bottleneck.
Witness chains then restrict parallel connectivity both during and after registration, but that is a separate mechanism from the registration throughput constraint.
|