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

loadtest_risk

loadtest_risk · loadtest_risk · 0 rules · Rego + WASM
policy.regosha256 173d…6da3
1package loadtest_risk
2
3import future.keywords
4
5default allow := false
6
7risk := data.wasm.risk
8
9allow if {
10 not risk.error
11 lower(risk.subject) == lower(input.from)
12 risk.source_version == data.params.source_version
13 risk.score <= data.params.max_score
14}
0 rules · 0 deny · entrypoint loadtest_risk.allow · policyCodeHash 0x9d29…4cf9
ARTIFACT — IMMUTABLE
Policy address0x196e1a2c89accae1a677df18d3739b849fef8b0e
ChainSepolia · 11155111
Packageloadtest_risk
Entrypointloadtest_risk.allow
policyCidbafkreiaxhu4iagz3nwmxrpxe4sfrdjtczyntumv3vhkh5j6ljngex3tnum
policyCodeHash0x9d298e3f0ae6cd1a28cf8518c8fe16a0c128eb7db1a4899d2d113642dccd4cf9
Rego sha-256173d38801b3b6d9978bee4e48b11a662ce1b3a32bba9d47ea7cb4b4c4bee6da3
schemaCidbafkreibtexa3ntutjpca3z4dk6fkxzjcipejo5ynpuiqmr3tpud67buuv4
wasmCidbafkreihz7xu6fjzooxnlj6zxwdnusatqbmlcmfz5hhsqezrlsfacofgtzm
secretsSchemaCid— none
metadataCidbafkreiguevldjjr76jltadah4zimruuyeq6hlk5bsrmtc7liqfzfxljo5m
Rules0 · 0 deny
Factory0x8dd5984f8f626a2fd1c61872217d1f8269a831da · isPolicy true
Composed by1 client, 1 slot
PARAMS SCHEMA — data.params
KeyTypeRequired
max_scoreintegeryes
source_versionunknownyes
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-10-07 21:39:12 UTC · block —
Txc0f939…d4b6
Publisher0xd116…9312
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

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.

Same module, other chains

matched on policyCodeHash
ChainPolicy address
Base Sepolia0x0dcb65884b1bb3a2f4841652740d4a4ddbecbe2c
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

12 of 12 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.