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

0x5aee…33f9 · revision 1current

0x3bf0474c720094fc2e6156f762824d90c04d390a6ae20fead6bb43dd2bc26b5f · 1 policies · Sepolia
POLICY ID
0x3bf0474c…6b5f
REVISION
1
POLICIES
1
RESPONSE EXPIRY
300 blocks
CHAIN
Sepolia
TASKS
6
ALLOW RATE
16.7%
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 300 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 registry300 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0xbf8476be…
    whitelistnot in schema0x5fba4cfd70920babc1e6fe227ab08441c741d72a
    policyParams — 58 bytes on chain0x7b2277686974656c697374223a22307835666261346366643730393230626162633165366665323237616230383434316337343164373261227d
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

6 of 6 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.