NEWTON PROTOCOL · POLICY SET
0xd715…fa4d · revision 1current
0xd563972300403a8c30b3234c597ac102f44bfc5ee73c74aeff266fc284b582e6 · 1 policies · Sepolia
POLICY ID
0xd5639723…82e6
CLIENT
REVISION
1
POLICIES
1
RESPONSE EXPIRY
300 blocks
CHAIN
Sepolia
TASKS
0
ALLOW RATE
—
Policies — 1
one Rego + WASM pair per slot- 00x8e85d2bf7f55b741cb3301efcc3c2b094b7301c80x8e85…01c8not in factory registry300 blocksbounds set expirywhitelistnot in schema0x798a410b898c0af367e789a00efae4296c4ed984
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307837393861343130623839386330616633363765373839613030656661653432393663346564393834227d
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.