0x5f75…6880 · revision 1 · Newton Explorer

Superseded. Every attestation minted against this policyId was revoked when the client wrote its next revision on 2026-09-29 — regardless of expiry block, because the client’s policyId no longer matches this one. Tasks created under it still replay correctly: each carries this exact set as its own frozen snapshot, and replay proves it by recomputing the id. Replaced by 0xbbc32111…21db →

POLICY ID

0xee3adddb…2535

CLIENT

0x5f75…6880

REVISION

POLICIES

RESPONSE EXPIRY

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

Policies — 1

one Rego + WASM pair per slot

0
0xcc3957c06472f9e599ed2eeba754d5854f23321b 0xcc39…321bnot in factory registry300 blocksbounds set expiry
wasmnone — pure Regorego
— rules— denyno WASMspecHash 0xaafb69da…
max_hopsnot in schema3
min_exposure_usdnot in schema0
policyParams — 35 bytes on chain
0x7b226d61785f686f7073223a332c226d696e5f6578706f737572655f757364223a307d

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.

0x5f75…6880 · revision 1superseded

Policies — 1

Tasks bound to this set