NEWTON PROTOCOL · POLICY SET
0x243d…d8c4 · revision 1current
0xb21ed27d139155fca013687c43f80b80ec09e38a9b3fc6936c66ee684fb2a2a0 · 1 policies · Sepolia
POLICY ID
0xb21ed27d…a2a0
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 schema0x243d3a68f79cbb3be46ee47478b55ee3e00ed8c4
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307832343364336136386637396362623362653436656534373437386235356565336530306564386334227d
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 |
|---|---|---|---|---|---|
| 0xab796d7a… | 0x0f6e…dee5 | admit() | 2 | COMPLIANT | 4d 19h |
| 0x0f075929… | 0x0f6e…dee5 | admit() | 2 | COMPLIANT | 4d 19h |
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.