HostDeFi › Guides › Shielded balances & viewing keys

Shielded balances and viewing keys — auditable privacy, explained

The design that ended the "privacy or compliance" stalemate: hide everything from everyone, then hand out read-only keys to exactly the parties you choose.

Educational guide · reviewed August 2026 · not financial or legal advice

For most of crypto's history, on-chain privacy was sold as a binary: either the whole world reads your ledger, or nobody does — including the auditor, the tax office and the exchange that has to decide whether your deposit is clean. Shielded balances with viewing keys dissolve that binary. The balance and every transfer amount are encrypted on-chain; the network still verifies that no rule was broken; and the owner holds a separate, read-only credential they can give to anyone who legitimately needs to see the books. It is the architecture behind most serious institutional privacy work of the past two years, and understanding it changes how you evaluate every "private" product that crosses your feed.

How a balance can be hidden and verified at once

The apparent paradox — how can validators check a transfer they cannot read? — is exactly what modern cryptography is good at. In the zero-knowledge construction, each shielded account's state is a commitment: a cryptographic sealed envelope whose contents can be proven without being opened. A transfer comes with a proof that says, in effect, "the sender's envelope contained at least this much, the amounts balance, nothing was created or destroyed" — and the network verifies the proof, not the numbers. Encrypted-computation designs reach the same destination differently, keeping amounts encrypted while specialized infrastructure computes on the ciphertexts. Either way, what lands on the public chain is validity without visibility.

This is a different thing from a mixer, and the difference matters. A mixer's job is to break the link between a deposit and a withdrawal — anonymity of flow. A shielded balance's job is confidentiality of state: the token still sits in your account, associated with you, movable only by your key; it's the amounts and activity that outsiders can't read. That distinction — confidential rather than anonymous — is precisely what gives the model its compliance story.

The viewing key is the whole trick

Alongside the spending key that moves funds, shielded systems derive a viewing key: a credential that can decrypt the account's activity but cannot sign a transaction. Hand it to your accountant and they can prepare your taxes from complete records. Hand a scoped disclosure to an exchange's compliance desk and they can satisfy themselves about a deposit's history. Some designs go further with proofs of non-association — demonstrating that funds do not trace to a sanctioned source without revealing where they do come from. The privacy stops being a wall and becomes a door with a guest list.

Where the model still leaks

Shielded balances narrow the audience; they do not erase the record, and a user who treats them as invisibility gets burned by the edges. The boundary is the classic one: moving tokens into shielded form and back out is a public event, and an entry followed by an equal-sized exit draws its own line for anyone watching. Timing and counterparty patterns survive encryption — who you transact with, and when, can say plenty even with every amount hidden. Whoever holds your viewing key sees everything it covers, forever, so scope and custody of those keys deserve the same care as the spending key. And the entire construction inherits smart-contract and implementation risk: an encrypted balance in a buggy system is still a lost balance.

There is also a liquidity truth nobody's marketing mentions: confidentiality is only as comfortable as the crowd sharing it. Early shielded ecosystems are small, and small anonymity sets mean each participant stands out more than the cryptography implies. The guarantees strengthen as adoption grows — which is a way of saying that today's shielded balances are a maturing tool, not a finished cloak.

Evaluating any "shielded" product in four questions

1. What exactly is hidden? Amounts only? Sender-receiver links? Account existence? Products differ wildly, and the word "private" covers all of them. Read the design, not the tagline.
2. Who can be shown what, and how? If there is no viewing-key or selective-disclosure mechanism, you are holding blanket anonymity — with the venue and regulatory risks that model carries.
3. How big is the crowd? Ask what the shielded pool or confidential-token adoption actually looks like. Privacy among ten users is a short suspect list.
4. What is the failure mode? Audited contracts, immutable or upgradeable, escape hatches, key-loss recovery. Encryption adds a way to lose access on top of every ordinary way to lose funds.

And the evergreen rule holds here too: shielding is a property of the rails, not the asset. A confidential balance of a worthless or malicious token is confidentially worthless. Verify the token before you care how privately you can hold it.

Frequently asked