Blockchain is built as a public network in the best traditions of open source technology. But their future is private. And that future is coming faster than most people realize.
This month, Tempo — the Stripe-backed payments blockchain that raised $500 million at a $5 billion valuation and whose backers include Visa, Mastercard, Paradigm and UBS — released a detailed architectural proposal for private enterprise stablecoin trading. Tempo is not a scrappy privacy-native project. This is arguably the most institutionally recognized blockchain launch in years, created by people who deeply understand the real needs of banks, payment processors and businesses. It’s not exactly a sign when a network with this pedigree makes privacy a priority during launch week. This is a verdict.
The question of whether the institutional chain should be privatized has been resolved. The remaining question is a harder one: What kind of privacy are we actually establishing?
Problems with public chains
Bitcoin solves a problem that has vexed computer scientists and bankers for decades: how to transfer value between strangers without a trusted intermediary. Ethereum takes the blockchain a step further by providing programmable value while transferring value – smart contracts that can encode protocols, automate settlements and eliminate an entire class of middlemen. Then came stablecoins, which combined programmability with the stability of the U.S. dollar, and since then real-world assets have begun migrating to on-chain protocols.
Each wave brings more institutional interest, capital and ambition. Now, as regulations become clearer, institutions are ready to deploy resources on-chain.
But there’s one thing holding them back – a fundamental flaw that becomes more severe the higher the number.
Everything is visible. per wallet. Every balance. Anyone using a browser can read every transaction in real time. In financial markets, this is not a feature. This is an existential problem. Imagine if every hedge fund position, every corporate treasury holding, every pension fund rebalancing trade appeared on a public screen as it was executed. Experienced counterparties will have a head start. Competitors will map your strategy. Criminals identify targets. The financial system that exists today would fail overnight.
Blockchain has always required institutions to embrace this. Tempo’s April 16 announcement was the clearest signal the agency has finally said: no.
architecture is destiny
Here, the dialogue becomes more important and more nuanced.
Tempo’s solution is zones: private parallel blockchains connected to the main network. Within an area, participants conduct transactions privately. The public can only see the cryptographic proof of validity, not the underlying data. Compliance automatically controls travel using tokens. Assets are still interoperable with the Tempo mainnet. It’s a thoughtful and practical design for businesses running payroll, financial operations, or closing workflows.
But Tempo’s privacy model is visible to the operator. Regional operators (enterprises or infrastructure providers) can view all transactions within their region. The public sees nothing. The operator sees everything. For many regulated institutions, this is acceptable and may even be required. But this means that privacy depends on trust in intermediaries. You’ve solved the visibility problem; you haven’t eliminated it.
This is not a criticism of Tempo. It describes a real architectural choice—one that has real consequences for anyone who thinks carefully about the risks.
Zero-knowledge cryptography offers a different path. ZK proofs allow a party to prove that a transaction is valid without revealing the underlying data. The new generation of ZK native blockchain builds this privacy protection into the execution layer itself. Accounts execute transactions locally, and the chain only stores cryptographic commitments. No sensitive information touches the public ledger. Transaction history cannot be viewed. Crucially, no operator has a God’s eye view – privacy is enforced at the base layer rather than delegated to intermediaries.
If Bitcoin gave us trustless transmissions and Ethereum gave us programmable trust, then the ZK native blockchain provides verifiable privacy: the ability to prove that everything happened correctly without revealing what actually happened.
Compliance not fully transparent
The obvious objection is regulation. Privacy and compliance have long been considered incompatible—oil and water. This framework is becoming obsolete.
Regulatory compliance does not require that everyone can see your transactions. It requires that the right parties, under the right conditions, can verify that your transaction is legitimate. This is a meaningful distinction, and one in which ZK cryptography is uniquely positioned. Selective, programmable disclosure—disclosing what regulators need to see and nothing more—is not a solution. This is a more precise implementation of what compliance actually requires.
Tempo’s model handles this problem at the operator level. ZK native methods handle it at the encryption level. Both meet compliance requirements. But the way they allocate trust is very different.
important questions
The financial industry knows it needs to move on-chain. It now knows – and Tempo’s statement makes this undeniable – that it cannot do so on a completely public infrastructure. The days of defaulting to public blockchains as the presumed standard in institutional finance are ending.
What happens next depends on the choice the industry is just beginning to make clear: protect privacy through trusted operators, or protect privacy through cryptographic guarantees that require no trust at all.
Both are legitimate answers. But they are not equivalent. The privacy model you choose determines your risk surface, your compliance status, and the failure modes of the intermediaries you rely on. Architecture is not a technical detail that needs to be solved later. Decisions determine everything else.
The issue facing the industry is not privacy. This debate is over.
The question is what kind of privacy – and who (if anyone) are you willing to trust with your opinion.
