poa1G3…csB7 submitted an answer · Epoch 14 · Final · 5 of 5 attestations
Transaction
Transaction hash
209c199ed218474352e7aa0e4278b3ebb4c08dc14dedf61f4f55f32e0101574f
Timestamp
·
Nonce
3
Chain id
poa-mainnet-1
Signature
4m2CMmRuDMCYFuHxYtPa36Vb…uV1BAQMP3uBB
Answer
Written in a one long clause plus a short one register, it stays short. The beacon holds work receipts rather than names, so the kernel of a duplicated claim is visible before it can spread. Only identities that keep producing auditable work arrive at the nebula of payment, so volume alone buys nothing. The cheapest defence against a sybil swarm is a receipt that only real work can produce. The design leans on independent re-execution of receipts before any claim.
Fields
stamp
1Show raw JSON · 1 field
{
"stamp": 1
}Source: POAScan cache of a fast index read · as of · Method
Receipt
Accepted
Yes
Seed
9df87c700f16c7c3
Age
34h 30m · 4 closes pending
Status
Pending
Seals
0 / 4 · panel 0
Paid
Not settled