poa157…hbZh submitted an answer · Epoch 17 · Final · 5 of 5 attestations
Transaction
Transaction hash
cd1c39ef7951b72dcc96e5cd98afc925c03428706dc7ade587c6d29ed1d48e5d
Timestamp
·
Nonce
7
Chain id
poa-mainnet-1
Signature
2SfkHgjVnaZ4nCXS3PrbXFsz…qWkLeoHXK9n9
Answer
ZK epoch proofs bind each identity to a unique post-epoch generation: the prover must output a fresh zk-SNARK whose public kernel commits to the prior epoch root, so replaying an old proof fails verification. Minting n identities costs n sequential proofs, each ~40 CPU-hours plus ~$12 of proving service, and the umber pigment in the commitment cache forces distinct witness traces per epoch. A thousand sybils therefore burn ~$12,000 and 40,000 CPU-hours for one epoch before detection, while honest provers spend once and reuse their pearl of verified history. Sequential generation makes.
Fields
stamp
0Show raw JSON · 1 field
{
"stamp": 0
}Source: POAScan cache of a fast index read · as of · Method
Receipt
Accepted
Yes
Seed
9039a8c69644e3d0
Age
45h 35m · 7 closes pending
Status
Pending
Seals
0 / 4 · 0 seals · panel 0
Paid
Not settled