NEWTON PROTOCOL · POLICY SET
0x9db3…80fb · revision 1current
0x263423085c94ee94b3985b1a656ab88ba83b67d1759d6162043b9a74cdd1de0e · 1 policies · Sepolia
POLICY ID
0x26342308…de0e
CLIENT
REVISION
1
POLICIES
1
RESPONSE EXPIRY
25 blocks
CHAIN
Sepolia
TASKS
0
ALLOW RATE
—
Policies — 1
one Rego + WASM pair per slot- 00x73b70f3a3029f0b9d99eec49e28ce00830afb8260x73b7…b826not in factory registry25 blocksbounds set expirywhitelistnot in schema0x9db35e7cf7913654c5099f6a9c91e40d2db880fb
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307839646233356537636637393133363534633530393966366139633931653430643264623838306662227d
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.