Block Puts $2.2B in Bitcoin on the Record: Q1 Proof-of-Reserves and the Real Transparency Trade-Off

Block has shifted from “trust us” to “check the chain.” In its first-quarter proof-of-reserves release, the Jack Dorsey–led fintech behind Square and Cash App disclosed 28,355 BTC—about $2.2 billion as of March 2026. Of that, 19,357 BTC (roughly $1.5 billion) are held for customers, and 8,997 BTC (about $692.3 million) sit in corporate treasury. A third-party audit backs the figures, and Block says anyone can independently verify balances via on-chain cryptographic signatures, with addresses under active control rather than passively observed.

One detail worth lingering on: Block is explicitly prioritizing verifiability over opacity. That choice carries strategic upsides—and some under-discussed costs.

What Block gets right - It meets the post-FTX demand for transparency. Proof-of-reserves (PoR) gained traction after November 2022 as exchanges and fintechs looked to rebuild confidence. A verifiable, auditor-attested reserve schema directly addresses customer anxiety. - It aligns with Bitcoin’s ethos. Encouraging users to verify—rather than rely on a PDF—is culturally resonant and reduces reliance on brand trust alone. - It signals treasury conviction without overreach. With just under 9,000 BTC, Block ranks 14th among corporate holders, sitting just behind Trump Media, according to public trackers. That’s meaningful exposure without becoming the story.

Where the model still falls short - Assets ≠ solvency. PoR demonstrates control of assets; it does not prove liabilities. Without a cryptographic liabilities attestation (e.g., Merkle tree commitments) and an independent reconciliation, stakeholders can’t reliably infer solvency. - Transparency can leak information. Publishing verifiable address sets—or even stable signing clusters—can reveal past and future transaction flows, counterparties, and treasury behavior. Michael Saylor criticized this precise point in 2025, arguing current PoR practices can weaken security for issuers, custodians, exchanges, and investors. Many operators quietly agree: verifiability can create new attack and surveillance surfaces. - “Active control” needs precision. Demonstrating key control today doesn’t guarantee encumbrances don’t exist elsewhere (off-chain lending, rehypothecation, or contingent claims). Audits help, but control proofs need pairing with policy attestations and legal constraints.

How to upgrade this framework - Pair PoR with proof-of-liabilities. A user-verifiable liabilities tree—audited for completeness—closes the biggest gap. Done well, this preserves privacy while giving depositors a direct check. - Use privacy-preserving attestations. Zero-knowledge proofs or one-time signing commitments can confirm reserves without exposing address histories or clustering heuristics that erode operational privacy. - Codify operational hygiene. No address reuse, disciplined UTXO management, and multi-sig policies with hardware-enforced quorum reduce traceability risks while keeping verifiability intact. - Time-bound and policy-bound proofs. Regular signing windows, auditor attestations of wallet policies, and disclosure of any encumbrances or lending agreements add context that pure key-control cannot.

Business context matters here. Block’s disclosure lands ahead of its May 7 Q1 earnings, following net income of $115.7 million in Q4 2025—down from $1.9 billion in the same quarter of 2024. Investors will likely parse whether transparent reserve practices support user retention in Cash App, lower funding costs, and reduce counterparty friction—benefits that often outweigh the incremental privacy risk when executed thoughtfully.

Block’s report is a constructive step: independently verified, on-chain checkable, and clear about what’s being controlled. But the market is drifting toward a higher bar—verifiable assets and verifiable liabilities, with privacy preserved by design. The companies that solve that triangle earn more durable trust than a signature alone can buy.