Starknet has introduced strkBTC, a wrapped Bitcoin token designed to run on its Layer 2 with an optional, Zcash-style privacy mode. The product is positioning itself as “institution-ready privacy”: you can keep balances and counterparties confidential when you need to, while still preserving provable backing and controlled disclosure for audits. Mainnet availability is scheduled for Q1 2026, and the rollout is planned in phases to reduce trust assumptions over time.
The design is aiming at a very specific tension in the market: privacy is valuable for protecting strategies and counterparties, but institutions typically cannot operate in a “black box” when auditors or regulators need visibility. strkBTC is trying to bridge that gap by combining deterministic, deposit-backed minting with dual-mode privacy and a selective viewing-key mechanism.
1/ It’s finally time for Bitcoin to get privacy.
Introducing strkBTC [₿]: a new wrapped Bitcoin token with built-in privacy capabilities.
Shield your Bitcoin balances and transfers, or don’t. You choose 🧵 pic.twitter.com/7FsloqN6Br
— Starknet (Privacy x BTCFi arc) 🥷 (@Starknet) February 26, 2026
How strkBTC is issued and how privacy works
strkBTC is minted only when there is a verifiable Bitcoin deposit, described as deterministic issuance intended to maintain a clear 1:1 backing relationship. That matters because it reduces discretionary minting risk and makes the backing story easier to explain and reconcile. On-chain, strkBTC supports two operating modes that users can choose between depending on their needs.
In unshielded mode, it behaves like a standard ERC-20: balances and transfers are publicly visible and easy to audit. In shielded mode, amounts and counterparties are hidden using zero-knowledge proofs. The practical choice is simple: transparency when you want maximal composability and low friction, privacy when you want confidentiality around exposure and relationships.
The project uses STARK-based proofs native to Starknet. The text highlights an important cost tradeoff: STARKs avoid a trusted setup and are described as more resilient in a quantum-era threat model, but they come with much higher verification cost. The cited figures—around 10 million gas to verify STARKs versus roughly 300,000–500,000 gas for zk-SNARK alternatives—signal that privacy on strkBTC is not “free,” it is a premium workflow. That cost delta is a big part of why the design keeps privacy optional rather than mandatory.
The institutional “hook”: selective disclosure via viewing keys
The viewing-key mechanism is central to the institutional positioning. It allows controlled visibility of shielded transactions for authorized parties without revealing the same information to everyone on the network. This is the core compliance compromise strkBTC is selling: you can produce an auditable trail when required without broadcasting your strategy to the entire market. In principle, that directly targets a common institutional barrier to deploying Bitcoin in DeFi—unintentional public disclosure of positions, counterparties, and treasury movements.
Operationally, this shifts work onto processes rather than pure technology. Custodians and service providers will need workflows for handling selective disclosure requests, storing tamper-evident records for audits, and ensuring viewing-key access aligns with internal policy and legal process. Once “selective disclosure” exists, the institution’s risk moves from “privacy vs. no privacy” to “who controls visibility, under what authority, and how that control is logged.”
The text also flags that higher verification gas costs can affect cost modeling for custody, settlement, and on-chain strategy execution, especially in shielded mode. For treasury operators, privacy becomes a budget line item: confidentiality is valuable, but it has to be priced into execution plans. On reserves and custody, deterministic issuance reduces one category of risk, but the system still depends on reconciled bridging and custody controls to maintain a demonstrable 1:1 backing model.
Finally, Starknet describes a phased deployment with “progressive trust reduction,” aiming to move reliance away from centralized bridges toward more decentralized, permissionless mechanisms over time. That roadmap framing matters because early wrapped-asset models often carry bridge and custody trust assumptions, and institutions tend to want to see those assumptions shrink over time—not expand. The roadmap also points toward broader private DeFi functionality, including private smart contract calls and more granular disclosure controls.
The near-term workload is governance and control design: updating AML/CFT policies to incorporate selective disclosure, pressure-testing how auditors would actually access viewing keys under formal process, and modeling the cost impact of shielded transactions on treasury operations. The integration decision should hinge less on marketing claims and more on whether custody reconciliation, bridging contracts, and disclosure procedures are defensible under scrutiny.