0x73b70f3a3029f0b9d99eec49e28ce00830afb826

Rego source unavailable.

ARTIFACT — IMMUTABLE

Policy address0x73b70f3a3029f0b9d99eec49e28ce00830afb826

ChainSepolia · 11155111

Package—

Entrypoint—

policyCid—

policyCodeHash—

Rego sha-256—

schemaCid—

wasmCid— empty · pure Rego

secretsSchemaCid— none

metadataCid—

Rules—

Factory0x8dd5984f8f626a2fd1c61872217d1f8269a831da · isPolicy FALSE

Composed by11 clients, 11 slots

PARAMS SCHEMA — data.params

Schema unavailable.

These are the parameters a client must supply. The values are not here: they live in each client’s PolicyConfig.policyParams, and one policy bound twice in the same set carries two different sets of them. See the bindings below.

DEPLOYMENT

Deployed— · block —

Tx—

Publisher—

Immutable. The Rego CID, the code hash, the params schema CID and the WASM CID are written once at deployment and have no setters; the proxy exposes no upgrade path. Only metadataCid and secretsSchemaCid can be repointed, by the policy’s owner, and neither changes what the policy decides. Republishing mints a new address, not a new version — there is no predecessor field and no supersede event, so no lineage to show.

Composed by

11 slots across 11 clients

Client	Policy set	Revision
0x6a67…7e4d0x6a67…7e4d	0x66cc7b61…2a38	1
0xc34d…14630xc34d…1463	0x36458722…4fd8	1
0x79a5…88e10x79a5…88e1	0x4bf4f041…1356	1
0x243d…d8c40x243d…d8c4	0xb21ed27d…a2a0	1
0xc7f1…db9a0xc7f1…db9a	0xfd7a865d…7dbb	1
0x7a0c…34af0x7a0c…34af	0xddd07da7…6146	1
0xc6d5…5dc60xc6d5…5dc6	0xc2de685f…67d1	1
0xded0…028f0xded0…028f	0x127fbc76…99a0	1
0xf6d2…29850xf6d2…2985	0x03a7db22…f5db	1
0x9db3…80fb0x9db3…80fb	0x26342308…de0e	1
0x86fd…84f00x86fd…84f0	0x546b36b8…ca27	1

This policy has no allow rate of its own. Every set that includes it holds more than one policy, and TaskResponse.allowed is a single boolean for the whole set — so a denial names no culprit, and a per-policy rate would be invention.

Tasks running this policy

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.