The Issue of Privacy Has Been Settled, But What Form Will It Take?

Blockchains were initially designed as public networks, following the principles of open-source technology. However, their future is headed towards private networks, and this shift is happening faster than anticipated. This month, Tempo, a Stripe-backed payment blockchain that raised $500 million at a $5 billion valuation with notable backers including Visa, Mastercard, Paradigm, and UBS, released a detailed architectural proposal for private enterprise stablecoin transactions. Given Tempo's strong institutional credentials and its decision to prioritize privacy from the outset, it's clear that the question of whether institutional chains will be private has been settled. The more challenging question now is what kind of privacy the industry will build. The problem with public chains lies in their transparency. Every wallet, balance, and transaction is visible to anyone with a browser, which is not a desirable feature in financial markets. This level of transparency would be catastrophic for institutions, as it would allow competitors to map their strategies, sophisticated counterparties to front-run, and criminals to identify targets. The financial system as we know it would come to a standstill overnight. Blockchains have been asking institutions to accept this level of transparency, but Tempo's announcement signals that institutions have finally said no. The conversation now turns to the type of privacy the industry will adopt. Tempo's solution, Zones, involves private parallel blockchains connected to the main network, where participants can transact privately, and the public only sees cryptographic proofs of validity. While this model is practical for enterprises, it relies on trusting an intermediary, as the Zone operator can see all transactions within its Zone. This is a genuine architectural choice with significant consequences for risk management. Zero-knowledge cryptography offers an alternative path, enabling parties to prove the validity of transactions without revealing underlying data. A new generation of blockchains is building this privacy-preserving functionality into their execution layer, allowing for verifiable privacy where transactions are validated without exposing sensitive information. The regulatory objection to privacy is becoming outdated, as compliance does not require full transparency but rather the ability for the right parties to verify the legitimacy of transactions under the right conditions. Both Tempo's model and ZK-native approaches satisfy compliance requirements but distribute trust differently. The financial industry recognizes the need to move on-chain and is now acknowledging that it cannot do so on fully public infrastructure. The choice between privacy through trusted operators or cryptographic guarantees will determine the industry's risk surface, compliance posture, and exposure to intermediary failures. This architectural decision will determine everything else, and the industry must make a clear choice.