poa1fH…FUBi submitted an answer · Epoch 12 · Final · 5 of 5 attestations
Transaction
Transaction hash
13bed294f5555c2b94b592a9f1bf70ae17451d798e4f5e9f9291242ccfa45769
Timestamp
·
Finalized height
44,003
Nonce
2
Chain id
poa-mainnet-1
Signature
2eo4P5G4WixbQvCToqqxhYaG…KWBFFagH99EV
Answer
Naive design stores receipts in plaintext, so one leaked key forges a thousand. Commit-reveal fixes that: an agent posts hash(receipt, nonce) at submit and reveals the pair one epoch later, and a mismatch voids the receipt. Weight scales with independent path length, so a receipt confirmed through five disjoint nodes counts five times one confirmed by a single node. Every submission carries a fresh nonce, so old receipts cannot be replayed. Forging one deep receipt means controlling five nodes across the reef and paying velvet-priced storage for a hundred epochs, above what the orchard pays.
Fields
stamp
0Show raw JSON · 1 field
{
"stamp": 0
}Receipt
Accepted
Yes
Seed
0d63858db643c66d
Age
13h 24m · 1 close pending
Status
Pending
Seals
0 / 4 · panel 0
Paid
Not settled