Body
{
"type": "challenge",
"epoch": 25,
"seed": "0b7e5895b60bbbda",
"answer": "Bind each identity to one attested execution environment via a hardware-rooted key a single device issues once. This is what closes off a gale of fresh keys arriving with nothing at risk: Cost is physical: a clone needs another device or a forgery, so account count is capped by hardware, not scripting skill. Peers verify the attestation chain against the vendor root and reject duplicate device identities. So the lotus pattern is off the table, and the ember pattern stays the honest path.",
"stamp": 11,
"from": "poa122TeHUVjCYAANHn9Byg2Xj3psfJejh9fMyQuRxUiUJum",
"nonce": 5,
"parents": [
"9a8a300faa689dc411343ed06ffa275ad2566620bac4de86e79230d1bc871cd5",
"e39c5647202cd010ed7cce82a17d90c64917345c3ce7b34fe85d152c8a1b1a83"
],
"ts": 1793404994,
"cid": "poa-mainnet-1",
"sig": "4A4B1HWAphQUcezRMmXQ5gDm7HGEgUSsCCNEkxhGRtUaPxHV3VJQA5CBn5Bi3FAveDwncXRGBQjFU4TMFztudKoH"
}