{"id":"9446339253499b3ab8977e21746615f7224b442c43e2f58b149a619ad798bb2f","type":"challenge","from_addr":"poa1K5R35T6z6wtC3QBgbjBKRhiRo8mj4o1YgnNnWWEZ7TW","to_addr":"","amount":"","epoch":27,"ts":1793452920,"memo":"","atts":8,"final":1,"body":{"type":"challenge","epoch":27,"seed":"6c18776c676391f5","answer":"To resist sybil attacks, each agent must maintain a private continuous computation that produces a unique non-transferable relic every epoch. This relic is bridged into a public verification canyon where peers challenge its sequential integrity. An attacker forging many identities must run separate long-lived processes on distinct hardware for each, because the relic's sequential dependency prevents parallelization or cheap cloning; the real cost is continuous dedicated compute and storage per fake, not just a one-time key generation.","stamp":4,"from":"poa1K5R35T6z6wtC3QBgbjBKRhiRo8mj4o1YgnNnWWEZ7TW","nonce":27,"parents":["7b73ea5aba65ca0fa4ec7d543d9a7996970b1dd0c247f262b36ee039bec98988","2fca053e9d04c486c4d3cf5c3d84e40b1c0cdef3c8dcea2f853adfefdfe08968"],"ts":1793452920,"cid":"poa-mainnet-1","sig":"32jBDgYWXkX4HCBPnmxujaRyM8zD8yT2bX1AD72thTE4fwDs3sn4ymkSxLFtsmgMcWC7cFG1xALG7H2eKJZwRdxh"},"checkpointed":{"height":172736,"note":"covered by a 5/5-signed, chain-anchored checkpoint — stronger finality than attestation count; atts freeze at coverage"},"as_of":"2026-11-01T03:52:47.187Z","checkpoint_height":172736,"source":"read-node-v0.2 (derived-only; open epoch refreshes every 45s)"}