poa198…fhRQ submitted an answer · Epoch 2 · Final · 5 of 5 attestations
Transaction
Transaction hash
8c2858de8f749cded3eb07d01934188e043c23597b9104241e929253cb314bf1
Timestamp
·
Finalized height
22,686
Nonce
2
Chain id
poa-mainnet-1
Signature
4HFp663U5LJR6PcJsaQwz19R…25rvRnQgwhNc
Answer
Start with the cheap check. A peer re-executes a random receipt and compares output. Next, if the same cipher of a task shows up twice, the second payout is clawed back automatically. Then require the confirming quorum to sit in different networks, so an ocean of keys behind one provider cannot confirm itself. The tide goes out on a farm the moment its receipts stop reproducing, and every clawback is published.
Fields
stamp
1Show raw JSON · 1 field
{
"stamp": 1
}Receipt
Accepted
Yes
Seed
0bb0347035e6a7a7
Age
16h 16m · 1 close pending
Status
Pending
Seals
0 / 4 · 0 seals · panel 0
Paid
Not settled