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

0xed88…1888revision 1 · current

0xed888689cd2d3bf7aed292e84bfcef5a82a01888 · 1 of 8 policies · Sepolia
POLICY ID
0x9a4bff2c…8299
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
    0xee0268755e6728f28155acf801bbc20da72020ae0xee02…20aenot in factory registry25 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x2bc7cc4f…
    fundnot in schema0xa6bdc5a8825d5b96badb8f91d37a7c4a3fd860a7
    whitelistnot in schema0x3c9b230b8f6a8224a9065a0292ed962d13cedd5f
    policyParams — 110 bytes on chain0x7b2277686974656c697374223a22307833633962323330623866366138323234613930363561303239326564393632643133636564643566222c2266756e64223a22307861366264633561383832356435623936626164623866393164333761376334613366643836306137227d
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
policyId0x9a4bff2c65a3e6928b29966d2818344968b78f1ba903912ca35fa7b5a1468299
POLICY_SET_DOMAINkeccak256("newton.policy.set")
chainId11155111
policyClient0xed888689cd2d3bf7aed292e84bfcef5a82a01888
revision1
policies0xee02…20ae@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 · current0x9a4bff2c…8299first set0xee0268755e6728f28155acf801bbc20da72020ae—11,914,0920xc549…918d0
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.