CoolBitX

• Name: CoolBitX
• URL: https://coolbitx.com/
• Category: hardware-wallet and compliance-stack company / Sygna originating operator / CoolWallet provenance boundary
• Tags: bitcoin-ecosystem compliance travel-rule
• Summary: CoolBitX belongs in companies/ because the useful question is not only what does Sygna Bridge do? but which named operator built and packaged both the CoolWallet signer line and the Sygna compliance stack, raised capital to expand Sygna globally, and gave the product its original security-and-provenance shell before later acquisition activity changed the ownership map? That company boundary matters because Sygna was not born as a neutral protocol primitive. It was launched inside a specific operator story with hardware-security branding, product packaging, and network-building decisions concentrated in one entity.
• What it does:
  • Founded and operated CoolBitX as a blockchain-security company with roots in hardware-wallet design and portable cold-storage products
  • Built and shipped the CoolWallet hardware-wallet line, which gave the company a signer-security and device-provenance identity before it expanded into compliance infrastructure
  • Launched Sygna Bridge as a Travel Rule solution for VASPs and later expanded the broader Sygna compliance suite beyond the bridge alone
  • Packaged company history, product narrative, and security posture around both wallet and compliance products inside one named corporate shell
  • Sat at the original operator boundary for Sygna before Sygna’s own official history later recorded acquisition by VerifyVASP in 2026
• Key claims:
  • CoolBitX’s about page says the company launched in early 2014, which is the starting point for the operator history rather than a generic product timeline
  • The same page ties CoolBitX directly to both CoolWallet and Sygna, saying that 2020 funding would help expand Sygna beyond the APAC region and later reflecting that CoolWallet S and Sygna were both core products of the company shell
  • Sygna’s own about page says CoolBitX ... launches Sygna Bridge as a first-to-market solution for VASPs to comply with FATF R.16, which is the clearest first-party evidence that the bridge originated inside CoolBitX rather than as an independent protocol foundation
  • The Sygna site also markets a broader modular AML range around Bridge, Hub, and Gate, which reinforces that customers were inheriting a company-run compliance stack rather than only one bridge API
  • The Sygna about page later says VerifyVASP Acquires Sygna, which makes the CoolBitX note useful as the originating operator boundary even if the current ownership/control story has evolved
  • The developer docs say verified-VASP registration, public-key publication, central relay behavior, and signed permission records are part of the operating model, which is exactly why naming the original operator matters for control-surface analysis
• Whitepaper: No standalone CoolBitX company whitepaper is the point here. The useful primary materials are CoolBitX’s about page plus Sygna’s official history, product overview, and developer docs, captured in ../whitepapers/coolbitx-primary-sources-2026-08-13.md.
• Sources:
  • https://coolbitx.com/
  • https://coolbitx.com/about/
  • https://www.sygna.io/
  • https://www.sygna.io/about/
  • https://developers.sygna.io/reference/introduction
  • ../whitepapers/coolbitx-primary-sources-2026-08-13.md

Internal linkages

• Product-layer note for the Travel Rule network surface: sygna-bridge.
• Useful adjacent current operator boundary: verifyvasp.
• Useful adjacent compliance-network contrasts: notabene, sumsub, and netki.
• Read this note when the question is about origin, packaging, or operator history across CoolWallet and Sygna rather than the bridge API surface in isolation.

Protocol / company boundary

• Keep Sygna Bridge on the product and integration surface: Travel Rule messaging, off-chain encrypted data exchange, wallet-verification workflow, signed responses, and developer-facing API mechanics.
• Keep this note on CoolBitX as the originating operator boundary that launched Sygna, packaged it inside a broader hardware-security company narrative, and controlled the early product and expansion story.
• Use VerifyVASP when the useful question becomes the later acquiring network operator and the broader consolidation of Travel Rule workflow under another named company.
• That distinction matters because how does Sygna Bridge work?, who originally built and packaged it?, and who may now sit above the network after acquisition? are related but not identical questions.

Control surface

• The important historical leverage here sat in product definition, network-building, verified-participant admission, public-key and relay workflow packaging, and the security/provenance shell that made Sygna marketable to VASPs as a trusted compliance product.

• Even if current operational authority has partially shifted after acquisition, origin still matters because many compliance stacks inherit design assumptions, customer relationships, and trust framing from the company that launched them.

• Read CoolBitX as the original operator and packaging boundary around Sygna, not as a neutral standards body.

• Last reviewed: 2026-08-13 UTC