NEWTON / EXPLORER
TESTNET
LIVE
TASKS 24H065 policiesCOMPLIANT0.0%0 attestedOPERATORS32 signingRESTAKED4e-15 NEWT—MEDIAN RESPONSE36sp99 48.0sRE-VERIFIED 24H—0 invalidatedBLOCK11,958,298Sepolia
NEWTON PROTOCOL · POLICY CLIENT

0x7a0c…34afrevision 1 · current

0x7a0c93085e161747b39e8461f40761543a9534af · 1 of 8 policies · Sepolia
POLICY ID
0xddd07da7…6146
REVISION
1 of 1
POLICIES
1 of 8
DISTINCT
1
RESPONSE EXPIRY
25 blocks
CHAIN
Sepolia
TASKS · 24H
0
ALLOW RATE
100.0%
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
    0x73b70f3a3029f0b9d99eec49e28ce00830afb8260x73b7…b826not in factory registry25 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x45ea5373…
    whitelistnot in schema0x7a0c93085e161747b39e8461f40761543a9534af
    policyParams — 58 bytes on chain0x7b2277686974656c697374223a22307837613063393330383565313631373437623339653834363166343037363135343361393533346166227d
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
policyId0xddd07da72e0c3b2f65f7788b160707233718eb6785d0cbfad4b72b34a3e06146
POLICY_SET_DOMAINkeccak256("newton.policy.set")
chainId11155111
policyClient0x7a0c93085e161747b39e8461f40761543a9534af
revision1
policies0x73b7…b826@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 · current0xddd07da7…6146first set0x73b70f3a3029f0b9d99eec49e28ce00830afb826—11,924,0160x4790…845f2
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

2 of 2 matchingExport CSVJSON
TaskSenderPolicyFunctionSignersResultAge
0x5e8e6c8c…0xdde0…73ad0x73b70f3a3029f0b9d99eec49e28ce00830afb826admit()2COMPLIANT4d 21h
0x88fab951…0xdde0…73ad0x73b70f3a3029f0b9d99eec49e28ce00830afb826admit()2COMPLIANT4d 21h
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.