Shielded Labs has proposed a new network upgrade for Zcash that would let anyone independently verify the privacy coin's total supply hasn't been secretly inflated. The proposal comes shortly after developers patched a bug in the Orchard shielded pool that could have allowed undetectable counterfeiting of ZEC tokens.
The Upgrade Proposal
The upgrade, put forward by the development group Shielded Labs, aims to add a public audit mechanism to Zcash's shielded transactions. Currently, the privacy features that hide transaction amounts also make it impossible for outsiders to confirm that no extra coins have been minted out of thin air. The proposed change would give anyone the cryptographic tools to check the supply without breaking privacy for individual users. Shielded Labs says this would close a longstanding trust gap in the network.
The Orchard Bug
Before the proposal was even announced, developers quietly fixed a vulnerability in Orchard, Zcash's main shielded pool. The bug could have let an attacker create counterfeit ZEC in a way that no public ledger would detect. Because shielded transactions are encrypted, a counterfeiting exploit wouldn't show up in normal block explorers. The patch was deployed without fanfare, and the Zcash Foundation confirmed no funds were lost. But the incident underscores why the supply verification upgrade matters: even a patched bug raises questions about what else might lurk in the shielded code.
Zcash has always faced a tension between privacy and trust. Users want to transact privately, but they also want to be sure the network isn't inflating supply behind the scenes. Bitcoin solves this with a fully transparent ledger. Zcash's shielded pools hide amounts, so users have to rely on developers and miners not to cheat. The proposed upgrade would turn that trust into something verifiable — anyone could run the math and confirm the total supply matches what's expected. For privacy coins, that could be a competitive advantage if it catches on.
Shielded Labs hasn't set a firm timeline for the upgrade. The proposal needs community consensus and then a network fork, likely in a future halving or protocol cycle. Meanwhile, the Orchard bug fix is already live, but the incident may push Zcash users to demand the supply verification feature sooner rather than later. The question now is whether the proposal gains enough support to move from a plan to a patched reality.
