NEWTON PROTOCOL · POLICY SET
0xded0…028f · revision 1current
0x127fbc761e257f09f412123a7f4ca6e8bc1a00642ebccb1d14810cc6da4099a0 · 1 policies · Sepolia
POLICY ID
0x127fbc76…99a0
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 schema0xded0d1100f2a52b2eeb28485c228231d91b6028f
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307864656430643131303066326135326232656562323834383563323238323331643931623630323866227d
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 |
|---|---|---|---|---|---|
| 0xf8cf3e3c… | 0xe597…d07c | admit() | 2 | COMPLIANT | 4d 21h |
| 0xa2171446… | 0xe597…d07c | admit() | 2 | COMPLIANT | 4d 21h |
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.