NEWTON PROTOCOL · POLICY ARTIFACT
loadtest_risk
loadtest_risk · loadtest_risk · 0 rules · Rego + WASM
policy.regosha256 173d…6da3
1
package loadtest_risk2
3
import future.keywords4
5
default allow := false6
7
risk := data.wasm.risk8
9
allow if {10
not risk.error11
lower(risk.subject) == lower(input.from)12
risk.source_version == data.params.source_version13
risk.score <= data.params.max_score14
}0 rules · 0 deny · entrypoint loadtest_risk.allow · policyCodeHash 0x9d29…4cf9
Composed by
1 slot across 1 client| Client | Policy set | Revision | Slot |
|---|---|---|---|
| 0x5105…7fa60x5105…7fa6 | 0x94ec97f3…5293 | 3 | 1 |
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 |
|---|---|
| Base Sepolia | 0x0dcb65884b1bb3a2f4841652740d4a4ddbecbe2c |
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 CSVJSONThe 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.