0x1785…aa16 · revision 1 · Newton Explorer

POLICY ID

0x840b6e50…d16a

CLIENT

0x1785…aa16

REVISION

POLICIES

RESPONSE EXPIRY

25 blocks

CHAIN

Sepolia

TASKS

ALLOW RATE

66.7%

Every policy must allowFail-closed, and no short-circuit: every policy is evaluated even after one has denied, and a single denial denies the intent. The response expires 25 blocks after its reference block — the shortest expireAfter in the set, on slot 0.

Policies — 1

one Rego + WASM pair per slot

0
0x59d46e1d98f4038cca022e719e7555319db4b969 0x59d4…b969not in factory registry25 blocksbounds set expiry
wasmnone — pure Regorego
— rules— denyno WASMspecHash 0x4ff975e7…
adminnot in schema0xA6Bdc5A8825d5B96BadB8F91D37a7c4a3fD860a7
allowed_chain_idsnot in schema[]
allowed_contractsnot in schema[]
allowed_functionsnot in schema[]
policyParams — 123 bytes on chain
0x7b2261646d696e223a22307841364264633541383832356435423936426164423846393144333761376334613366443836306137222c22616c6c6f7765645f636861696e5f696473223a5b5d2c22616c6c6f7765645f636f6e747261637473223a5b5d2c22616c6c6f7765645f66756e6374696f6e73223a5b5d7d

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

3 of 3 matchingExport CSV JSON

Task	Sender	Function	Signers	Result	Age
0x2751d951…	0xa6bd…60a7	ping()	2	COMPLIANT	21d 23h
0x9cc54fbd…	0x0000…dead	ping()	2	NON-COMPLIANT	22d 0h
0x71dd5ac4…	0xa6bd…60a7	ping()	2	COMPLIANT	22d 0h

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.

0x1785…aa16 · revision 1current

Policies — 1

Tasks bound to this set