Blockstream

• Name: Blockstream
• URL: https://blockstream.com/
• Category: bitcoin infrastructure company / wallet-and-signer operator / Lightning-node and Liquid-tokenization infrastructure company
• Tags: bitcoin-ecosystem
• Summary: Blockstream belongs as an entity note because the useful control surface is not any single protocol. One named company sits across the Blockstream App / Jade signer stack, Greenlight hosted Lightning nodes, Core Lightning packaging and stewardship, and the enterprise custody / tokenization workflow around Liquid and AMP. The practical question is who controls the firmware and app release path, hosted-node operating policy, enterprise authorization workflow, and the distribution shell that ties those surfaces together.
• What it does:
  • Operates the Blockstream App and Jade hardware-wallet stack for Bitcoin, Liquid, and Lightning-adjacent self-custody flows
  • Runs Greenlight as a hosted-but-self-custodial Lightning-node service built around Core Lightning infrastructure and Blockstream-managed scheduler / operating layers
  • Maintains and commercializes Core Lightning as part of a broader company product surface rather than leaving it as a detached implementation artifact
  • Sells Blockstream Enterprise for custody, treasury, and tokenization workflows with policy controls, segregated accounts, roles and permissions, and HSM-backed infrastructure
  • Sells AMP as a Liquid-oriented issuance and authorization surface for security-token, stablecoin, and transfer-restriction workflows
  • Positions itself as a long-running Bitcoin infrastructure company spanning consumer wallets, developer tooling, Lightning operations, enterprise custody, tokenization, and Liquid-adjacent infrastructure
• Key claims:
  • The homepage presents one company product stack spanning Blockstream App, Liquid Network, Blockstream Enterprise, Core Lightning, and Jade rather than a single narrow protocol or wallet line
  • The Greenlight launch release calls Blockstream a global leader in Bitcoin infrastructure technology and explicitly groups Greenlight, Core Lightning, Jade, Green, Liquid, and mining / infrastructure services under one company story
  • The same Greenlight release says Core Lightning is the go-to code for enterprise Lightning deployments, Jade is an open-source hardware wallet for Bitcoin and Liquid assets, and Green is the consumer wallet; that is exactly why the company boundary matters more than any one product page
  • The Blockstream Enterprise page sells roles and permissions, segregated accounts, policy controls, cryptographic audit trails, and HSM-backed infrastructure as one integrated enterprise operating shell
  • The AMP page makes issuance, tracking, transfer restrictions, issuer-side ownership records, vesting, dividends, and third-party authorization APIs part of the Blockstream-controlled business surface around Liquid assets
  • The Lightning page markets Core Lightning and Greenlight together and says spec-driven development is maintained by Blockstream’s research team, which reinforces that the company is not only shipping wallets; it is also steering important node and implementation defaults
  • The Jade page keeps hardware design, open-source firmware, and the virtual secure element story inside the same company portfolio, which matters because firmware provenance and companion-app defaults are practical trust boundaries
• Whitepaper: No classic standalone company whitepaper is the point here. The strongest primary-source snapshot for this entity split is ../whitepapers/blockstream-primary-sources-2026-08-06.md.
• Sources:
  • https://blockstream.com/
  • https://blockstream.com/about/
  • https://blockstream.com/enterprise/
  • https://blockstream.com/amp/
  • https://blockstream.com/lightning/
  • https://blockstream.com/lightning/greenlight/
  • https://blockstream.com/jade/
  • https://blockstream.com/press-releases/2023-10-12-blockstream-greenlight-scalable-lightning-integration/

Internal linkages

• Product-layer notes that should stay separate: blockstream-app-jade, greenlight, and core-lightning.
• Useful adjacent company reads: coinkite, foundation-devices, and lightspark.
• Keep the distinction explicit: Blockstream is the operator and release / workflow shell above those product and implementation notes, not a substitute for them.

Protocol / company boundary

• There is no especially clean standalone Blockstream protocol that captures the real control surface here.
• Core Lightning remains an implementation note, Greenlight remains a hosted Lightning service note, and Blockstream App / Jade remains a wallet-and-signer note. But the company still matters separately because one entity controls release cadence, hosted operating policy, enterprise packaging, and the commercial workflow around several of those surfaces at once.
• The Liquid ecosystem and AMP tokenization surface make that even more explicit: the company is selling policy-rich issuance, custody, and treasury workflow, not merely publishing an open-source client.
• That is why Blockstream belongs in companies/: the practical question is who runs the firmware, wallet, node, and enterprise-control shell people actually inherit.

Control surface

• Practical leverage sits in firmware and companion-app release policy, Greenlight scheduler and auth defaults, Core Lightning packaging and roadmap influence, Enterprise roles / permissions / approval workflow, AMP authorization and transfer-restriction policy, and the broader Blockstream-run infrastructure customers treat as operational truth.

• Open-source code lowers some trust costs, but it does not erase the company boundary. Most users and institutions still inherit Blockstream-operated defaults, release channels, APIs, or support workflows instead of composing the whole stack themselves.

• Read Blockstream as a company-run Bitcoin control plane spanning signer firmware, wallet distribution, Lightning-node operations, and Liquid-adjacent enterprise workflow — not as one neutral protocol primitive.

• Last reviewed: 2026-08-06 UTC