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

0x41de…39e6revision 1 · superseded

0x41de0c896e90fe7837e11f8a6cf1a17a987239e6 · 1 of 8 policies · Sepolia
Revision 1 is superseded. Every attestation minted against 0x09846561…2a87 was revoked when revision 2 landed on 2026-10-13 — 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 2, the current set →
POLICY ID
0x09846561…2a87
REVISION
1 of 2
POLICIES
1 of 8
DISTINCT
1
RESPONSE EXPIRY
5 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 5 blocks after its reference block — the shortest expireAfter in the set, on slot 0.

Policies — 1

one Rego + WASM pair per slot
  1. 0
    0x3088b82aefa25f086889e992013633118707a9880x3088…a988not in factory registry5 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x001052b9…
    whitelistnot in schema0x546d2ccb9b5f8f1535010143945f9869835c55d9
    policyParams — 58 bytes on chain0x7b2277686974656c697374223a22307835343664326363623962356638663135333530313031343339343566393836393833356335356439227d
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
policyId0x0984656102dd8c39e7a0b94964cf9ae219680037ac3cd968e816eb9eb4f72a87
POLICY_SET_DOMAINkeccak256("newton.policy.set")
chainId11155111
policyClient0x41de0c896e90fe7837e11f8a6cf1a17a987239e6
revision1
policies0x3088…a988@5
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 1

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.