NEWTON PROTOCOL · POLICY SET
0x6ded…cf2a · revision 1current
0xf4c070d68904581d2b646907770946c186512d423d9d3e57871b985813bb6e5f · 1 policies · Sepolia
POLICY ID
0xf4c070d6…6e5f
CLIENT
REVISION
1
POLICIES
1
RESPONSE EXPIRY
300 blocks
CHAIN
Sepolia
TASKS
0
ALLOW RATE
—
Policies — 1
one Rego + WASM pair per slot- 0wasmbafkreicdyh43c5vv42iunlojjcsaoqvnbzpswqrgk22c2alqjinf55pkbmregonewton_redstone.allowmax_list_age_secondsnot in schema691200
policyParams — 36 bytes on chain
0x7b0a2020226d61785f6c6973745f6167655f7365636f6e6473223a203639313230300a7d
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.