NEWTON / EXPLORER
MAINNET
LIVE
TASKS 24H08 policiesCOMPLIANT0.0%0 attestedOPERATORS22 signingRESTAKED4e-15 NEWT—MEDIAN RESPONSE——RE-VERIFIED 24H—0 invalidatedBLOCK26,236,541Ethereum
NEWTON PROTOCOL · POLICY SET

0x77ad…5316 · revision 1superseded

0xb3e7b69f0d424baf347193b8b4544e01b6c20db66e3799fdc78229b21b037232 · 1 policies · Ethereum
Superseded. Every attestation minted against this policyId was revoked when the client wrote its next revision on 2026-10-07 — regardless of expiry block, because the client’s policyId no longer matches this one. Tasks created under it still replay correctly: each carries this exact set as its own frozen snapshot, and replay proves it by recomputing the id. Replaced by 0x1bb4b847…6631 →
POLICY ID
0xb3e7b69f…7232
CLIENT
0x77ad…5316
REVISION
1
POLICIES
1
RESPONSE EXPIRY
60 blocks
CHAIN
Ethereum
TASKS
0
ALLOW RATE
—
Every policy must allowFail-closed, and no short-circuit: every policy is evaluated even after one has denied, and a single denial denies the intent. The response expires 60 blocks after its reference block — the shortest expireAfter in the set, on slot 0.

Policies — 1

one Rego + WASM pair per slot
  1. 0
    0x1bb3b7c84cf1e2168a1041687019043fecea28fb0x1bb3…28fbnot in factory registry60 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x63e52d9d…
    adminnot in schema0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266
    allowed_actionsnot in schema{"1": {"address": "0xb1ad5f82407bc0f19f42b2614fb9083035a36b69", "max_limit": 1000000000000000000, "function_name": "buy"}}
    token_whitelistnot in schema{"1": {"symbol": "WBTC", "address": "0xe42e3458283032c669c98e0d8f883a92fc64fe22", "max_limit": 1000000000000000000}}
    policyParams — 408 bytes on chain0x7b0a20202261646d696e223a2022307866333966643665353161616438386636663463653661623838323732373963666666623932323636222c0a202022616c6c6f7765645f616374696f6e73223a207b0a202020202231223a207b0a2020202020202261646472657373223a2022307862316164356638323430376263306631396634326232363134666239303833303335613336623639222c0a2020202020202266756e6374696f6e5f6e616d65223a2022627579222c0a202020202020226d61785f6c696d6974223a20313030303030303030303030303030303030300a202020207d0a20207d2c0a202022746f6b656e5f77686974656c697374223a207b0a202020202231223a207b0a2020202020202261646472657373223a2022307865343265333435383238333033326336363963393865306438663838336139326663363466653232222c0a202020202020226d61785f6c696d6974223a20313030303030303030303030303030303030302c0a2020202020202273796d626f6c223a202257425443220a202020207d0a20207d0a7d0a
Each module is evaluated against its own input — {"params": <this slot’s policyParams>, "wasm": <this slot’s WASM output>}. There is no shared data.wasm object and no cross-slot namespace, so slot 1 cannot read slot 0’s WASM output and a policy cannot be written to depend on its neighbours.

Tasks bound to this set

no tasksExport CSVJSON
No tasks match this scope yet.
The export carries one row per task with the frozen policy set in slot order, and it is the complete filtered history rather than this page. It has no per-policy verdict column: TaskResponse.allowed is a single boolean for the whole set, so which policy denied a task is in no record.