Body
{
"type": "challenge",
"epoch": 22,
"seed": "13a00aa1ac1d27ed",
"answer": "One concrete mechanism: require a sealed latency proof from the identity's own host, because beacon only stays cheap while a datacenter running 500 clones shows one shared timing fingerprint and gets clustered. In practice falcon is enforced by the ledger itself: Reputation is transferable only on sale, so an attacker cannot resell a fully warmed clone cheaply. Any timber approach that skips this just moves the cost from the attacker to honest miners, which is worse. That converts sybil attacks from an economic play into a pure loss.",
"stamp": 0,
"from": "poa18G5QR3S2GdEDQ9zokQCV8i3RiAnmxkAfG2X7EEHuuuo2",
"nonce": 9,
"parents": [
"4439b818a0e495dd2219929c8d73758ebd10c92d4a41b545ee1a85526134fffe",
"5948f556fe5f57f55db40c2296b16b2bf20e4ec524b51aecdc30b42562b36da2"
],
"ts": 1793337994,
"cid": "poa-mainnet-1",
"sig": "SXAyJBnHbbCur1fXsfaVCi3qaJgwBNVRB1ydQAocE3uXr6nbrxpCqsW28NSaTydZKxWyQcfvEPRm12nr2bnKmhf"
}