The origins of blockchain technology are rooted in public, open-source networks. However, the future of this technology is increasingly private, with this shift happening more rapidly than anticipated. This month, Tempo, a Stripe-backed payment blockchain that has secured significant funding and backing from major institutions like Visa, Mastercard, Paradigm, and UBS, unveiled a detailed architectural proposal for private enterprise stablecoin transactions.
The fact that Tempo, with its strong institutional credentials and understanding of the needs of banks, payment processors, and enterprises, has made privacy a priority from the outset, is a clear indication of the direction the industry is taking. The question of whether institutional blockchains will be private is no longer up for debate; the focus has moved to determining the type of privacy that will be built into these systems. The issue with public blockchains lies in their transparency, which, while a foundational aspect of their design, poses significant challenges for institutional adoption.
Every transaction, balance, and wallet is visible to anyone, which is not feasible for financial markets. This level of transparency can lead to front-running, strategy mapping by competitors, and identification of targets by criminals, effectively crippling the financial system as we know it. The recent announcement by Tempo signals that institutions are no longer willing to accept this level of transparency. The solution proposed by Tempo involves 'Zones' - private parallel blockchains connected to the main network, where participants can transact privately, with only cryptographic proofs of validity visible to the public.
This design is practical for enterprises handling payroll, treasury operations, or settlement workflows but relies on trusting the Zone operator, who has visibility into all transactions within their Zone. This model, while acceptable for many regulated institutions, does not eliminate the visibility problem but rather shifts it. An alternative approach is offered by zero-knowledge cryptography, which enables proving the validity of a transaction without revealing the underlying data. ZK-native blockchains integrate this privacy-preserving functionality directly into their execution layer, allowing for local transaction execution with only a cryptographic commitment stored on the chain.
This approach ensures that no operator has a comprehensive view, and privacy is enforced at the base layer. Regulatory compliance is often cited as a barrier to privacy, with the assumption that privacy and compliance are mutually exclusive.
However, this framing is outdated. Compliance requires that the right parties can verify the legitimacy of transactions under the right conditions, not that all transactions be fully transparent.
ZK cryptography can enforce selective, programmable disclosure, meeting compliance demands without full transparency. The choice between privacy through trusted operators or cryptographic guarantees has significant implications for the risk surface, compliance posture, and exposure to intermediary failure modes. As the financial industry moves towards on-chain operations, the era of public-by-default blockchains for institutional finance is coming to an end.
The decision on the type of privacy to adopt will determine the course of this transition, with both models having legitimate arguments but differing in how trust is distributed. Ultimately, the question is no longer about whether to have privacy but about what kind of privacy the industry is willing to adopt and who, if anyone, they are willing to trust with oversight.