NEWTON PROTOCOL · POLICY SET
0x6a67…7e4d · revision 1current
0x66cc7b61eb5da88a8b58706204e8cc95f89dd6cdec039b3c29221f494a272a38 · 1 policies · Sepolia
POLICY ID
0x66cc7b61…2a38
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 schema0x6a6789b63b05239d58e479ff7129289a20e97e4d
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307836613637383962363362303532333964353865343739666637313239323839613230653937653464227d
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.