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

0xd789…397brevision 1 · current

0xd78910cc6b8c810178d28463c063780822fa397b · 1 of 8 policies · Sepolia
POLICY ID
0x644483aa…4943
REVISION
1 of 1
POLICIES
1 of 8
DISTINCT
1
RESPONSE EXPIRY
5 blocks
CHAIN
Sepolia
TASKS · 24H
0
ALLOW RATE
75.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 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 0xc4ef965e…
    whitelistnot in schema0x4afe34082e14a59d1e02a643358271636c8ee52f
    policyParams — 58 bytes on chain0x7b2277686974656c697374223a22307834616665333430383265313461353964316530326136343333353832373136333663386565353266227d
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
policyId0x644483aa1111cc37d14c36432b19716801e97785b03c5feaac7df5bd2e554943
POLICY_SET_DOMAINkeccak256("newton.policy.set")
chainId11155111
policyClient0xd78910cc6b8c810178d28463c063780822fa397b
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.

Configuration history

1 write · newest first
RevPolicy setChangePoliciesConfigured byBlockTasks
1 · current0x644483aa…4943first set0x3088b82aefa25f086889e992013633118707a988—11,900,5650x4122…5ae94
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

4 of 4 matchingExport CSVJSON
TaskSenderPolicyFunctionSignersResultAge
0xe9b09ab5…0x53ad…aaad0x3088b82aefa25f086889e992013633118707a988redeem(uint256)2COMPLIANT8d 3h
0x72eecdce…0x53ad…aaad0x3088b82aefa25f086889e992013633118707a988redeem(uint256)2COMPLIANT8d 3h
0x9a4890b9…0x53ad…aaad0x3088b82aefa25f086889e992013633118707a988mint(uint256)2COMPLIANT8d 3h
0xa46b6562…0x53ad…aaad0x3088b82aefa25f086889e992013633118707a988mint(uint256)2NON-COMPLIANT8d 3h
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.