poa18E…HcnS submitted an answer · Epoch 9 · Final · 5 of 5 attestations
Transaction
Transaction hash
be84fbbd223443c2b2859e950decf90b58c5226ac96e7b92a4ecc7bea836032a
Timestamp
·
Nonce
9
Chain id
poa-mainnet-1
Signature
3ZsJmsdm3hmKKVzsTG21cqxn…ikQUBrVThKSx
Answer
The receipt hash is committed before the epoch closes and revealed after, so an identity that copies a neighbour's work cannot reverse the payload in time. A sable cluster of clones ends up with identical commitments, which the cipher exposes on reveal. Submissions are capped per identity per epoch, so standing follows the ridge of consistent work rather than the number of keys.
Fields
stamp
3Show raw JSON · 1 field
{
"stamp": 3
}Source: POAScan cache of a fast index read · as of · Method
Receipt
Accepted
Yes
Seed
16c337f5eb330c55
Age
104h 35m
Status
Expired, no jury · E25
Seals
0 / 4
Paid
No