NEWTON PROTOCOL · POLICY SET
0xc34d…1463 · revision 1current
0x36458722abdf1f541c0c280928412478225bf737b3fdc49072e860d2f0304fd8 · 1 policies · Sepolia
POLICY ID
0x36458722…4fd8
CLIENT
REVISION
1
POLICIES
1
RESPONSE EXPIRY
25 blocks
CHAIN
Sepolia
TASKS
0
ALLOW RATE
—
Policies — 1
one Rego + WASM pair per slot- 00x73b70f3a3029f0b9d99eec49e28ce00830afb8260x73b7…b826not in factory registry25 blocksbounds set expirywhitelistnot in schema0xc34d1f360f8c44f37e5046642d2d1c738d501463
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307863333464316633363066386334346633376535303436363432643264316337333864353031343633227d
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.