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

0xfbb4…a1eerevision 1 · current

0xfbb4ab5e180c24cdbc554df76ae25ead0295a1ee · 2 of 8 policies · Sepolia
POLICY ID
0x58934ab7…9cb2
REVISION
1 of 1
POLICIES
2 of 8
DISTINCT
2
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 and 1.

Policies — 2

one Rego + WASM pair per slot
  1. 0
    0xff73354a3223ce9a915a0f9a6a8ce989bb3cba150xff73…ba15not in factory registry25 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x3879a4f8…
    policyParams — 2 bytes on chain0x7b7d
  2. 1
    0x84db14f3d3b71a3656d33058544db5947afd735d0x84db…735dnot in factory registry25 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x889bfcb2…
    policyParams — 2 bytes on chain0x7b7d
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
policyId0x58934ab7ac0eb39fb293524e2190eb6fde2856d0a2f1ca9b29daaafd373c9cb2
POLICY_SET_DOMAINkeccak256("newton.policy.set")
chainId11155111
policyClient0xfbb4ab5e180c24cdbc554df76ae25ead0295a1ee
revision1
policies0xff73…ba15@25, 0x84db…735d@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 · current0x58934ab7…9cb2first set0xff73354a3223ce9a915a0f9a6a8ce989bb3cba15 · 0x84db14f3d3b71a3656d33058544db5947afd735d—11,808,3010x89c2…abf90
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.