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

0x6ded…cf2arevision 1 · current

0x6ded0aca06d76fef4ec8254b8f661edbc387cf2a · 1 of 8 policies · Sepolia
POLICY ID
0xf4c070d6…6e5f
REVISION
1 of 1
POLICIES
1 of 8
DISTINCT
1
RESPONSE EXPIRY
300 blocks
CHAIN
Sepolia
TASKS · 24H
0
ALLOW RATE
0.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 300 blocks after its reference block — the shortest expireAfter in the set, on slot 0.

Policies — 1

one Rego + WASM pair per slot
  1. 0
    0xd0ff7aca199aeacc5f316b029a476da7684a38770xd0ff…3877not in factory registry300 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0x406f6dd0…
    max_list_age_secondsnot in schema691200
    policyParams — 36 bytes on chain0x7b0a2020226d61785f6c6973745f6167655f7365636f6e6473223a203639313230300a7d
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
policyId0xf4c070d68904581d2b646907770946c186512d423d9d3e57871b985813bb6e5f
POLICY_SET_DOMAINkeccak256("newton.policy.set")
chainId11155111
policyClient0x6ded0aca06d76fef4ec8254b8f661edbc387cf2a
revision1
policies0xd0ff…3877@300
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 · current0xf4c070d6…6e5ffirst set0xd0ff7aca199aeacc5f316b029a476da7684a3877—11,877,1720x23bf…cf812
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
0x5ec21840…0x5404…18080xNON-COMPLIANT11d 8h
0x3ef9d4a5…0x0ea1…2ae30xNON-COMPLIANT11d 8h
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.