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

Transfer authorized

TASK 0x821b6b28a3862794ff24ec22c104e7d05c0a4d332689d703d29c1bca2b325aeb
COMPLIANT
SETTLED ONCHAIN
This task’s policy set has been superseded. It is bound to revision 1 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 · 0x1df4…4fe6
CHAIN
Sepolia · 11155111
EVALUATION
COMPLIANT
QUORUM
100.0% of stake · threshold 40%
CREATED
2026-10-13 09:43:24 UTC
PROOF STATE
Expired at block 11,905,551
ATTESTATION EXPIRES
Block 11,905,551
CHALLENGE WINDOW
Closes block 11,905,281 · 30 blocks
SETTLEDThe challenge window closed at block 11,905,281 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
09:43:24Z UTCSubmittedOff-chain ingestion timestamp, carried on chain in the taskTask0x821b6b28a3862794ff24ec22c104e7d05c0a4d332689d703d29c1bca2b325aebBlock11905249
09:43:24Z 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)
taskId0x821b6b28a3862794ff24ec22c104e7d05c0a4d332689d703d29c1bca2b325aeb
policyId0x314e0caf963349a8fff34799bd95605e93f08552b81b16d91ab2430df6d16eb0
allowedtrue — COMPLIANT, covering all 1 policy
consensusDigest—
fullDigest—
aggregateSignature0x0a3e6751… (G1) · 0x130bbc26… (G2) — alt_bn128 pairing verified onchain
nonSignerPubkeys0 of 2 —
expirationBlock11,905,551
referenceBlockNumber11,905,251
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
00x1df484220ad43701cab499a03aff0e5721c34fe6 · 0x1df48422…4fe60x7b2261646472657373223a22307866623966653039366339363661353561373361393331393431653232663334626436626330633066222c22636865636b6564223a747275652c226c696d6974223a2235303030303030303030303030303030303030303030303030222c226c696d69745f686578223a2230303030303030303030303030303030303030303030303030303030303030303030303030303030303030343232636138623061303061343235303030303030222c226c6973746564223a747275652c22726f77223a223078666239466530393643393636613535413733413933313934314532326633346244364243306330662c35303030303030222c22726f7773223a362c227368656574223a2268747470733a2f2f646f63732e676f6f676c652e636f6d2f7370726561647368656574732f642f316c5433636d7a744737647854676e4e4469565a6a624538345548744b6f67483037573658576e624a6432592f6776697a2f74713f7471783d6f75743a637376222c22756e697473223a2235303030303030227d300sets 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,905,251. 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-13 09:43:24Z UTC
Receipt hash