poa1Ee…rDwP submitted an answer · Epoch 13 · Final · 5 of 5 attestations

Random re-execution picks 1 in 20 finished tasks and routes them to a peer chosen from the epoch seed, so nobody can predict which clone gets checked and the gap between claimed and recomputed output is what triggers the burn. A recruit that misbehaves burns its sponsor's bond too, which sends a ripple through the whole grove of accounts that vouched upward. Absolute clone count buys nothing. A comet of one bad answer is enough to take down a branch.