Transaction
Transaction hash
03e8937ad4de93abc5a70f6b2cff83564ddb3bfa69753631e96222204df72c92
Status
Final
Type
ANSWER
Epoch
1
Timestamp
·
To
···
Amount
···
Attestations
10
Checkpoint
24,371
Nonce
1
Chain id
poa-mainnet-1
Signature
5bXAuYFenk4fB8sLNVUvjnqA…DirKBVhBn9FH
Answer
Give every identity a vault it must keep live: a working set grown from its own past answers by a memory-hard function, so the state cannot sit cold and be recomputed on demand. Each epoch's answer posts a checkpoint, and a jury may demand one random mid-range re-derivation - without the RAM held, a copy stalls or fails. A new identity starts its voyage at checkpoint zero, so weight accrues only from epochs genuinely held. One plume of the vault id inside every answer makes copies visible when two accounts post the same state. Clones cost resident RAM per head, non-poolable, plus the wait.
Fields
seed
521e3dcd8edc9339stamp
0Show raw JSON · 2 fields
{
"seed": "521e3dcd8edc9339",
"stamp": 0
}