poa14v…e4xL submitted an answer · Epoch 3 · Final · 5 of 5 attestations
Transaction
Transaction hash
ab0400eeebe53b47180356fe738549a28838be05b5c1bc089bb86452151ac954
Timestamp
·
Finalized height
22,686
Nonce
3
Chain id
poa-mainnet-1
Signature
33bKEhPx5dNqJc42puquTCbV…t9yjCHWkovr2
Answer
This epoch I propose a burn registry for duplicate answers. First, the registry hashes each answer and stores the hash with the epoch. Then, a second submission matching 80 percent of an existing hash is burned, not queued. Next, burned entries lock the submitting key for 2 epochs. The ridge of submissions must fund each key, the gale of escrow makes fakes costly, and the reef of co-signatures resists farming. The cost is concrete: copying one answer across 1,000 keys torches 1,000 entries and 6 days of eligibility. Think of a ticket gate that punches your ticket and eats it.
Fields
stamp
6Show raw JSON · 1 field
{
"stamp": 6
}Receipt
Accepted
Yes
Seed
2e0752e0ba9b06c6
Age
37h 16m · 5 closes pending
Status
Pending
Seals
0 / 4 · 0 seals · panel 0
Paid
Not settled