LIVE
TASKS 24H08 policiesCOMPLIANT0.0%0 attestedOPERATORS22 signingRESTAKED2k NEWT—MEDIAN RESPONSE——RE-VERIFIED 24H—0 invalidatedBLOCK26,235,938Ethereum
NEWTON PROTOCOL · POLICY CLIENT

0x61fc…ad37revision 1 · current

0x61fcddf1c8d08867ab62a12ca0c054d2e648ad37 · 1 of 8 policies · Ethereum
REVISION
1 of 1
POLICIES
1 of 8
DISTINCT
1
RESPONSE EXPIRY
60 blocks
CHAIN
Ethereum
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 60 blocks after its reference block — the shortest expireAfter in the set, on slot 0.

Policies — 1

one Rego + WASM pair per slot
  1. 0
    0xdeffd83760a963c9368f2337b26ac979ae285cb50xdeff…5cb5not in factory registry60 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0xf905091e…
    adminnot in schema0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266
    allowed_actionsnot in schema{"1": {"address": "0xb1ad5f82407bc0f19f42b2614fb9083035a36b69", "max_limit": 1000000000000000000, "function_name": "buy"}}
    token_whitelistnot in schema{"1": {"symbol": "WBTC", "address": "0xe42e3458283032c669c98e0d8f883a92fc64fe22", "max_limit": 1000000000000000000}}
    policyParams — 408 bytes on chain0x7b0a20202261646d696e223a2022307866333966643665353161616438386636663463653661623838323732373963666666623932323636222c0a202022616c6c6f7765645f616374696f6e73223a207b0a202020202231223a207b0a2020202020202261646472657373223a2022307862316164356638323430376263306631396634326232363134666239303833303335613336623639222c0a2020202020202266756e6374696f6e5f6e616d65223a2022627579222c0a202020202020226d61785f6c696d6974223a20313030303030303030303030303030303030300a202020207d0a20207d2c0a202022746f6b656e5f77686974656c697374223a207b0a202020202231223a207b0a2020202020202261646472657373223a2022307865343265333435383238333033326336363963393865306438663838336139326663363466653232222c0a202020202020226d61785f6c696d6974223a20313030303030303030303030303030303030302c0a2020202020202273796d626f6c223a202257425443220a202020207d0a20207d0a7d0a
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
POLICY_SET_DOMAINkeccak256("newton.policy.set")
chainId1
revision1
policies0xdeff…5cb5@60
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 · current0xf53cbe04…c2a4first set0xdeffd83760a963c9368f2337b26ac979ae285cb5—26,057,7440x2ff6…5de30
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.