NEWTON / EXPLORER
TESTNET
LIVE
TASKS 24H48,49969 policiesCOMPLIANT81.7%0 attestedOPERATORS32 signingRESTAKED4e-15 NEWT—MEDIAN RESPONSE36sp99 72.0sRE-VERIFIED 24H—0 invalidatedBLOCK11,965,833Sepolia
NEWTON PROTOCOL · POLICY SET

0x5f75…6880 · revision 15superseded

0xba029d2bb40b3633153ee63bc71ae335f09c9d9190b985f80a9fe0684646eb3d · 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 0x17c4a105…4356 →
POLICY ID
0xba029d2b…eb3d
CLIENT
0x5f75…6880
REVISION
15
POLICIES
2
RESPONSE EXPIRY
300 blocks
CHAIN
Sepolia
TASKS
1
ALLOW RATE
100.0%
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 300 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
    0xcc3957c06472f9e599ed2eeba754d5854f23321b0xcc39…321bnot in factory registry300 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0xaafb69da…
    max_hopsnot in schema3
    min_exposure_usdnot in schema0
    policyParams — 35 bytes on chain0x7b226d61785f686f7073223a332c226d696e5f6578706f737572655f757364223a307d
  2. 1
    0xa1ac0aef68ff48a383fe6ab17590a63a0b0ff08e0xa1ac…f08enot in factory registry300 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x664504ff…
    listnot in schema0x2614CdfC0119B509c0B98236545751Bc19DfcF22
    swap_selectornot in schema0x9d555cf7
    threshold_hexnot in schema0000000000000000000000000000000000000000000000000000000000000000
    deposit_selectornot in schema0xf08a814e
    policyParams — 197 bytes on chain0x7b22737761705f73656c6563746f72223a2230783964353535636637222c226465706f7369745f73656c6563746f72223a2230786630386138313465222c227468726573686f6c645f686578223a2230303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030222c226c697374223a22307832363134436466433031313942353039633042393832333635343537353142633139446663463232227d
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

1 of 1 matchingExport CSVJSON
TaskSenderFunctionSignersResultAge
0x33d9c49c…0xfb9f…0c0ffunction swap(address currency0, address currency1, uint24 fee, int24 tickSpacing, bool zeroForOne, bool exactInput, uint256 amount, uint160 sqrtPriceLimitX96)2COMPLIANT21d 8h
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.