Cowrie Research

jan3

4 min read

JAN3

  • Name: JAN3 LLC
  • URL: https://jan3.com/
  • Category: Bitcoin-and-Liquid wallet operator / integration-packaging company / Bitcoin adoption workflow shell
  • Tags: bitcoin-ecosystem
  • Summary: JAN3 clears the bar for a company note because the useful question is not only what can AQUA Wallet do? but which named operator ships the wallet, controls supported-asset and partner-integration policy, runs the docs and support path, and packages account-adjacent workflow like Lightning Address and WapuPay around the user experience? The project note remains useful for AQUA’s product surface; this note is for the company boundary around release, legal terms, product packaging, and the broader JAN3 shell that decides how Bitcoin, Liquid, Lightning, swaps, and fiat-adjacent rails get bundled for users.
  • What it does:
    • Operates JAN3 as a Bitcoin technology company building tools for individuals, enterprises, and nation-states
    • Ships AQUA as a non-custodial Bitcoin-and-Layer-2 wallet for BTC, Liquid assets, and USDt-oriented spending and savings flows
    • Controls which digital assets AQUA supports and explicitly reserves discretion to add other supported assets in the future
    • Maintains the wallet’s docs and support path, with the public AQUA repository pointing to JAN3-hosted documentation and first-party support channels
    • Packages third-party integrations and service access around the wallet, including swaps, on/off-ramp-style conveniences, and geography-sensitive service availability described in AQUA’s legal materials
    • Extends the broader account-and-wallet shell beyond the mobile app through first-party tooling like Agentic AQUA, which exposes JAN3 account login, Lightning Address management, and WapuPay flows
  • Key claims:
    • JAN3’s official site says it is a Bitcoin technology company that provides tools and solutions for individuals, enterprises, and nation-states, which is the clearest first-party statement that JAN3 is an operating company rather than a neutral protocol steward
    • The AQUA homepage footer says © 2026 JAN3 LLC and Built by JAN3, which is a strong direct signal that the wallet’s public distribution surface belongs to the company boundary
    • AQUA’s terms say the agreement is between the user and JAN3 LLC, describe the company as registered in Prospera ZEDE under corporate registration number 86588576351549, and call it a wholly-owned indirect subsidiary of JAN3 GLOBAL INC.
    • AQUA’s terms say the wallet is for Bitcoin, Liquid assets, and any other digital assets JAN3 may explicitly decide to support in the future at its discretion, which makes supported-asset policy an operator-controlled surface rather than a neutral protocol fact
    • The same terms say AQUA supports or integrates with several third-party services and warn that some services may geoblock or require extra accounts and data collection, which reinforces that the company boundary matters for partner packaging and access policy
    • The AQUA repository README routes docs to jan3.zendesk.com and support to support@aqua.net, which makes the support-and-documentation shell part of the JAN3 control surface rather than just community-maintained wallet software
    • JAN3’s agentic-aqua materials say JAN3 account features include login, Lightning Address, and WapuPay, which is useful evidence that the company is packaging more than a static mobile wallet binary
  • Whitepaper: No separate JAN3 company whitepaper is the point here. The strongest primary materials are JAN3’s company pages, AQUA’s footer and legal pages, and JAN3’s public repository materials already captured in ../whitepapers/jan3-primary-sources-2026-08-08.md.
  • Sources:

Internal linkages

  • Product-layer note: aqua-wallet.
  • Useful wallet-company comparisons: cake-labs, blockstream, and lightspark.
  • Keep the AQUA product note separate from this operator note: the wallet rail mix is one question; the named company boundary around support, integrations, and account packaging is another.

Protocol / company boundary

  • Keep aqua-wallet focused on the product surface: BTC/Liquid/USDt packaging, consumer wallet UX, swap and spending rails, and the practical mix of Liquid plus thinner Lightning support.
  • Keep this note focused on JAN3 as the named operator that publishes the legal terms, controls supported-asset policy, chooses and packages partner integrations, runs the support/docs path, and increasingly wraps account-level workflow around the wallet experience.
  • That split matters because what does AQUA expose? and which company controls the distribution, integration, and trust shell around AQUA? are related but not identical questions.

Control surface

  • Practical leverage sits in supported-asset policy, third-party integration choices, geography-sensitive service exposure, documentation and support routing, and the broader JAN3 account layer that can make Lightning Address, agent tooling, and WapuPay feel native around the wallet.

  • Even when the wallet is non-custodial, users still depend on JAN3 for the release path, the legal and support perimeter, and the default packaging of Liquid, swap, and payment-adjacent services.

  • Treat JAN3 as the company-run wallet-and-payments packaging shell around AQUA, not as a neutral protocol or merely a marketing parent.

  • Last reviewed: 2026-08-08 UTC

Graph View

Backlinks