Block primary sources — 2026-08-07

Project status in this pass

  • No standalone company whitepaper surfaced.
  • The clearest current source of truth for the entity split is Block’s own bitcoin page plus its open-source overview, read alongside the already-captured primary-source bundles for Cash App and Bitkey.
  • The useful question is not just what does one product do? but how does one named company package bitcoin distribution, checkout, recovery, merchant acceptance, and open-source infrastructure under one operator boundary?

Primary-source snapshots

1) Block bitcoin page

  • URL: https://block.xyz/bitcoin
  • Key excerpt:
    • Block says it has championed bitcoin for over a decade and explicitly groups together Cash App bitcoin access, Lightning payments, Bitkey self-custody, Proto mining hardware, and native bitcoin payments across Square merchants.
    • The page says more than 24 million actives have bought bitcoin with Cash App and that one in four bitcoin payments on Cash App happen over the Lightning Network.
    • This is the clearest first-party reason to treat Block as a company-layer Bitcoin control surface rather than reading each surface in total isolation.

2) Block open-source overview

  • URL: https://opensource.block.xyz/
  • Key excerpt:
    • The page says Block’s projects span payment systems, privacy initiatives, bitcoin hardware wallets, AI agent frameworks, and broader developer infrastructure.
    • It highlights LDK as a featured project and frames Block as contributing to foundational technologies across Bitcoin and wider software ecosystems.
    • This is useful because it makes the company’s engineering and distribution boundary broader than Cash App or Bitkey alone.

3) Cash App bitcoin page

  • URL: https://cash.app/bitcoin
  • Key excerpt:
    • The page says bitcoin services are provided by Block, Inc., says Cash App holds bitcoin 1:1 and never lends it out, and says users can withdraw to their own wallet anytime.
    • It also says users can pay merchants that use Square with bitcoin or U.S. dollars.
    • That is a clean primary-source link between the Cash App product surface and the broader company/operator boundary.

4) Cash App Pay developer docs

  • URL: https://developers.cash.app/cash-app-pay-partner-api/guides/welcome
  • Key excerpt:
    • The docs welcome page says developers get comprehensive guides, API references, testing environments, and integration tools for implementing Cash App Pay.
    • This confirms that the Block boundary is not only retail bitcoin distribution; it also includes a real merchant and developer checkout surface.

5) Bitkey primary sources

  • Source bundle: ./bitkey-primary-sources-2026-05-01.md
  • Key excerpt:
    • Bitkey’s official materials say the product is a mobile app, hardware device, and set of recovery tools, while the code-release post says Block published code for the device, app, server, and hardware designs.
    • The repository overview separates firmware, mobile apps, shared wallet logic, nodes, server / Wallet Security Module, and infrastructure.
    • This is strong evidence that Block’s role is not only branding; it is the release and provenance boundary for a multi-layer custody-and-recovery system.

6) Cash App primary sources

  • Source bundle: ./cash-app-primary-sources-2026-05-02.md
  • Key excerpt:
    • The standing Cash App source bundle already shows the mix of 1:1 bitcoin custody claims, self-custody withdrawals, grant-based payment authorization, and broader Block open-source context.
    • That bundle remains the best product-layer evidence for why the Cash App note should stay separate while still pointing upward to Block.

Working conclusion

Block is worth an explicit company/entity note because the practical Bitcoin control surface is not exhausted by Cash App or Bitkey individually. The company bundles retail distribution, merchant acceptance, collaborative recovery, open-source release workflow, and public Bitcoin strategy under one operator boundary. That makes who controls the Block shell around these products? a materially different and more useful question than what does one product page claim?