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

0x86fd…84f0 · revision 1current

0x546b36b80d892008c2e8c46fbd6420745c01ffb5e3246a2e93e13d2fd62aca27 · 1 policies · Sepolia
POLICY ID
0x546b36b8…ca27
REVISION
1
POLICIES
1
RESPONSE EXPIRY
25 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 25 blocks after its reference block — the shortest expireAfter in the set, on slot 0.

Policies — 1

one Rego + WASM pair per slot
  1. 0
    0x73b70f3a3029f0b9d99eec49e28ce00830afb8260x73b7…b826not in factory registry25 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x28659b8e…
    whitelistnot in schema0x86fd1c9aa583c3cf10d8224af9747ee4724084f0
    policyParams — 58 bytes on chain0x7b2277686974656c697374223a22307838366664316339616135383363336366313064383232346166393734376565343732343038346630227d
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.