0x95c66b29db62136094dc95e40c33cc524cfe4ba1

Rego source unavailable.

ARTIFACT — IMMUTABLE

Policy address0x95c66b29db62136094dc95e40c33cc524cfe4ba1

ChainSepolia · 11155111

Package—

Entrypointnewton_sanctions.allow

policyCidbafkreigvmehmguzwvy3wla2q56jk25jpfog3ecuym5v6cquoeocjodhqri

policyCodeHash0x4d462159a5125fda8d4919855d77447a6614a8d8febb9d0cf0881c1482021aab

Rego sha-256—

schemaCidbafkreiav7whatgtbfd3ufep5datnkadzvs3dmzqmior76fba4z5kit44bm

wasmCid— empty · pure Rego

secretsSchemaCid— none

metadataCidbafkreihvzo27j33hqs6kyesynqeaupfrhzvqddknbnm3jo4rtyh257dvta

Rules—

Factory0x8dd5984f8f626a2fd1c61872217d1f8269a831da · isPolicy true

Composed byno client yet

PARAMS SCHEMA — data.params

This policy’s schema declares no parameters.

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

Deployed2026-09-28 08:32:48 UTC · block —

Tx1ca595…3b8d

Publisher0x8b4b…1a48

Implementationv0.7.0

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

no client set includes this policy

No client has bound this policy. Its address has to appear in a client’s ordered PolicySpec[] before it can decide anything.

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.

Same module, other chains

matched on policyCodeHash

Chain	Policy address
Sepolia	0xde5315776f0f1742308d47071387446095b26e56

A separate deployment, not a link the protocol knows about: each chain runs its own factory, so identical bytes land at unrelated addresses and neither contract references the other.

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.