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

0xcea2…8f1brevision 0 · current

0xcea2939913d04fc9533be04b66be234b04d58f1b · 0 of 8 policies · Sepolia
POLICY ID
0x9fc2d86c…b834
REVISION
0 of 0
POLICIES
0 of 8
DISTINCT
0
RESPONSE EXPIRY
0 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 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
    policyId0x9fc2d86c95058645cb4715e66ed5bcf8c54bbbd46cf6fb96008f29d749f7b834
    POLICY_SET_DOMAINkeccak256("newton.policy.set")
    chainId11155111
    policyClient0xcea2939913d04fc9533be04b66be234b04d58f1b
    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

    6 of 6 matchingExport CSVJSON
    TaskSenderPolicyFunctionSignersResultAge
    0x1451a749…0x0000…00990x62757928616464726573732c75696e743235362c75696e74333229NON-COMPLIANT4h 30m
    0xec56ca54…0x0000…00990x62757928616464726573732c75696e743235362c75696e74333229NON-COMPLIANT4h 30m
    0xb803c8f8…0x0000…00990x62757928616464726573732c75696e743235362c75696e74333229NON-COMPLIANT4h 30m
    0x03fd3b7f…0x0000…00990x62757928616464726573732c75696e743235362c75696e74333229NON-COMPLIANT4h 30m
    0x06e1c622…0x0000…00990x62757928616464726573732c75696e743235362c75696e74333229NON-COMPLIANT4h 30m
    0x3a5b9301…0x0000…00990x62757928616464726573732c75696e743235362c75696e74333229NON-COMPLIANT4h 30m
    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.