Network Compliance Oracle
Real-time, network-wide compliance signals attached to verified participants and digital asset movement.
For VASPs, regulated institutions, and blockchain integrators that require deterministic, on-chain compliance, not off-chain, point-in-time checks.
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.
Compliance state, coordinated across the network.
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.
Continuous screening and policy state
BlockTravel runs sanctions screening, counterparty discovery and policy evaluation continuously, not at transfer time alone. Status changes — new sanctions, revoked attestations, flagged counterparties — emit signals as they occur.
Network-wide signal propagation
Status changes propagate to every participating institution in real time. The signal is the same for every party in the network; there is no cached private view. Each institution operates against the network’s coordinated state, not its own ageing one.
Oracle query interface
Any participating institution can query the network’s current compliance state for any counterparty, on demand. The Oracle returns the live coordinated state — not a probability, not a snapshot, not a private cache.
Two layers of the architecture, coordinated as one network signal.
01 — Identity Trust
BlockID
Verify the participant.
02 — Payment Control
BlockPay
Govern the transaction.
03 — Digital Asset Transfer Compliance
BlockTravel
Enable compliant movement.
04 — Settlement Certainty
BlockSettle
Settle with confidence.
The Network Compliance Oracle is the live coordination of BlockID’s verified participant layer and BlockTravel’s transfer compliance layer. Verified state from BlockID propagates through the network. Live screening signals from BlockTravel attach to participants, transactions and chain addresses. Any institution participating in the network can query the current state — not its own cached view, but the network’s coordinated state.
Inherited from BlockID and BlockTravel.
- FCA
- MiCA
- FATF
- GDPR
- MAS
- IVMS 101
- OpenAPI 3.0
- OAuth2
- mTLS
The Network Compliance Oracle inherits the regulatory and technical standards of BlockID and BlockTravel. IVMS 101 is the canonical interVASP message standard underpinning network-wide propagation. The oracle exposes the coordinated state via the same API contract used by each underlying product.
Two products, one coordinated signal.
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.