NEWTON PROTOCOL · POLICY SET
0x79a5…88e1 · revision 1current
0x4bf4f0419754155951a2078b3975d76624e9c1e7d9cef2eed07cf5e4dbaf1356 · 1 policies · Sepolia
POLICY ID
0x4bf4f041…1356
CLIENT
REVISION
1
POLICIES
1
RESPONSE EXPIRY
25 blocks
CHAIN
Sepolia
TASKS
2
ALLOW RATE
100.0%
Policies — 1
one Rego + WASM pair per slot- 00x73b70f3a3029f0b9d99eec49e28ce00830afb8260x73b7…b826not in factory registry25 blocksbounds set expirywhitelistnot in schema0x79a54de8e0ab7ab24e6a058d88019425611288e1
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307837396135346465386530616237616232346536613035386438383031393432353631313238386531227d
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
2 of 2 matchingExport CSVJSON| Task | Sender | Function | Signers | Result | Age |
|---|---|---|---|---|---|
| 0xcb2c2971… | 0x3163…9f95 | admit() | 2 | COMPLIANT | 4d 0h |
| 0x5ee26025… | 0x3163…9f95 | admit() | 2 | COMPLIANT | 4d 0h |
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.