NEWTON PROTOCOL · POLICY SET
0xe4f1…0fd9 · revision 1current
0x5e89cdf815e7b59f10c1a5e447c93ddf4bfce10e2a36fac0a9436c61790d7b68 · 1 policies · Sepolia
POLICY ID
0x5e89cdf8…7b68
CLIENT
REVISION
1
POLICIES
1
RESPONSE EXPIRY
25 blocks
CHAIN
Sepolia
TASKS
0
ALLOW RATE
—
Policies — 1
one Rego + WASM pair per slot- 00x6cc19a9cb5b90f8065886aaf744049a276755c840x6cc1…5c84not in factory registry25 blocksbounds set expirycheck_kycnot in schematruecheck_ofacnot in schematruecheck_fraudnot in schemafalse
policyParams — 57 bytes on chain
0x7b22636865636b5f6f666163223a747275652c22636865636b5f6b7963223a747275652c22636865636b5f6672617564223a66616c73657d0a
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.