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

0x156f…df2crevision 0 · current

0x156f61ca983cb97a3b6f6ac56474a7018fccdf2c · 0 of 8 policies · Ethereum
POLICY ID
…
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
    policyId
    POLICY_SET_DOMAINkeccak256("newton.policy.set")
    chainId1
    policyClient0x156f61ca983cb97a3b6f6ac56474a7018fccdf2c
    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

    4 of 4 matchingExport CSVJSON
    TaskSenderPolicyFunctionSignersResultAge
    0xc3b24b76…0xf39f…2266—0x62757928616464726573732c75696e743235362c75696e74333229NON-COMPLIANT137d 21h
    0xfe8cdc76…0xf39f…2266—0x62757928616464726573732c75696e743235362c75696e74333229NON-COMPLIANT137d 21h
    0xf0cb972f…0xf39f…2266—0x62757928616464726573732c75696e743235362c75696e74333229NON-COMPLIANT137d 21h
    0x5cec9026…0xf39f…2266—0x62757928616464726573732c75696e743235362c75696e74333229NON-COMPLIANT137d 22h
    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.