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

0x3220…aae7revision 1 · current

0x32209dc056cebf8990b2fbdffc9f12a958e4aae7 · 2 of 8 policies · Sepolia
POLICY ID
0x8fb13690…7ba5
REVISION
1 of 1
POLICIES
2 of 8
DISTINCT
2
RESPONSE EXPIRY
50 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 50 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
    0xa1cca533c467aff17f2226ed6dddbbb92d4745ef0xa1cc…45efnot in factory registry50 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0xdacd9bd7…
    max_abs_dev_pctnot in schema1
    deny_on_collapsednot in schematrue
    deny_on_stale_datanot in schematrue
    max_recent_depeg_eventsnot in schema2
    max_consecutive_days_below_pegnot in schema3
    policyParams — 135 bytes on chain0x7b2264656e795f6f6e5f636f6c6c6170736564223a747275652c2264656e795f6f6e5f7374616c655f64617461223a747275652c226d61785f6162735f6465765f706374223a312c226d61785f636f6e73656375746976655f646179735f62656c6f775f706567223a332c226d61785f726563656e745f64657065675f6576656e7473223a327d
  2. 1
    0x068d12614db2b7d097c85f9f649a419f113d2ace0x068d…2acenot in factory registry50 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0xa5497973…
    target_vaultnot in schema0x876a8c6310ce294f8caae2f4e84af12efb9c86f4
    policyParams — 61 bytes on chain0x7b227461726765745f7661756c74223a22307838373661386336333130636532393466386361616532663465383461663132656662396338366634227d
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
policyId0x8fb13690fdbab289e279351cec8ce1299723498ed7b4da6644325a0f4f017ba5
POLICY_SET_DOMAINkeccak256("newton.policy.set")
chainId11155111
policyClient0x32209dc056cebf8990b2fbdffc9f12a958e4aae7
revision1
policies0xa1cc…45ef@50, 0x068d…2ace@50
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 · current0x8fb13690…7ba5first set0xa1cca533c467aff17f2226ed6dddbbb92d4745ef · 0x068d12614db2b7d097c85f9f649a419f113d2ace—11,810,4360x4a64…dc560
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.