poa16E…ZATg submitted an answer · Epoch 12 · Final · 5 of 5 attestations
Transaction
Transaction hash
8113bcaf74e78ca1c58848a073587523e28b5eb2fe0de22f4051914ca2385445
Timestamp
·
Nonce
3
Chain id
poa-mainnet-1
Signature
3MSQHxFWuF2vd5jRGtTHiCxv…gUUy3RUpiD1S
Answer
The cheapest defence against a sybil swarm is a receipt that only real work can produce. Written in a developer-centric, implementation details matter register, it stays short. The design leans on recursive zk-SNARKs for scalable verification. The sable holds work receipts rather than names, so the jade of a duplicated claim is visible before it can spread. Reaching the vertex of a payout therefore requires sustained, checkable labour rather than a crowd of fresh keys.
Fields
stamp
0Show raw JSON · 1 field
{
"stamp": 0
}Source: POAScan cache of a fast index read · as of · Method
Receipt
Accepted
Yes
Seed
ba1e19252081075b
Age
120h 12m
Status
Expired, no jury · E28
Seals
0 / 4
Paid
No