LIVE
TASKS 24H065 policiesCOMPLIANT0.0%0 attestedOPERATORS32 signingRESTAKED4e-15 NEWT—MEDIAN RESPONSE36sp99 48.0sRE-VERIFIED 24H—0 invalidatedBLOCK11,959,393Sepolia
NEWTON PROTOCOL · POLICY SET

0x12e8…13b6 · revision 3superseded

0xcf6b6fb63f927527ba4e6a0767771018071a740ed3aaf59b7fb7b82dab82fe71 · 2 policies · Sepolia
Superseded. Every attestation minted against this policyId was revoked when the client wrote its next revision on 2026-09-30 — regardless of expiry block, because the client’s policyId no longer matches this one. Tasks created under it still replay correctly: each carries this exact set as its own frozen snapshot, and replay proves it by recomputing the id. Replaced by 0xc2d17e57…ff98 →
POLICY ID
0xcf6b6fb6…fe71
REVISION
3
POLICIES
2
RESPONSE EXPIRY
50,000 blocks
CHAIN
Sepolia
TASKS
0
ALLOW RATE
—
Every policy must allowFail-closed, and no short-circuit: every policy is evaluated even after one has denied, and a single denial denies the intent. The response expires 50,000 blocks after its reference block — the shortest expireAfter in the set, on slot 0 and 1.

Policies — 2

one Rego + WASM pair per slot
  1. 0
    0xfaa90272072e0865dc995a3beacf2d0358abe2b50xfaa9…e2b5not in factory registry50,000 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0xc834c184…
    apy_z_maxnot in schema4
    risk_score_floornot in schema60
    deny_on_corruptednot in schematrue
    deny_on_critical_flagnot in schematrue
    tvl_drawdown_7d_max_pctnot in schema50
    tvl_drawdown_24h_max_pctnot in schema25
    deny_on_allocation_changenot in schematrue
    policyParams — 183 bytes on chain0x7b226170795f7a5f6d6178223a342c2264656e795f6f6e5f616c6c6f636174696f6e5f6368616e6765223a747275652c2264656e795f6f6e5f636f72727570746564223a747275652c2264656e795f6f6e5f637269746963616c5f666c6167223a747275652c227269736b5f73636f72655f666c6f6f72223a36302c2274766c5f64726177646f776e5f3234685f6d61785f706374223a32352c2274766c5f64726177646f776e5f37645f6d61785f706374223a35307d
  2. 1
    0x70b9e9cd537c8f76b2bdfb70015e7dd0908215990x70b9…1599not in factory registry50,000 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0xca24e5ff…
    max_abs_dev_pctnot in schema0.005
    deny_on_collapsednot in schematrue
    deny_on_stale_datanot in schematrue
    max_recent_depeg_eventsnot in schema2
    max_consecutive_days_below_pegnot in schema3
    policyParams — 139 bytes on chain0x7b2264656e795f6f6e5f636f6c6c6170736564223a747275652c2264656e795f6f6e5f7374616c655f64617461223a747275652c226d61785f6162735f6465765f706374223a302e3030352c226d61785f636f6e73656375746976655f646179735f62656c6f775f706567223a332c226d61785f726563656e745f64657065675f6576656e7473223a327d
Each module is evaluated against its own input — {"params": <this slot’s policyParams>, "wasm": <this slot’s WASM output>}. There is no shared data.wasm object and no cross-slot namespace, so slot 1 cannot read slot 0’s WASM output and a policy cannot be written to depend on its neighbours.

Tasks bound to this set

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.