Cowrie Research

coinos

3 min read

CoinOS

  • Name: CoinOS
  • URL: https://www.coinos.io/
  • Category: web Bitcoin wallet / self-hostable operator bundle / Bitcoin-Liquid-Lightning-Nostr access layer
  • Tags: bitcoin-ecosystem
  • Summary: CoinOS is a web wallet and self-hostable operator bundle for Bitcoin, Lightning, Liquid, and Nostr. The useful part is the packaging around those rails — browser client, API/server layer, and deployable backend stack — not a novel wallet model. Small operator-facing access layer, not a category anchor.
  • What it does:
    • Provides a web-based Bitcoin and Nostr client that users can access through the public CoinOS instance or self-host themselves
    • Supports payments over Bitcoin, Liquid, and the Lightning Network rather than only a single Bitcoin rail
    • Lets operators use CoinOS as a front end to their own Bitcoin and Lightning nodes or run a public username/password-based instance for others
    • Ships a separate API/server component plus frontend web app, with the frontend README pointing to API documentation exposed on a /docs route
    • Coordinates a broader backend stack that the server README describes in terms of Bitcoin node, Liquid, Core Lightning, KeyDB, Nostr, and Cashu-Nutshell-related components
    • Uses containerized setup flows and sample data so operators can stand up a working environment without wiring each component manually
  • Key claims:
    • The main frontend and server repository descriptions both say CoinOS is a web-based Bitcoin and Nostr client and that users can either point it at personal infrastructure or host a public instance
    • The classic/frontend README says CoinOS supports payments over the Bitcoin, Liquid, and Lightning networks and presents the client as a progressive web application
    • The current frontend README says operators should also run coinos-server, which provides a REST/WebSocket API and exposes API documentation on a /docs path
    • The server README describes CoinOS as a composed stack centered on CoinOS Server, Bitcoin, Liquid, Core Lightning, and KeyDB, while also listing Nostr and Cashu Nutshell as integrated components used to support the full feature surface
    • The server setup flow explicitly creates Bitcoin and Liquid wallets and bootstraps Docker containers plus sample data, reinforcing that CoinOS is an operational stack rather than just a lightweight front-end skin
    • During this pass, the public coinos.io and coinos.io/docs URLs exposed mostly client-rendered Svelte shell content to basic fetch tooling, so the GitHub READMEs were the clearest primary-source materials for recovering the actual operating model
  • Whitepaper: No canonical standalone CoinOS whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site/docs URLs plus the public frontend and server repository READMEs; see ../whitepapers/coinos-primary-sources-2026-05-02.md.
  • Sources:

Internal linkages

  • Strongest upward community-banking reads: galoy and blink.

Control surface

  • Power sits in whether an operator runs the public instance or self-hosts, which backend components they actually wire up, the account model they expose to users, and how far they extend the stack into merchant or community-wallet operations.

  • Treat CoinOS as a packaged access layer over stronger underlying rails and services, not as a base protocol or banking anchor.

  • Last reviewed: 2026-06-04 UTC

Graph View