NEWTON PROTOCOL · POLICY SET
0xf6d2…2985 · revision 1current
0x03a7db22993d22663210cb407694c31d25fb84d8b23c981f0475d3377738f5db · 1 policies · Sepolia
POLICY ID
0x03a7db22…f5db
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 schema0xf6d2204084c4c6bddf7d590af0dc613b14492985
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307866366432323034303834633463366264646637643539306166306463363133623134343932393835227d
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.