LIVE
TASKS 24H265 policiesCOMPLIANT100.0%0 attestedOPERATORS32 signingRESTAKED0.04 NEWT—MEDIAN RESPONSE36sp99 36.0sRE-VERIFIED 24H—0 invalidatedBLOCK11,957,711Sepolia
NEWTON PROTOCOL · POLICY ARTIFACT

0x755dcc4af0c9813d1c4ba61b991b1bb0dfc13771

· · — · Pure Rego
Rego source unavailable.
ARTIFACT — IMMUTABLE
Policy address0x755dcc4af0c9813d1c4ba61b991b1bb0dfc13771
ChainSepolia · 11155111
Package—
Entrypoint—
policyCid—
policyCodeHash—
Rego sha-256—
schemaCid—
wasmCid— empty · pure Rego
secretsSchemaCid— none
metadataCid—
Rules—
Factory0x8dd5984f8f626a2fd1c61872217d1f8269a831da · 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
ClientPolicy setRevisionSlot
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 CSVJSON
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.