NEWTON PROTOCOL · POLICY SET
0x41de…39e6 · revision 2current
0xe15dec3185497574d14ab03ea22ae20c452b91a0e627b9199b3b6165b265f3a5 · 1 policies · Sepolia
POLICY ID
0xe15dec31…f3a5
CLIENT
REVISION
2
POLICIES
1
RESPONSE EXPIRY
25 blocks
CHAIN
Sepolia
TASKS
1
ALLOW RATE
100.0%
Policies — 1
one Rego + WASM pair per slot- 00x3088b82aefa25f086889e992013633118707a9880x3088…a988not in factory registry25 blocksbounds set expirywhitelistnot in schema0x546d2ccb9b5f8f1535010143945f9869835c55d9
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307835343664326363623962356638663135333530313031343339343566393836393833356335356439227d
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
1 of 1 matchingExport CSVJSON| Task | Sender | Function | Signers | Result | Age |
|---|---|---|---|---|---|
| 0x7158cedc… | 0xa6bd…60a7 | redeem(uint256) | 2 | COMPLIANT | 6d 7h |
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.