Travel Rule routing on rails you can ship.
Veriscope-based IVMS101 exchange today, with per-customer ECIES keys, wallet ownership proofs, incoming auto-claim, and a protocol adapter model for expansion.
Veriscope Direct routing
On-chain IVMS101 exchange via Shyft Network without a ta-node dependency.
ECIES per-customer keys
Customer keypairs are generated, encrypted at rest, and used for IVMS exchange.
Auto-claim incoming attestations
Incoming attestations are matched against the wallet registry and claimed automatically.
Wallet registry + ownership proofs
Proofs support self-hosted wallet detection and jurisdiction-specific handling.
Same API, growing protocol surface.
Counterparty networks should not dictate your product architecture. Covalent turns protocol differences into adapter behavior.
Wallet ownership becomes part of the compliance state.
Covalent can flag self-hosted or unhosted wallets and require ownership proof above a threshold, block in selected jurisdictions, or branch into analyst review.
Deploy Travel Rule routing without protocol lock-in.
Start with Veriscope, keep a stable Covalent API, and extend protocol coverage as counterparties require it.