Brazil’s central bank digital currency pilot, Drex, is running into fresh obstacles as unresolved privacy issues continue to slow development. Local media reports indicate that several outside partners, including Microsoft and EY, have reduced the number of employees assigned to Drex-related work after the Brazilian central bank ended the second phase of the pilot without approving any of the privacy solutions submitted by participants.
The pullback highlights a broader problem for the project: Drex has not yet found a privacy framework capable of satisfying two difficult goals at the same time. Any proposed system must keep transaction details confidential for users while also allowing regulators to inspect activity when necessary. According to the reports cited, none of the solutions tested so far has met the central bank’s requirements on both fronts, leaving the initiative in a state of uncertainty.
Privacy Remains the Main Technical Bottleneck
The Drex pilot has been under pressure for months because privacy is not a secondary feature in the design of a CBDC—it is a core architectural issue. Brazil’s central bank has been seeking a model that can preserve transaction secrecy without undermining legal oversight. That balance is especially difficult in digital money projects, where regulators want traceability and compliance controls, while users and institutions demand confidentiality.
Reports from earlier this year had already signaled trouble. In a February update, none of the privacy proposals presented by participating vendors was found to meet the strict standards set by the central bank. Since then, there have been no major public institutional announcements clarifying the roadmap for Drex, adding to concerns that the pilot has entered a holding pattern rather than moving decisively toward its next stage.
Microsoft and EY Reduce Staffing
Among the companies involved in the effort, EY has been leading the Starlight privacy project. Local reporting says the team working on that solution has lost three members. Microsoft, which had devoted substantial resources last year to its ZKP Nova proposal, has also reduced its direct involvement.
Even so, ZKP Nova is not being abandoned entirely. The proposal will continue to be tested and supported by Hamsa, a Microsoft partner. That detail suggests that while some companies are scaling back direct resource commitments, they are not necessarily walking away from the initiative altogether. Still, the reduction in manpower signals a more cautious stance from private-sector participants after the lack of approval in phase two.
For a complex pilot such as Drex, staffing changes matter. CBDC testing requires intensive collaboration across technology providers, financial institutions, compliance teams, and policymakers. When major contributors lower headcount, development timelines can stretch, experimentation can slow, and momentum can weaken—especially when there is no clear guidance on what standards will ultimately be accepted.
Central Bank Offers Few Details on Next Steps
Brazilian central bank executive secretary Rogerio Lucca recently said the Drex team is still evaluating the project’s future. According to his remarks, technical teams are discussing possible next steps based on the results of ongoing tests. However, he did not disclose those results, nor did he provide a timeline for any decision.
That limited communication has become part of the story. Market participants and technology partners appear to be waiting for stronger signals from the central bank before committing additional resources. In the absence of a clearer direction, companies that had allocated engineers and specialists to Drex are now reassessing how much effort they should continue to devote to solutions that may require further redesign or may not be approved at all.
A Familiar CBDC Dilemma
The Drex case underscores one of the central tensions in CBDC development globally: how to reconcile user privacy with regulatory visibility. A system that is too opaque may be unacceptable to authorities concerned about illicit finance, while a system that is too transparent may fail to win trust from users and institutions seeking confidentiality in routine transactions.
Brazil’s pilot was meant to explore exactly these kinds of trade-offs, but the latest developments show how difficult they are to resolve in practice. If no privacy proposal can satisfy the central bank’s technical and policy requirements, the program risks further delays regardless of broader interest in digital currency innovation.
For now, Drex remains in limbo. The project is still being studied, tests are still being discussed, and some solutions are still under evaluation. But with no approved privacy model, no detailed official roadmap, and reduced support from key external partners, the Brazilian CBDC pilot faces a more uncertain path forward than many had expected.