Summary: Sygna Bridge is Travel Rule transport and verification plumbing. Its product surface is an API-first network for VASPs to exchange encrypted compliance data off-chain, verify counterparties, and run self-hosted-wallet checks before permitting normal blockchain transfers. Useful interoperability infrastructure, not a category anchor.
What it does:
Connects VASPs through an API-based Travel Rule messaging network designed for encrypted compliance-data exchange
Keeps personally identifiable information off-chain and encrypted, with keys controlled by the participating VASPs
Supports self-hosted-wallet / private-wallet verification workflows including wallet filtering and Satoshi-test confirmation
Provides a developer center with guides, API references, changelogs, status pages, and a public GitHub docs surface
Uses signed API responses and bridge public-key verification to help counterparties validate message integrity
Key claims:
The product page says Sygna Bridge can be integrated through a simple one-time API integration, supports all virtual asset types, and can connect VASPs to a growing alliance network
The product page says Sygna encrypts PII, keeps data off-chain, and does not collect or access private data
The developer-center workflow docs say Sygna provides both Sygna-to-Sygna VASP transfer flows and VASP-to-private-wallet flows
The private-wallet workflow docs describe wallet-address filtering, originator confirmation, a Satoshi test, and follow-on blockchain-analysis / sanctions checks before the actual transfer proceeds
The bridge-public-key docs say Sygna issues a central public key after VASP registration and attaches signatures to API responses so counterparties can verify data integrity
Whitepaper: No canonical Sygna Bridge whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official product page plus the Sygna developer center and workflow / key-management docs; see ../whitepapers/sygna-bridge-primary-sources-2026-05-01.md.