NEWTON PROTOCOL · POLICY CLIENT
0x5105…7fa6revision 2 · superseded
0x51054ed0a36f216f5ff57428e9581fae67be7fa6 · 2 of 8 policies · Sepolia
Revision 2 is superseded. Every attestation minted against 0x126dde1a…4a9c was revoked when revision 3 landed on 2026-10-07 — regardless of its expiry block, because the client’s policyId no longer matches. Tasks created under it still replay correctly: each one carries this exact set as its own frozen snapshot. See revision 3, the current set →
POLICY ID
REVISION
2 of 3
POLICIES
2 of 8
DISTINCT
2
RESPONSE EXPIRY
7,200 blocks
CHAIN
Sepolia
TASKS · 24H
—
ALLOW RATE
—
Policies — 2
one Rego + WASM pair per slot- 00xa572044b393bcd1980330220a4dec66dabbb08050xa572…0805not in factory registry7,200 blocksbounds set expirytokennot in schema0xe42e3458283032c669c98e0d8f883a92fc64fe22targetnot in schema0xb1ad5f82407bc0f19f42b2614fb9083035a36b69chain_idnot in schema11155111max_amountnot in schema100000000000max_slippagenot in schema2
policyParams — 173 bytes on chain
0x7b22636861696e5f6964223a223131313535313131222c226d61785f616d6f756e74223a3130303030303030303030302c226d61785f736c697070616765223a322c22746172676574223a22307862316164356638323430376263306631396634326232363134666239303833303335613336623639222c22746f6b656e223a22307865343265333435383238333033326336363963393865306438663838336139326663363466653232227d - 10x196e1a2c89accae1a677df18d3739b849fef8b0e0x196e…8b0enot in factory registry7,200 blocksbounds set expirymax_scorenot in schema50source_versionnot in schemav1
policyParams — 38 bytes on chain
0x7b226d61785f73636f7265223a35302c22736f757263655f76657273696f6e223a227631227d
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 under revision 2
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.