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

0xd789…397b · revision 1current

0x644483aa1111cc37d14c36432b19716801e97785b03c5feaac7df5bd2e554943 · 1 policies · Sepolia
POLICY ID
0x644483aa…4943
REVISION
1
POLICIES
1
RESPONSE EXPIRY
5 blocks
CHAIN
Sepolia
TASKS
4
ALLOW RATE
75.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 0xc4ef965e…
    whitelistnot in schema0x4afe34082e14a59d1e02a643358271636c8ee52f
    policyParams — 58 bytes on chain0x7b2277686974656c697374223a22307834616665333430383265313461353964316530326136343333353832373136333663386565353266227d
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

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