NEWTON PROTOCOL · POLICY SET
0x5f75…6880 · revision 19current
0x6f3034508b1fd3ceedb54ac707c2881665002fb63e56d27041253045635cccc2 · 1 policies · Sepolia
POLICY ID
0x6f303450…ccc2
CLIENT
REVISION
19
POLICIES
1
RESPONSE EXPIRY
300 blocks
CHAIN
Sepolia
TASKS
0
ALLOW RATE
—
Policies — 1
one Rego + WASM pair per slot- 00xb019e3e7ec715b0e353454722e51b7b7b288bc410xb019…bc41not in factory registry300 blocksbounds set expirylistnot in schema0x3f21e39EC62Cc2b201883CFFc18852B5203bDeCbswap_selectornot in schema0x9d555cf7threshold_hexnot in schema0000000000000000000000000000000000000000000000000000000000000000deposit_selectornot in schema0xf08a814e
policyParams — 197 bytes on chain
0x7b22737761705f73656c6563746f72223a2230783964353535636637222c226465706f7369745f73656c6563746f72223a2230786630386138313465222c227468726573686f6c645f686578223a2230303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030222c226c697374223a22307833663231653339454336324363326232303138383343464663313838353242353230336244654362227d
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.