Transfer authorized
Every challenger watching this chain independently re-evaluated the policy against the same inputs and none could produce a proof that the result differs. This is final: the window cannot be reopened.
No ABI available for selector admit() — switch to RAW to inspect the calldata.
One aggregate BLS signature is submitted on chain, not one per operator — so an individual signature, the prepare/commit phase it was produced in, and per-operator latency are not recoverable from any record. Membership above is exact; the parts the gateway discarded after aggregating are not shown rather than guessed.
No policy in this set reads private data, so its operators produced no enclave attestation and none is stored on chain. Privacy is decided per policy — a set needs only one slot touching a privacy namespace, and then the whole set runs inside one enclave request. Correctness here rests on the policy re-evaluation proof any challenger can generate — section 07 — not on hardware isolation.
| Slot | Policy | WASM output | expireAfter |
|---|---|---|---|
| 0 | 0x73b70f3a3029f0b9d99eec49e28ce00830afb826 · 0x73b70f3a…b826 | 0x7b2277686974656c6973745f61646d697373696f6e223a7b7d7d | 25sets response expiry |
newton-cli policy-client status --registry 0x0dbd6e44a1814f5efe4f67a00b7f28642e3064dd --client 0x7a0c93085e161747b39e8461F40761543A9534AF
The aggregate signature verifies against the operator set registered at block 11,924,021. Anyone may re-run this check — and challenge submission is permissionless, so anyone who finds a mismatch can act on it directly.
Receipt hash