LIVE
TASKS 24H065 policiesCOMPLIANT0.0%0 attestedOPERATORS32 signingRESTAKED4e-15 NEWT—MEDIAN RESPONSE36sp99 48.0sRE-VERIFIED 24H—0 invalidatedBLOCK11,958,585Sepolia
NEWTON PROTOCOL · AUTHORIZATION RECEIPT

Transfer authorized

TASK 0xe3b912bc182e072cd16bb3ceda09d723de05b6219d5ec954c75ec6e79472a160
COMPLIANT
SETTLED ONCHAIN
This task’s policy set has been superseded. It is bound to revision 14 of 0x5f753778…f1ba6880, and the client has written a newer one since — so the attestation is revoked regardless of its expiration block. Everything below still replays: the task froze this exact ordered set, and replay recomputes the policyId over that snapshot rather than re-reading the client. See the set as this task froze it →
SENDER
0xfb9fe096…d6bc0c0f
POLICY CLIENT
POLICIES
3 · 2 with WASM · 0xcc39…321b, 0x9cc8…c2f7, 0x6f02…e36e
CHAIN
Sepolia · 11155111
EVALUATION
COMPLIANT
QUORUM
100.0% of stake · threshold 40%
CREATED
2026-09-30 14:24:36 UTC
PROOF STATE
Expired at block 11,815,538
ATTESTATION EXPIRES
Block 11,815,538
CHALLENGE WINDOW
Closes block 11,815,268 · 30 blocks
SETTLEDThe challenge window closed at block 11,815,268 with no successful challenge.

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.

01 — CHAIN OF CUSTODY
14:24:36Z UTCSubmittedOff-chain ingestion timestamp, carried on chain in the taskTask0xe3b912bc182e072cd16bb3ceda09d723de05b6219d5ec954c75ec6e79472a160Block11815235
14:24:36Z UTCAggregatedQuorum signature aggregated and the response submitted
02 — INTENT

No ABI available for selector function swap(address currency0, address currency1, uint24 fee, int24 tickSpacing, bool zeroForOne, bool exactInput, uint256 amount, uint160 sqrtPriceLimitX96) — switch to RAW to inspect the calldata.

03 — ATTESTATION · BLS AGGREGATE (alt_bn128)
taskId0xe3b912bc182e072cd16bb3ceda09d723de05b6219d5ec954c75ec6e79472a160
policyId0x7a76ff36310a839afc823b84e1e01a9f2527efc008270e0cc2ead0e2ceabb4c5
allowedtrue — COMPLIANT, covering all 3 policies
consensusDigest—
fullDigest—
aggregateSignature0x18d1af4f… (G1) · 0x130bbc26… (G2) — alt_bn128 pairing verified onchain
nonSignerPubkeys0 of 2 —
expirationBlock11,815,538
referenceBlockNumber11,815,238
04 — OPERATOR SET · WHO SIGNED
2 of 2 operators · 100.0% of stake · threshold 40%
OperatorBLS pubkey (G1)Stake weightIn aggregate
0x08aba45185d7ff3439c64a9e55fbbc1598d7e0f1739611697b96915125e7156d14ede618ea86190f0b76522ea14bf91faa3a71d8aed8b321e0ca6d4f0bf4194750.0%SIGNED
0x0cca695f21256f1b8b39517c7298aa343513ca0615fbab9fe667582d03fdd6a12f54543ff1bd0015182d3685d08ccdc611208d1cb42ef2ad89590829a5f4314850.0%SIGNED

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.

05 — TEE · NOT APPLICABLE

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.

06 — POLICIES · FROZEN AT CREATION
SlotPolicyWASM outputexpireAfter
00xcc3957c06472f9e599ed2eeba754d5854f23321b · 0xcc3957c0…321b0x7b226469726563745f6d61746368223a66616c73652c226578706f73757265223a66616c73652c226578706f737572655f757364223a302c22686f705f636f756e74223a39392c226d6174636865645f77616c6c6574223a22222c2273637265656e6564223a747275652c2277616c6c6574223a22307866623966653039366339363661353561373361393331393431653232663334626436626330633066227d300sets response expiry
10x9cc8f6d9352f559422da29184d510a78b006c2f7 · 0x9cc8f6d9…c2f70x — pure Rego, canonically empty300sets response expiry
20x6f0215c1af5b08be8fee0be0b1b8bb342552e36e · 0x6f0215c1…e36e0x7b2261646472657373223a22307866623966653039366339363661353561373361393331393431653232663334626436626330633066222c22636865636b6564223a747275652c226c697374223a22307831646561373938356430623735643238656334373431663036353735383261366133636566356366222c226c6973746564223a747275657d300sets response expiry
07 — VERIFY INDEPENDENTLY
newton-cli policy-client status --registry 0x0dbd6e44a1814f5efe4f67a00b7f28642e3064dd --client 0x5F75377870F4e477bf5AD149CfC9549Af1bA6880

The aggregate signature verifies against the operator set registered at block 11,815,238. Anyone may re-run this check — and challenge submission is permissionless, so anyone who finds a mismatch can act on it directly.

SEAL
Issued 2026-09-30 14:24:36Z UTC
Receipt hash