NEWTON / EXPLORER
TESTNET
LIVE
TASKS 24H6,48165 policiesCOMPLIANT0.0%0 attestedOPERATORS32 signingRESTAKED4e-15 NEWT—MEDIAN RESPONSE36sp99 48.0sRE-VERIFIED 24H—0 invalidatedBLOCK11,957,720Sepolia
NEWTON PROTOCOL · POLICY SET

0xbf07…7149 · revision 1current

0x0947378597ba171d2bc3793291e6e6fcffae688d4ba02e63849e6c94457728b9 · 1 policies · Sepolia
POLICY ID
0x09473785…28b9
CLIENT
0xbf07…7149
REVISION
1
POLICIES
1
RESPONSE EXPIRY
25 blocks
CHAIN
Sepolia
TASKS
6
ALLOW RATE
50.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 25 blocks after its reference block — the shortest expireAfter in the set, on slot 0.

Policies — 1

one Rego + WASM pair per slot
  1. 0
    0x6cc19a9cb5b90f8065886aaf744049a276755c840x6cc1…5c84not in factory registry25 blocksbounds set expiry
    wasmnone — pure Regorego
    — rules— denyno WASMspecHash 0xebefd96c…
    check_kycnot in schemafalse
    check_ofacnot in schemafalse
    check_fraudnot in schematrue
    policyParams — 58 bytes on chain0x7b22636865636b5f6f666163223a66616c73652c22636865636b5f6b7963223a66616c73652c22636865636b5f6672617564223a747275657d0a
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.

Tasks bound to this set

6 of 6 matchingExport CSVJSON
TaskSenderFunctionSignersResultAge
0x1cb2ffb7…0x0000…0001mint(address,uint256)2COMPLIANT11d 21h
0x321b3666…0x0000…0001mint(address,uint256)2NON-COMPLIANT11d 21h
0xcd8b8a34…0x0000…0001mint(address,uint256)2COMPLIANT18d 3h
0xfc5d1ce5…0x0000…0001mint(address,uint256)2NON-COMPLIANT18d 3h
0x80e17f9f…0x0000…0001mint(address,uint256)2NON-COMPLIANT20d 0h
0x4ea680e5…0x0000…0001mint(address,uint256)2COMPLIANT20d 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.