NEWTON PROTOCOL · POLICY SET
0x8fe2…ebc5 · revision 1superseded
0xa7e8100621873406415285eca6e94f2127c4133405e0a6eae149b5840a1b1702 · 1 policies · Sepolia
Superseded. Every attestation minted against this policyId was revoked when the client wrote its next revision on 2026-10-06 — 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 0xfafa15f6…b84a →
POLICY ID
0xa7e81006…1702
CLIENT
REVISION
1
POLICIES
1
RESPONSE EXPIRY
50 blocks
CHAIN
Sepolia
TASKS
0
ALLOW RATE
—
Policies — 1
one Rego + WASM pair per slot- 00x811feaca33095f5fde8001ed401946e81322f10e0x811f…f10enot in factory registry50 blocksbounds set expiryexpected_ratifiernot in schema0x4cD178f4DF8244d9DA16a9ca56d9388e06f1aaB3max_cumulative_fill_limitnot in schema500000000000000000000000
policyParams — 121 bytes on chain
0x7b2265787065637465645f7261746966696572223a22307834634431373866344446383234346439444131366139636135366439333838653036663161614233222c226d61785f63756d756c61746976655f66696c6c5f6c696d6974223a22353030303030303030303030303030303030303030303030227d
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
no tasksExport CSVJSONNo tasks match this scope yet.
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.