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

0x57f4…8d18 · revision 2superseded

0x34cb95f2ae987450ca92514253c08610a061dee8864eb51bc787b4d8729bacd0 · 1 policies · Sepolia
Superseded. Every attestation minted against this policyId was revoked when the client wrote its next revision on 2026-10-09 — 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 0x10596ed0…0a2c →
POLICY ID
0x34cb95f2…acd0
CLIENT
0x57f4…8d18
REVISION
2
POLICIES
1
RESPONSE EXPIRY
300 blocks
CHAIN
Sepolia
TASKS
2
ALLOW RATE
0.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 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
    0xd0ff7aca199aeacc5f316b029a476da7684a38770xd0ff…3877not in factory registry300 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x406f6dd0…
    max_list_age_secondsnot in schema691200
    policyParams — 36 bytes on chain0x7b0a2020226d61785f6c6973745f6167655f7365636f6e6473223a203639313230300a7d
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
0x38cdfe30…0x8b4b…1a480xNON-COMPLIANT11d 12h
0xe07103a4…0x8b4b…1a480xNON-COMPLIANT11d 12h
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.