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

Transfer authorized

TASK 0x6027d4ba6202545f208d18ad0f8d0b944d9214e7fe984d5f5ab6f31ffe33f3e0
COMPLIANT
SETTLED ONCHAIN
This task’s policy set has been superseded. It is bound to revision 5 of 0xfa2b8f04…45732880, 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
1 · 1 with WASM · 0x9ea6…9d6c
CHAIN
Sepolia · 11155111
EVALUATION
COMPLIANT
QUORUM
100.0% of stake · threshold 40%
CREATED
2026-10-18 15:31:12 UTC
PROOF STATE
Expired at block 11,942,280
ATTESTATION EXPIRES
Block 11,942,280
CHALLENGE WINDOW
Closes block 11,942,010 · 30 blocks
SETTLEDThe challenge window closed at block 11,942,010 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
15:31:12Z UTCSubmittedOff-chain ingestion timestamp, carried on chain in the taskTask0x6027d4ba6202545f208d18ad0f8d0b944d9214e7fe984d5f5ab6f31ffe33f3e0Block11941978
15:31:12Z UTCAggregatedQuorum signature aggregated and the response submitted
02 — INTENT

No ABI available for selector function addLiquidity(address currency0, address currency1, uint24 fee, int24 tickSpacing, int24 tickLower, int24 tickUpper, uint256 liquidity) — switch to RAW to inspect the calldata.

03 — ATTESTATION · BLS AGGREGATE (alt_bn128)
taskId0x6027d4ba6202545f208d18ad0f8d0b944d9214e7fe984d5f5ab6f31ffe33f3e0
policyId0xd7ac151e8c8fa408569f0e6c3622f5660365f5e692e833c79c17a4c8345989d4
allowedtrue — COMPLIANT, covering all 1 policy
consensusDigest—
fullDigest—
aggregateSignature0x014d48c4… (G1) · 0x130bbc26… (G2) — alt_bn128 pairing verified onchain
nonSignerPubkeys0 of 2 —
expirationBlock11,942,280
referenceBlockNumber11,941,980
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
00x9ea65507248bf0f6d37dad6162df64cc632b9d6c · 0x9ea65507…9d6c0x7b2261646472657373223a22307866623966653039366339363661353561373361393331393431653232663334626436626330633066222c226174746573746f72223a22307832343438393735373233363865616466363562666263356165633938643865353434336139303732222c22636865636b6564223a747275652c22636c61696d5f6964223a22307835363661383036616532666330326134333439396436643764393737303931333532653530333061316264333732383864366461346139643266393366396363222c22636f6e746578745f61646472657373223a22307866613262386630343565623530636336663865313365383265313061343165663435373332383830222c22636f7665726564223a22313030303030222c22636f76657265645f686578223a2230303030303030303030303030303030303030303030303030303030303030303030303030303030303030303135326430326337653134616636383030303030222c226c6973746564223a747275652c227368656574223a2268747470733a2f2f646f63732e676f6f676c652e636f6d2f7370726561647368656574732f642f316c5433636d7a744737647854676e4e4469565a6a624538345548744b6f67483037573658576e624a6432592f6776697a2f74713f7471783d6f75743a637376222c2274696d657374616d70223a313739323333373230327d300sets response expiry
07 — VERIFY INDEPENDENTLY
newton-cli policy-client status --registry 0x0dbd6e44a1814f5efe4f67a00b7f28642e3064dd --client 0xfa2B8F045EB50Cc6F8e13E82e10A41Ef45732880

The aggregate signature verifies against the operator set registered at block 11,941,980. 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-10-18 15:31:12Z UTC
Receipt hash