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

loadtest_intent

loadtest_intent · loadtest_intent · 0 rules · Pure Rego
policy.regosha256 9ac6…0d72
1package loadtest_intent
2
3import future.keywords
4
5default allow := false
6
7allow if {
8 input.chain_id == data.params.chain_id
9 lower(input.to) == lower(data.params.target)
10 input.function.name == "buy"
11 lower(input.decoded_function_arguments[0]) == lower(data.params.token)
12 to_number(input.decoded_function_arguments[1]) <= data.params.max_amount
13 to_number(input.decoded_function_arguments[2]) <= data.params.max_slippage
14}
0 rules · 0 deny · entrypoint loadtest_intent.allow · policyCodeHash 0x885e…e445
ARTIFACT — IMMUTABLE
Policy address0xdddb457aec77cfc57b381001d4511f93b45abddc
ChainSepolia · 11155111
Packageloadtest_intent
Entrypointloadtest_intent.allow
policyCidbafkreie2yzd7aq6vftwhug5mhnylomquixqo3ayz73audrbtiuxuspinoi
policyCodeHash0x885e848a82b36b29d2bee428225ac4614eb1d06fdd4f00dfeb7a666f8910e445
Rego sha-2569ac647f043d52cec7a1bac3b70b7321445e0ed8319fec141c433452f493d0d72
schemaCidbafkreie7mwadj4e537574naznwdbtaspjru2ypcjlatobfla3pv3auc63q
wasmCid— empty · pure Rego
secretsSchemaCid— none
metadataCidbafkreigjof2fg2w2d7egxlazpkkd6xxj7q2wytyhjxsm6ysdiptkzdf4oa
Rules0 · 0 deny
Factory0x8dd5984f8f626a2fd1c61872217d1f8269a831da · isPolicy true
Composed by1 client, 1 slot
PARAMS SCHEMA — data.params
KeyTypeRequired
tokenstringyes
targetstringyes
chain_idstringyes
max_amountintegeryes
max_slippageintegeryes
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:43:00 UTC · block —
Tx126d78…f29d
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
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.