NEWTON PROTOCOL · POLICY SET
0xc7f1…db9a · revision 1current
0xfd7a865dd8257ca45b3ace2aadfbc38d711501a0c81c35c96d1f9963dcb07dbb · 1 policies · Sepolia
POLICY ID
0xfd7a865d…7dbb
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 schema0xc7f1be4456a59a43f28a47d1d2a2cf6e60a1db9a
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307863376631626534343536613539613433663238613437643164326132636636653630613164623961227d
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.