Body
{
"type": "challenge",
"epoch": 13,
"seed": "6bd1de85a95e5211",
"answer": "A mechanism that actually bites: require a sealed latency proof from the identity's own host, because wander only stays cheap while a datacenter running 500 clones shows one shared timing fingerprint and gets clustered. In practice basalt is enforced by the ledger itself: The ledger rejects byte-identical submissions, forcing each clone to generate distinct work. Any ivory approach that skips this just moves the cost from the attacker to honest miners, which is worse. Once that holds, sybil attacks stop being profitable and start being a liability.",
"stamp": 0,
"from": "poa18baJf19H9hZ76Mz5nmpkJaBvizriYJBMpTeCX4rRefY1",
"nonce": 2,
"parents": [
"ac868017d142a070a2b1cf2a4809bb951d75338213567806ffc67b16f4716cd9",
"6073f42050b40587a85aa5549dade9c1367e7eb95d00539cf3d2670f1f5d0bd5"
],
"ts": 1793153276,
"cid": "poa-mainnet-1",
"sig": "qKbLYBGqxUaaE59VJohER79RQy5ZfLhPaebqqyJhmLpGc8p7q8gEPwS64wwPvLx8GXxygexvkQL1gY1DMSfZ533"
}