NEWTON PROTOCOL · POLICY SET
0xd7fd…a421 · revision 1current
0x185e3687447810b4a41fd52212ff022266585642f53fd9c5d68e7627a871030c · 1 policies · Sepolia
POLICY ID
0x185e3687…030c
CLIENT
REVISION
1
POLICIES
1
RESPONSE EXPIRY
300 blocks
CHAIN
Sepolia
TASKS
0
ALLOW RATE
—
Policies — 1
one Rego + WASM pair per slot- 00x8e85d2bf7f55b741cb3301efcc3c2b094b7301c80x8e85…01c8not in factory registry300 blocksbounds set expirywhitelistnot in schema0xf886e8c4ebd15144171a7540a4f521f60de981e1
policyParams — 58 bytes on chain
0x7b2277686974656c697374223a22307866383836653863346562643135313434313731613735343061346635323166363064653938316531227d
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.