0x8fe2…ebc5 · revision 2 · Newton Explorer

POLICY ID

0xfafa15f6…b84a

CLIENT

0x8fe2…ebc5

REVISION

POLICIES

RESPONSE EXPIRY

50 blocks

CHAIN

Sepolia

TASKS

ALLOW RATE

—

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 50 blocks after its reference block — the shortest expireAfter in the set, on slot 0.

Policies — 1

one Rego + WASM pair per slot

0
0x811feaca33095f5fde8001ed401946e81322f10e 0x811f…f10enot in factory registry50 blocksbounds set expiry
wasmnone — pure Regorego
— rules— denyno WASMspecHash 0x54b2004b…
expected_ratifiernot in schema0x4cD178f4DF8244d9DA16a9ca56d9388e06f1aaB3
max_cumulative_fill_limitnot in schema500000000000000000000000
policyParams — 121 bytes on chain
0x7b2265787065637465645f7261746966696572223a22307834634431373866344446383234346439444131366139636135366439333838653036663161614233222c226d61785f63756d756c61746976655f66696c6c5f6c696d6974223a22353030303030303030303030303030303030303030303030227d

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 CSV JSON

No 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.

0x8fe2…ebc5 · revision 2current

Policies — 1

Tasks bound to this set