NEWTON PROTOCOL · POLICY SET
0xc6d5…5dc6 · revision 1current
0xc2de685f94da74bf53e98ab1ddb70a3d47ec7b2390b8297b6871d3af164f67d1 · 1 policies · Sepolia
POLICY ID
0xc2de685f…67d1
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 schema0xc6d57c9e90597f923b2c8fa282dc910e19c35dc6
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307863366435376339653930353937663932336232633866613238326463393130653139633335646336227d
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.