0xdeffd83760a963c9368f2337b26ac979ae285cb5

Rego source unavailable.

ARTIFACT — IMMUTABLE

Policy address0xdeffd83760a963c9368f2337b26ac979ae285cb5

ChainEthereum · 1

Package—

Entrypoint—

policyCid—

policyCodeHash—

Rego sha-256—

schemaCid—

wasmCid— empty · pure Rego

secretsSchemaCid— none

metadataCid—

Rules—

Factory0x92f7b10ecabc3d87f32cfc0e1845253a1f2a43a6 · isPolicy FALSE

Composed by1 client, 1 slot

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

1 slot across 1 client

Client	Policy set	Revision	Slot
0x61fc…ad370x61fc…ad37	0xf53cbe04…c2a4	1	0

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.