LIVE
TASKS 24H6,48165 policiesCOMPLIANT0.0%0 attestedOPERATORS32 signingRESTAKED4e-15 NEWT—MEDIAN RESPONSE36sp99 48.0sRE-VERIFIED 24H—0 invalidatedBLOCK11,958,016Sepolia
NEWTON PROTOCOL · POLICY ARTIFACT

0x59d46e1d98f4038cca022e719e7555319db4b969

· · — · Pure Rego
Rego source unavailable.
ARTIFACT — IMMUTABLE
Policy address0x59d46e1d98f4038cca022e719e7555319db4b969
ChainSepolia · 11155111
Package—
Entrypoint—
policyCid—
policyCodeHash—
Rego sha-256—
schemaCid—
wasmCid— empty · pure Rego
secretsSchemaCid— none
metadataCid—
Rules—
Factory0xe37952d9003d399579670e97b4c67b175112d0cd · isPolicy FALSE
Composed by4 clients, 4 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

4 slots across 4 clients
ClientPolicy setRevisionSlot
95.5% allowed — and this number is real only because a set that holds one policy makes the set’s verdict and the policy’s verdict the same thing.

Tasks running this policy

34 of 34 matchingExport CSVJSON
TaskSenderPolicyFunctionSignersResultAge
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.