NEWTON / EXPLORER
MAINNET
LIVE
TASKS 24H08 policiesCOMPLIANT0.0%0 attestedOPERATORS22 signingRESTAKED4e-15 NEWT—MEDIAN RESPONSE——RE-VERIFIED 24H—0 invalidatedBLOCK26,236,223Ethereum
NEWTON PROTOCOL · POLICY CLIENT

0x69af…91c0revision 0 · current

0x69afa67e81345868673a7dc5cfce01cc924491c0 · 0 of 8 policies · Ethereum
POLICY ID
0x71a86d1f…b74f
REVISION
0 of 0
POLICIES
0 of 8
DISTINCT
0
RESPONSE EXPIRY
0 blocks
CHAIN
Ethereum
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 0 blocks after its reference block — the shortest expireAfter in the set, on slot .

Policies — 0

one Rego + WASM pair per slot
    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
    policyId0x71a86d1f51d3a1e8e78c2a819e2a97f2b2295eac59d63e21dd8766bc5373b74f
    POLICY_SET_DOMAINkeccak256("newton.policy.set")
    chainId1
    policyClient0x69afa67e81345868673a7dc5cfce01cc924491c0
    revision0
    policies
    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

    0 writes · newest first
    RevPolicy setChangePoliciesConfigured byBlockTasks
    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 0 is the only one whose attestations are still spendable.

    Task history — every revision

    12 of 12 matchingExport CSVJSON
    TaskSenderPolicyFunctionSignersResultAge
    0x2dbd30a9…0x5ff2…e4bd—0xdeadbeefNON-COMPLIANT57d 0h
    0xf48c84f7…0x5ff2…e4bd—0xNON-COMPLIANT57d 0h
    0xd5c57320…0x5ff2…e4bd—0xNON-COMPLIANT57d 13h
    0x5f9f7592…0x5ff2…e4bd—0xNON-COMPLIANT57d 13h
    0x65fc0747…0x5ff2…e4bd—0xNON-COMPLIANT57d 13h
    0x7ce5f4cc…0x5ff2…e4bd—0xNON-COMPLIANT57d 13h
    0xc01a9a62…0x5ff2…e4bd—0xNON-COMPLIANT57d 16h
    0x0e02619c…0x5ff2…e4bd—0xNON-COMPLIANT57d 16h
    0x5c46e67d…0x5ff2…e4bd—0xNON-COMPLIANT57d 18h
    0x5abf743c…0x5ff2…e4bd—0xNON-COMPLIANT57d 18h
    0xd3837ceb…0x5ff2…e4bd—0xNON-COMPLIANT64d 5h
    0x0ac7b704…0x5ff2…e4bd0x65786563757465486f6f6b732828616464726573735b5d2c62797465735b5d2c75696e743235365b5d2c627974657333325b5d5b5d2c627974657333325b5d5b5d2929NON-COMPLIANT95d 0h
    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.