NEWTON PROTOCOL · POLICY SET
0xfbb4…a1ee · revision 1current
0x58934ab7ac0eb39fb293524e2190eb6fde2856d0a2f1ca9b29daaafd373c9cb2 · 2 policies · Sepolia
POLICY ID
0x58934ab7…9cb2
CLIENT
REVISION
1
POLICIES
2
RESPONSE EXPIRY
25 blocks
CHAIN
Sepolia
TASKS
0
ALLOW RATE
—
Policies — 2
one Rego + WASM pair per slot- 00xff73354a3223ce9a915a0f9a6a8ce989bb3cba150xff73…ba15not in factory registry25 blocksbounds set expiry
policyParams — 2 bytes on chain
0x7b7d - 10x84db14f3d3b71a3656d33058544db5947afd735d0x84db…735dnot in factory registry25 blocksbounds set expiry
policyParams — 2 bytes on chain
0x7b7d
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.