Stellar’s Denelle Dixon says institutional blockchain adoption stalls over privacy gaps. Banks fear rivals seeing their transaction data on transparent ledgers.
A major global bank told Stellar’s Executive Director something that stopped her cold. “Unless you can protect my information, I can’t do anything on the blockchain.” That was not about customer data. Not about consumer protection. It was about the bank’s own competitive intelligence.
Denelle Dixon shared that account in a blog post published March 9, 2026, laying out what she sees as blockchain’s real adoption wall. The issue is not regulation. It is not cost. It is the ledger itself.
You Might Also Like: Chainlink Powers Visa, ANZ, Fidelity in Cross-Border Settlement
What Banks Actually Mean By “Privacy”
When a financial institution says privacy, Dixon argues, they mean something very specific. Daily deposit volumes. Payment flow patterns. Counterparty identities on large deals. Positions being built. That information shapes competitive strategy. A rival watching those flows in real time would know payroll schedules, vendor relationships, which payment corridors are winning.
No institution puts that on a public ledger willingly. The traditional financial system solved this decades ago, not cleanly, but reliably. Custodians, broker-dealers, and clearing corporations sit between institutions and public records. Competitors cannot see each other’s books. It works.
Blockchain’s open architecture breaks that. The transparent ledger that makes it auditable and trustworthy is the same thing stripping institutions of protections they already have.
Must Read: ICE Invests in OKX at $25B Valuation to Expand Tokenized Stock Trading
The Distinction That Changes Everything
As Dixon wrote on X, “Blockchain transparency was designed so bad actors can’t hide. It was never designed so one bank can see what another is doing on a Tuesday afternoon. That distinction matters.”
That sentence carries the weight of the whole debate. The technology’s core design keeps fraudsters visible. It was never meant to hand one bank’s strategy to its rival. Those two purposes get conflated constantly, and that conflation is what stalls progress.
Dixon is clear that existing legal tools cannot fix the technical gap. GDPR and similar regimes were designed for controlled, siloed Web2 systems. Trade secrecy protections depend on information staying secret. Once data broadcasts on a transparent chain, no legal doctrine pulls it back. The fix has to come from the protocol level.
You Might Also Like: Digital Asset Firm Zerohash Applies for U.S. National Trust Bank Charter
Privacy and Openness Are Not Opposites
Dixon pushes back on the purist framing. Technology absolutists say: if you need that much privacy, use a private database. Enterprise skeptics say: if you cannot offer privacy, the infrastructure goes unused. Both miss the point.
Neither position reflects how this actually develops. Privacy and openness sit on a spectrum, not at two poles. Different use cases need different settings. One institution’s requirements will not match another’s. The answer is configurable privacy at the application layer over a transparent base. Stellar has already been building toward that.
The cryptographic tools exist. Zero-knowledge proofs let a party confirm a transaction is valid without revealing counterparties. An account can prove it meets a threshold without disclosing the balance. Provenance can be verified without exposing the full transaction chain. The building blocks are there.
Must Read: Eric Trump Says JPMorgan, BofA Are Blocking Crypto Yields As SEC Acts
Institutions Are Now at the Table
Dixon noted that financial institutions are only now beginning to engage directly in these conversations. Stellar has been pursuing partnerships with major financial players, not to build for them, but alongside them. The goal is understanding actual requirements, not assumed ones.
The questions she puts forward are precise. How much transaction detail does the system need to be public to prove integrity? What audit access satisfies regulators without leaking competitive data? How is asset provenance verified without exposing flow patterns? How does bad actor removal work without contaminating the broader network?
None of those questions gets answered without institutions in the room. And none gets answered by blockchain developers alone.
The path Dixon describes is not about making a new system from scratch. It is about asking whether shared, auditable infrastructure can deliver better accountability while keeping competitive data protected. That outcome, she says, is only possible if both sides stop treating each other as obstacles and start building together.
