Stacks Founder Proposes Bitcoin Privacy Above the Base Layer

A privacy layer that leaves Bitcoin’s supply auditable

Stacks co-founder Muneeb Ali says Bitcoin could support confidential transactions without changing its base layer. In an interview with Scott Melker, he argued that transaction privacy and public verification of the network’s total supply need not be treated as an all-or-nothing choice. His proposal places privacy features in an execution layer built above Bitcoin, rather than making the underlying ledger itself confidential.

Ali said he does not expect privacy to be introduced directly at Bitcoin’s base layer, adding that he does not think it should be. His stated reason is that Bitcoin’s supply ought to remain auditable. In his view, users should be able to verify the total number of coins in circulation even if some details of individual transactions are concealed elsewhere in the system.

That distinction is central to the proposal: keep the supply-checking role of Bitcoin’s underlying network intact, while allowing applications on an upper layer to offer confidential transactions. Ali said there is nothing preventing such transactions from operating at the execution layer and described the idea as part of Stacks’ roadmap. The interview, however, did not specify a design or a launch schedule.

How the proposal fits Stacks’ broader plans

Stacks is described as a network running on top of Bitcoin that aims to make BTC programmable, faster and cheaper to use. Ali presented the privacy plan within that broader effort, rather than as a change to Bitcoin’s base protocol. The distinction matters because the proposal concerns capabilities built above Bitcoin; it does not amount to a claim that Bitcoin transactions are already private.

Ali identified three areas where Stacks intends to contribute: privacy, applications that could make Bitcoin productive through yield generation, and preparation for possible quantum-computing threats. These are described as parts of the network’s development plans, not as completed outcomes. The interview offers a broad direction for the work, but gives no implementation details or timetable for the privacy and yield-related initiatives.

For Bitcoin users, the potential attraction of Ali’s approach is a combination of two properties: more transaction confidentiality in applications and continued ability to audit total supply at the base layer. That is the intended balance he described, not a demonstrated result. The source does not explain which transaction details would be hidden, what information would remain visible, or how users would verify the system’s operation.

AI, open-source security and quantum readiness

Ali also raised the prospect that advances in AI could speed up the timeline for quantum-related threats to Bitcoin. He said 2029 may be a more appropriate preparedness target than 2030, the year he associated with the National Institute of Standards and Technology’s target. The interview presents this as his assessment; it does not establish that a quantum threat will materialize by either date.

The readiness question is tied, in Ali’s account, to the time needed to change Bitcoin. He said the network would need at least a couple of years to ship upgrades, making preparation time relevant to the dates he discussed. He also warned that disputes over Satoshi Nakamoto’s stash could make the process contentious. The source does not detail a proposed upgrade or how such disputes would be resolved.

Ali argued that Bitcoin’s underlying software needs strengthening and pointed to open-source review as one way systems can become more secure: more developers can inspect code and try to find vulnerabilities. This is a general security rationale he offered, not a claim that review alone eliminates weaknesses. His remarks also connect the future security discussion to the possibility of more capable, AI-assisted attacks.

What the proposal does—and does not—establish

The interview included a discussion of a reported Binance hack in which attackers stole $6.3 billion. Ali praised the exchange’s handling of the crisis but warned that AI-assisted attacks could expose weaknesses in existing systems and said stronger AI-based defenses would be necessary. The source does not provide further technical detail about the attack or explain how those proposed defenses would operate.

According to the account, more than half of the stolen funds were frozen on-chain. The FBI claimed North Korean-linked actors were behind the hack, while officials in Pyongyang distanced the country from the accusation and said the United States was trying to provoke it. Those competing statements are relevant context, but the report does not resolve responsibility for the incident.

The privacy plan remains a proposal on Stacks’ roadmap, and its practical value will depend on whether the network or other projects can deliver confidential transactions while preserving independent supply audits at scale. The source leaves that question open. It also provides no specific mechanism, deployment date or account of what users would need to do, so the intended balance is clearer than its eventual implementation.

Source: CryptoPotato