Barry Silbert’s Zcash call: what a 5% to 10% rotation from Bitcoin would mean

Barry Silbert's February 2026 comment matters because it frames privacy coins as an allocation question, not just a niche crypto debate. Reported by The Block and echoed by TradingView and Forklog, his view was that 5% to 10% of Bitcoin capital could move into privacy-focused assets such as Zcash. That is still a forecast, but it is a useful signal about how some market participants are thinking about privacy, transparency, and portfolio diversification.

What changed in the market conversation?

The immediate change is not a protocol upgrade or a regulatory decision. It is a public thesis from a prominent crypto investor that privacy demand may be large enough to pull capital away from Bitcoin. The reporting matters because Bitcoin is often treated as the benchmark asset in crypto, so even a modest rotation thesis raises questions about whether investors want more transaction privacy than Bitcoin's public ledger can provide. Zcash is relevant here because it uses zk-SNARKs and supports shielded transactions, which can hide transaction details while still allowing the network to verify validity.

For readers tracking the market in February 2026, the historical date is important. This was a reported opinion at that point in time, not evidence that capital has already shifted at scale. The practical takeaway is that privacy is being discussed as an investment theme again, and that can influence how funds, traders, and payment businesses assess asset support and customer demand.

Why does this matter for investors and operators?

For investors, the main implication is allocation discipline. A 5% to 10% rotation thesis is large enough to justify reviewing whether privacy assets belong in a portfolio framework, but not so large that it should be treated as a market consensus. The better question is whether privacy coins are being considered for speculation, for hedging against surveillance concerns, or for a longer-term belief that transaction confidentiality will matter more in digital finance.

For operators, especially businesses that handle crypto payments or treasury flows, the issue is more practical. Privacy-focused assets can complicate transaction monitoring, customer screening, and internal policy design because the available on-chain visibility may differ from Bitcoin. That does not make them unusable, but it does mean support decisions should be deliberate. Teams need to know what they can monitor, what they cannot, and which counterparties or transaction types require additional review.

What are the limitations and failure modes?

The biggest limitation is that this is still a forecast reported by third parties, not a confirmed reallocation of capital. The Block, TradingView, and Forklog all describe Silbert's view, but none of those reports prove that the market has already moved 5% to 10%. The practical response is to treat the claim as a scenario to watch, with ownership split across treasury, compliance, and risk teams rather than assumed as a settled trend.

A second limitation is that privacy features can create operational friction. Zcash's shielded transactions may improve confidentiality, but they also reduce the visibility that exchanges, payment processors, and finance teams often rely on for reconciliation and controls. The response is not to ignore privacy assets, but to define policy boundaries in advance, set monitoring expectations, and decide whether additional review is needed before enabling support.

What should readers watch next?

The next useful signals are not more commentary alone, but evidence of actual behavior. Watch for whether institutional allocators, exchanges, or payment providers change support policies, and whether privacy coins gain broader use beyond trading narratives. If the theme starts to appear in treasury policy or settlement workflows, it will matter far more than the original forecast itself.

For Radom readers, the broader lesson is that crypto payment strategy should account for asset-specific visibility and compliance trade-offs, especially when customers may want to settle in privacy-oriented tokens. The right response is usually policy first, not product enthusiasm: decide what you support, what you monitor, and what you exclude before demand forces the issue.