NEWTON PROTOCOL · POLICY SET
0xed88…1888 · revision 1current
0x9a4bff2c65a3e6928b29966d2818344968b78f1ba903912ca35fa7b5a1468299 · 1 policies · Sepolia
POLICY ID
0x9a4bff2c…8299
CLIENT
REVISION
1
POLICIES
1
RESPONSE EXPIRY
25 blocks
CHAIN
Sepolia
TASKS
0
ALLOW RATE
—
Policies — 1
one Rego + WASM pair per slot- 00xee0268755e6728f28155acf801bbc20da72020ae0xee02…20aenot in factory registry25 blocksbounds set expiryfundnot in schema0xa6bdc5a8825d5b96badb8f91d37a7c4a3fd860a7whitelistnot in schema0x3c9b230b8f6a8224a9065a0292ed962d13cedd5f
policyParams — 110 bytes on chain
0x7b2277686974656c697374223a22307833633962323330623866366138323234613930363561303239326564393632643133636564643566222c2266756e64223a22307861366264633561383832356435623936626164623866393164333761376334613366643836306137227d
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.