NEWTON / EXPLORER
TESTNET
LIVE
TASKS 24H365 policiesCOMPLIANT100.0%0 attestedOPERATORS32 signingRESTAKED0.04 NEWT—MEDIAN RESPONSE36sp99 36.0sRE-VERIFIED 24H—0 invalidatedBLOCK11,958,371Sepolia
NEWTON PROTOCOL · POLICY CLIENT

0x5105…7fa6revision 2 · superseded

0x51054ed0a36f216f5ff57428e9581fae67be7fa6 · 2 of 8 policies · Sepolia
Revision 2 is superseded. Every attestation minted against 0x126dde1a…4a9c was revoked when revision 3 landed on 2026-10-07 — regardless of its expiry block, because the client’s policyId no longer matches. Tasks created under it still replay correctly: each one carries this exact set as its own frozen snapshot. See revision 3, the current set →
POLICY ID
0x126dde1a…4a9c
REVISION
2 of 3
POLICIES
2 of 8
DISTINCT
2
RESPONSE EXPIRY
7,200 blocks
CHAIN
Sepolia
TASKS · 24H
—
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 7,200 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
    loadtest_intent0xa572…08057,200 blocksbounds set expiry
    wasmnone — pure Regoregoloadtest_intent.allow
    0 rules0 denyno WASMspecHash 0x04528db1…
    token0xe42e3458283032c669c98e0d8f883a92fc64fe22
    target0xb1ad5f82407bc0f19f42b2614fb9083035a36b69
    chain_id11155111
    max_amount100000000000
    max_slippage2
    policyParams — 173 bytes on chain0x7b22636861696e5f6964223a223131313535313131222c226d61785f616d6f756e74223a3130303030303030303030302c226d61785f736c697070616765223a322c22746172676574223a22307862316164356638323430376263306631396634326232363134666239303833303335613336623639222c22746f6b656e223a22307865343265333435383238333033326336363963393865306438663838336139326663363466653232227d
  2. 1
    loadtest_risk0x196e…8b0e7,200 blocksbounds set expiry
    wasmbafkreihz7xu6fjzooxnlj6zxwdnusatqbmlcmfz5hhsqezrlsfacofgtzmregoloadtest_risk.allow
    0 rules0 denyWASMspecHash 0x0effe881…
    max_score50
    source_versionv1
    policyParams — 38 bytes on chain0x7b226d61785f73636f7265223a35302c22736f757263655f76657273696f6e223a227631227d
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.
SET IDENTITY
policyId0x126dde1a07ccd6cd1e6fdd0da67b35decbf31fb726a6e9808fb94c85735e4a9c
POLICY_SET_DOMAINkeccak256("newton.policy.set")
chainId11155111
policyClient0x51054ed0a36f216f5ff57428e9581fae67be7fa6
revision2
policies0xa572…0805@7200, 0x196e…8b0e@7200
Task managerreads getPolicies() at task creation, then never again
policyId = keccak256(abi.encode(POLICY_SET_DOMAIN, chainId, client, revision, policies)), where policies is the complete ordered array with each entry’s parameters and expiry. Order is part of it, so a reorder alone is a new id.
WHAT A TASK FREEZES
A task carries this exact ordered set as its own snapshot, plus one WASM input per slot. Response validation reads that snapshot and never re-reads the client, so reconfiguring mid-flight cannot change what an in-flight task means — and replay proves it by recomputing the policyId over the snapshot and comparing against the task’s own.
The bound is MAX_POLICIES = 8, enforced on chain and mirrored in the operator, the enclave and the proof guest. An oversize set is rejected, never truncated, and an empty one is rejected too — there is no vacuous allow.

Tasks under revision 2

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.