BlockID BlockTravel

Network Compliance Oracle

Real-time, network-wide screening state for digital asset movement from BlockTravel, plus reusable participant verification from BlockID where you need it.

For VASPs, regulated institutions, and blockchain integrators that need live, queryable compliance state, not point-in-time checks.

The problem

Compliance state is off-chain, fragmented, and ageing.

Today, compliance is executed off-chain and point-in-time. An institution verifies a counterparty, assigns a status, and relies on that status until the next refresh, often delayed, inconsistent, or never triggered.

Three structural problems compound. Stale state: every institution carries its own ageing view of every counterparty it has ever verified. Inconsistent posture: the same counterparty rated differently by every institution they touch. No network effects: compliance does not compound across the network even though every institution is processing similar signals.

VASPs and regulated institutions running multi-counterparty operations feel this most acutely. Each transaction carries the cost of the network’s fragmented state. Point-in-time compliance is a structural cost of fragmented infrastructure, not a vendor-selection problem.

The solution

BlockTravel’s network state, queryable in real time.

01
BlockID

Verified, reusable participant attestations

BlockID issues auditable, cross-jurisdictional attestations for every verified participant. The same attestation is referenced by every participating institution: one verification, one canonical record.

02
BlockTravel

Continuous screening and policy state

BlockTravel’s Agentic Compliance runs sanctions screening, counterparty discovery and policy evaluation continuously, not at transfer time alone. Status changes, such as new sanctions, revoked attestations or flagged counterparties, emit signals as they occur.

03
BlockTravel

Network-wide screening state

BlockTravel’s compliance verdicts for counterparties and transactions are kept current across the network. Each institution queries BlockTravel’s live state on demand, rather than relying on its own ageing records.

04
BlockTravel

Oracle query interface

Any participating institution can query BlockTravel’s current screening state for any counterparty or transaction, on demand, through a single API. The Oracle returns the live state, not a stale snapshot. Where an institution also needs verified participant detail, BlockID separately provides reusable attestations it can reference on its own terms.

Architecture in action

BlockTravel’s network state, and BlockID’s reusable verification: two independent controls.

The Network Compliance Oracle runs on BlockTravel’s own network-wide screening state. BlockTravel evaluates sanctions, counterparty risk and policy rules continuously, and its live verdicts attach to participants, transactions and chain addresses, queryable by any participating institution, in place of a private, ageing view. BlockID operates independently alongside it: institutions that also need verified participant detail can reference BlockID’s reusable attestations on their own terms, without the two products exchanging data.

Standards

Inherited from BlockID and BlockTravel.

Regulatory frameworks
  • FCA
  • MiCA
  • FATF
  • GDPR
  • MAS
Technical and security standards
  • IVMS 101
  • OpenAPI 3.0
  • OAuth2
  • mTLS

The Network Compliance Oracle inherits the regulatory and technical standards of BlockTravel, and BlockID’s wherever an institution also references its verification data. IVMS 101 is the interVASP data standard BlockTravel uses for Travel Rule transfer messaging. The Oracle exposes BlockTravel’s live state via its own API contract.

Work with us

Make your compliance state network-wide.

Design partners running operations across multiple counterparties get early access to the Network Compliance Oracle, a direct line to the build team, and influence over how network signals propagate. We ask for genuine integration intent, a structured feedback loop with named compliance and technical counterparts, and a mutual non-disclosure agreement.