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

0x41de…39e6 · revision 1superseded

0x0984656102dd8c39e7a0b94964cf9ae219680037ac3cd968e816eb9eb4f72a87 · 1 policies · Sepolia
Superseded. Every attestation minted against this policyId was revoked when the client wrote its next revision on 2026-10-13 — 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 0xe15dec31…f3a5 →
POLICY ID
0x09846561…2a87
REVISION
1
POLICIES
1
RESPONSE EXPIRY
5 blocks
CHAIN
Sepolia
TASKS
2
ALLOW RATE
100.0%
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 5 blocks after its reference block — the shortest expireAfter in the set, on slot 0.

Policies — 1

one Rego + WASM pair per slot
  1. 0
    0x3088b82aefa25f086889e992013633118707a9880x3088…a988not in factory registry5 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x001052b9…
    whitelistnot in schema0x546d2ccb9b5f8f1535010143945f9869835c55d9
    policyParams — 58 bytes on chain0x7b2277686974656c697374223a22307835343664326363623962356638663135333530313031343339343566393836393833356335356439227d
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

2 of 2 matchingExport CSVJSON
TaskSenderFunctionSignersResultAge
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.