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

0x1785…aa16revision 1 · current

0x1785774f58618f874efcc19bc0e72c6ea2b4aa16 · 1 of 8 policies · Sepolia
POLICY ID
0x840b6e50…d16a
REVISION
1 of 1
POLICIES
1 of 8
DISTINCT
1
RESPONSE EXPIRY
25 blocks
CHAIN
Sepolia
TASKS · 24H
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 25 blocks after its reference block — the shortest expireAfter in the set, on slot 0.

Policies — 1

one Rego + WASM pair per slot
  1. 0
    0x59d46e1d98f4038cca022e719e7555319db4b9690x59d4…b969not in factory registry25 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x4ff975e7…
    adminnot in schema0xA6Bdc5A8825d5B96BadB8F91D37a7c4a3fD860a7
    allowed_chain_idsnot in schema[]
    allowed_contractsnot in schema[]
    allowed_functionsnot in schema[]
    policyParams — 123 bytes on chain0x7b2261646d696e223a22307841364264633541383832356435423936426164423846393144333761376334613366443836306137222c22616c6c6f7765645f636861696e5f696473223a5b5d2c22616c6c6f7765645f636f6e747261637473223a5b5d2c22616c6c6f7765645f66756e6374696f6e73223a5b5d7d
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
policyId0x840b6e50566d488e34d9693ad6103573f5482dc054fd86a59de42795e545d16a
POLICY_SET_DOMAINkeccak256("newton.policy.set")
chainId11155111
policyClient0x1785774f58618f874efcc19bc0e72c6ea2b4aa16
revision1
policies0x59d4…b969@25
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.

Configuration history

1 write · newest first
RevPolicy setChangePoliciesConfigured byBlockTasks
1 · current0x840b6e50…d16afirst set0x59d46e1d98f4038cca022e719e7555319db4b969—11,803,4000x1ca4…43b50
Every write mints a new policyId and revokes every attestation bound to the previous one, because the id commits the client, the chain, the revision counter and the exact ordered list — keccak256(POLICY_SET_DOMAIN, chainId, client, revision, policies). Revision 1 is the only one whose attestations are still spendable.

Task history — every revision

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.