mt logoMyToken
ETH Gas
EN

The Institutional Blockchain Privacy Debate Has Moved On to the Next Question

zama1
zama1 768x1024 1

Institutional finance is moving onto open blockchains, and privacy is now firmly on the roadmap. Jeremy Bradley, COO, Zama, says this may well end the ‘is private onchain finance needed?’ debate, but surface another around how it’s provided

Over the past year or so, institutional blockchain has crossed a threshold. Banks, asset managers, payment networks and custodians are no longer confined to isolated pilots, they’re actually validating, issuing and settling on open networks built for regulated financial markets.

Several of the newest networks have also begun building opt-in privacy into their roadmaps, openly acknowledging that institutions need ways to keep financial information confidential while operating on open networks.

When infrastructure built specifically for institutions treats privacy as a priority rather than an afterthought, it confirms what the market’s been saying for some time: financial activity at scale needs to shield balances, transactions and counterparties, while preserving auditability, governance controls and usability.

This, for me, puts an end to the question of whether confidentiality will be needed if institutions are going to use public infrastructure for financial activity. But it doesn’t answer how that confidentiality should be delivered, or what institutions can trust to provide it without giving up the benefits that brought them onchain in the first place.

Different technologies, different trade-offs

Looking at exactly what institutions should expect from a privacy solution, the goal is to protect sensitive information without undermining the properties that make blockchains useful in the first place – settlement, programmability, composability, and interoperability. It also – importantly – needs to preserve the ability of authorised parties to carry out the regulatory checks that financial markets require; something we call “verifiable confidentiality”.

For any institutional reviewer evaluating privacy architecture right now, whether established or newly launched, the above are all points to keep front of mind. The technologies below can also form complementary parts of the same system.

  • Zero-Knowledge Proofs (ZKPs): As one of the first practical ways to verify transactions without revealing amounts or counterparties, ZKPs have been a favourite for early institutional blockchain pilots. But because they can hide transaction paths and flows from everyone (including auditors), institutions may need separate compliance infrastructure, meaning they can’t preserve existing processes onchain. Also, applications often need specialised circuits rather than general smart-contract execution, making integration harder and potentially fragmenting liquidity and execution environments.
  • Permissioned chains: Permissioned networks essentially make confidentiality and compliance easier to manage as they give institutions better control over who can access and transact on them. However, that control comes at the cost of composability and shared liquidity. Institutions can end up operating in fragmented “walled gardens”, with liquidity and counterparties confined to individual networks and limited access to the broader ecosystem.
  • Multi-Party Computation (MPC): MPC lets multiple parties compute over private data without revealing their inputs to one another, but the computation must be carried out jointly by multiple computing parties, which may be separate operators rather than the participants in the transaction. So, in situations where participants are unknown, there are lots of them, or they’re offline, each interaction just adds the need for more coordination and communication, leaving you with something that’s unworkable at scale.
  • Trusted execution environments (TEEs): TEEs let existing smart contracts run largely unmodified, with privacy added at the hardware layer rather than requiring new circuits or specialised tooling. They are today’s most mature option for performance, which is why many networks start there. The trade-off is that confidentiality depends on trusting the hardware and its attestation chain, rather than on cryptography alone. For institutions, the practical questions are how a TEE-based design is secured today, and how it can evolve as cryptographic approaches mature.
  • Fully Homomorphic Encryption (FHE): FHE is somewhat different from the examples above, as it’s the only approach that keeps the chain and computation public, but keeps the data fully encrypted end-to-end and the system composable – all at the same time. As well as nobody without authorisation being able to decrypt balances or transaction amounts on the blockchain, FHE allows selective disclosure to authorised parties, such as regulators, auditors and compliance teams. This is where encrypted data can be accessed by authorised parties, such as regulators, auditors and compliance teams, without exposing it to everyone else. So every regulatory obligation institutions already fulfil – FATF Travel Rule, AML/KYT, audit access – is preserved, with no need to route around them. Composability also isn’t a trade-off here. Smart contracts can operate on encrypted values using the same underlying logic, so transactions can move between contracts as they do today, while the data remains encrypted.

The  decision of any institutional network to put privacy on a product roadmap is a sign of where institutional blockchain is heading. So, as more financial activity moves onto open networks, it’s time to start answering this question of how to add confidentiality without giving up the transparency, compliance and composability that make those networks useful in the first place. Because stablecoins and tokenised assets simply won’t scale in regulated markets without addressing all three simultaneously. That is the standard institutional blockchain privacy needs to meet.

The post The Institutional Blockchain Privacy Debate Has Moved On to the Next Question appeared first on BlockchainReporter .

Disclaimer: This article is copyrighted by the original author and does not represent MyToken’s views and positions. If you have any questions regarding content or copyright, please contact us.(www.mytokencap.com)contact
More exciting content is available on
X(https://x.com/MyTokencap)
or join the community to learn more:MyToken-English Telegram Group
(https://t.me/mytokenGroup)