Cowrie Research

coolbitx-primary-sources-2026-08-13

4 min read

CoolBitX primary-source snapshot

Fetched: 2026-08-13 UTC

1) CoolBitX about page

Source: https://coolbitx.com/about/

Selected excerpts from the official site:

CoolBitX launched in early 2014, ready to change the world.

In February of 2020, CoolBitX raised $16.75 million in a series B funding round led by SBI Holdings. Other partners include Monex, Binsonic and the National Development Fund of Taiwan. The funding will help expand Sygna beyond the APAC region to help provide FATF-compliant solutions to VASPs around the world.

Without industry support, CoolWallet S and Sygna would not be what they are today.

Additional signals from the source:

  • CoolBitX presents itself as the named company behind both the CoolWallet hardware-wallet line and the Sygna compliance stack, which is exactly the kind of cross-product operator boundary that can get lost if the corpus only keeps a product note.
  • The about page is useful because it ties company history, fundraising, and product expansion together in one operator narrative rather than treating Sygna as a disconnected protocol surface.
  • Even without a separate CoolWallet product note in this pass, the page makes clear that Sygna was launched inside a broader company shell with hardware-wallet provenance and security branding.

2) Sygna about page

Source: https://www.sygna.io/about/

Selected excerpts from the official site:

CoolBitX, backed by investment from SBI Holdings, launches Sygna Bridge as a first-to-market solution for VASPs to comply with FATF R.16

Sygna Bridge demonstrates effectiveness as a cross-border ‘Travel Rule’ solution and acquires global recognition.

VerifyVASP Acquires Sygna

Additional signals from the source:

  • Sygna’s own history page explicitly keeps the company boundary visible instead of presenting the bridge as a standalone neutral primitive.
  • The page is especially useful for taxonomy because it shows both the originating operator boundary (CoolBitX) and a later ownership/control transition (VerifyVASP’s 2026 acquisition of Sygna).
  • That means the right analytical question is not only how does Sygna Bridge move compliance data? but also which named entity is packaging and controlling the network at each stage?

3) Sygna homepage / solutions page

Source: https://www.sygna.io/

Selected excerpts from the official site:

Sygna’s modular crypto AML range will help your VASP meet global crypto regulations with confidence, thanks to our ease of use, industry-best ISMS standards and total user data privacy.

Includes Sygna Bridge Travel Rule protocol, interoperability enabled with other protocols like CipherTrace’s TRISA & Veriscope on Shyft.

Additional signals from the source:

  • Sygna markets a broader modular compliance suite rather than only a narrow message relay, which strengthens the case for modeling a company/entity shell above the bridge product.
  • The homepage also shows that Sygna Bridge sits inside a larger product and alliance story that customers may inherit operationally.

4) Sygna developer introduction / API flow

Source: https://developers.sygna.io/reference/introduction

Selected excerpts from the official docs:

Bridge API helps VASPs to exchange required compliance information and obtain a cryptographically signed compliance record (we call it permission) before broadcasting anything to the blockchain.

Once you have successfully registered as a verified VASP in the Bridge Ecosystem, we will publish your public key along with an associated vasp_code for other VASPs to query.

The server will then relay the request to the beneficiary VASP and wait for the callback of the validation result.

Additional signals from the source:

  • The docs make the operator role concrete: registration, verified-VASP admission, public-key publication, central relay behavior, and signed compliance records are all company-shaped workflow decisions rather than neutral protocol facts.
  • This is why the company boundary matters separately from the product note: network admission and workflow truth are part of the practical control surface.

Notes

  • This pass did not try to fully map CoolBitX’s corporate structure or post-acquisition legal boundaries; the useful outcome was clarifying that Sygna originated inside CoolBitX’s operator shell and later moved into a broader VerifyVASP consolidation story.
  • The best taxonomy split after this source check is: Sygna Bridge for the product and integration mechanics, CoolBitX for the originating operator / packaging boundary, and VerifyVASP for the acquiring Travel Rule network operator boundary now relevant to Sygna’s ownership story.

Graph View