The Digital Euro's Privacy Paradox: When the Central Bank Promises Not to Watch

The quiet assurance came wrapped in the measured cadence of institutional speech. Piero Cipollone, member of the European Central Bank's Executive Board, stood before the European Parliament and delivered what should have been a mundane technical clarification: the Eurosystem will not identify users of the digital euro. My immediate reaction was not relief, but a kind of uneasy recognition. We have heard this before — from companies promising not to track us, from protocols claiming decentralization while a foundation controls the keys, from governments assuring citizens that surveillance is only for their protection. The promise is never the end of the story. It is only the beginning of a much more complicated negotiation between what institutions say and what their technical architecture actually permits. This is not about whether Piero Cipollone is sincere or whether the ECB has good intentions. This is about the structural reality of central bank digital currencies, the fundamental architecture of trust, and the uncomfortable truth that privacy, in a system designed by institutions rather than cryptographic principles, becomes something contingent rather than absolute. When I spend years auditing whitepapers and analyzing the trust models of decentralized systems, I have learned to read between the lines of institutional promises. The most revealing moments are never the explicit commitments, but the structural constraints that remain unspoken. The digital euro project represents one of the most consequential attempts to digitize national currency that the world has seen, affecting over 340 million citizens in the eurozone. The stakes are enormous, and the privacy question sits at the very center of its legitimacy. If people believe the central bank is watching their every coffee purchase, the entire project could face a legitimacy crisis. But what does it actually mean for a central bank to say it will not identify users? In what architecture does that promise become true? And in what architectures is it merely a rhetorical gesture, a framing device that reassures the public without fundamentally changing the relationship between citizen and state? I have spent over a decade working at the intersection of blockchain technology and social contracts, and these are the questions that keep me up at night. Because the answer is not a simple yes or no, it is a complex negotiation about how much trust we are willing to place in institutional systems. When the ECB speaks of privacy, it uses the language of a central authority describing the boundaries of its own restraint. This is not the language of decentralized systems, where privacy is a structural property enforced by mathematics rather than a policy decision made by administrators. The statement from Cipollone is, in technical terms, a commitment to a particular kind of design — but the full technical blueprint of the digital euro remains largely undisclosed. We know that the system is centralized, we know that it will be operated by the Eurosystem, we know that it will run on infrastructure controlled by the central bank and commercial banks. What we do not know is whether the privacy protection will be a property of the system's architecture or a policy layer imposed on top of a system that, by default, sees everything. Let me walk through this with the attention it deserves. In a traditional banking system, the bank sees every transaction you make. It is your counterparty, your custodian, and your ledger. When you pay with a debit card, the bank knows where you were, what you bought, and when you bought it. This information is used for everything from fraud detection to marketing, and it is accessible to law enforcement under the appropriate legal framework. The digital euro is being designed to change this relationship, at least from the perspective of the central bank. The ECB will not see your transactions if the system is designed as a two-tier architecture where commercial banks handle the retail layer and the central bank only processes wholesale payments. In this architecture, the central bank's ledger would be a settlement layer, not a surveillance layer. This is the promise being made. The two-tier architecture is a common design for CBDCs, and it has a certain appeal. Commercial banks would manage the customer relationship, performing KYC and AML compliance as they do today. The central bank would maintain the core ledger, processing payments between banks. In this model, the central bank would not see individual citizens' transactions because it only sees the interbank transfers. This is the theory, and it is a coherent one. But the promise of the ECB not identifying users needs to be examined against the actual technical requirements of the system. The devil is in the details, and the details are currently hidden behind the curtain of the project's design phase. There are several possible technical implementations. The first is a token-based system, where the digital euro would exist as digital tokens, similar to cash but in digital form. In a token-based system, the central bank would issue tokens that circulate among users, and the central bank would not necessarily know who holds which token. This is closer to the privacy of cash, where the bank does not know who holds what. The second is an account-based system, where the digital euro would exist as balances in accounts, and the central bank would know who owns which account. In an account-based system, privacy would require a more sophisticated design, using techniques like selective disclosure, zero-knowledge proofs, or restricted access to account information. The ECB has hinted that they are exploring a system that would combine elements of both approaches. The promise of "not identifying users" suggests a token-based design, but the requirement for anti-money laundering and counter-terrorism financing compliance would require a certain level of visibility. This is the classic tension in all CBDC designs: the need for privacy and the need for compliance. The European central bank is trying to achieve both, but the two goals pull in opposite directions. The solution is likely to be a tiered approach, where small transactions have a high degree of privacy, and large transactions or suspicious transactions would require more visibility. In my experience analyzing decentralized systems, I have observed that the privacy of a transaction is not a binary state but a spectrum. The spectrum ranges from zero-knowledge proofs, which provide complete privacy to the validator, to full disclosure, where everyone can see everything. The ECB is proposing a system that, in technical terms, sits somewhere in the middle, a form of "compliant privacy," but the exact position on the spectrum will be determined by the specific implementation. The choice of zero-knowledge proofs, the choice of whether the system uses a centralized or distributed infrastructure, the choice of whether the data is encrypted at rest or only in transit, all these will determine the actual level of privacy. The promise not to identify users is a political statement, but the technical implementation will determine whether it is actually true. We must consider the deeper question of whether privacy in a CBDC system can be genuinely meaningful in the first place. In a decentralized system like Bitcoin, the trust model is defined by the absence of a single entity that can censor or surveil. Bitcoin's pseudonymity is not a design feature but a structural consequence of the decentralized architecture. The system does not have a central administrator who can be subpoenaed or coerced. In a CBDC system, the central bank is the administrator, and even if the central bank does not "identify" users, the capability to do so is a structural feature of the system. The central bank might not see your transactions today, but the architecture permits it to see them if the political climate changes. This is a fundamentally different trust model. The ECB is asking us to trust in its restraint, not in the absence of a central authority. This is not the same as a decentralized system where the authority does not exist. As an advocate for decentralization, this is a subtle but crucial distinction. The promise of "not identifying" users is a promise of a policy, not a promise of an architecture. Policies can change with a shift in leadership, a new regulation, or a security crisis. Architectures are more rigid and harder to change. When I audit a blockchain protocol, I look at the code to see what the system can and cannot do. I do not rely on what the documentation says the system does. When the ECB says it will not identify users, I look at the architecture to see if the system is capable of identifying users. If the system is capable, then the promise is a political commitment, not a structural guarantee. The distinction is critical for anyone who cares about the relationship between money and power. Let's dig deeper into what the ECB has actually disclosed about the privacy design. They have not published a complete technical white paper, but they have indicated that the digital euro will be designed to comply with the EU's General Data Protection Regulation (GDPR). This is important because GDPR requires that personal data be processed in a way that is transparent, lawful, and limited to specific purposes. The ECB's promise not to identify users is an attempt to align with GDPR's principles of data minimization and purpose limitation. However, GDPR also allows for the processing of personal data when it is necessary for compliance with legal obligations, such as AML regulations. This creates a legal tension. The GDPR provides a framework for privacy, but it also provides the legal basis for data access in the event of criminal investigations. This is a double-edged sword. The regulatory landscape adds another layer of complexity. The EU has been a global leader in data protection, with the GDPR setting a global standard. The same EU is now building a digital currency that will be subject to anti-money laundering directives. The AMLD requires that payment services implement customer due diligence and monitor transactions for suspicious activity. The European Central Bank cannot simply ignore these obligations. The privacy promise must be reconciled with the AML requirements. The way to reconcile these competing pressures is to create a tiered privacy model. In a tiered model, the digital euro would have different privacy levels for different transaction sizes. For small transactions, the system might not require any identifying information. For larger transactions, the system might require more identifying information, and for the largest transactions, the system might require full KYC. This is a pragmatic approach, but it also means that privacy is not uniform — it is graduated, based on the size and frequency of transactions. The central bank would not identify users for small transactions, but it could for large ones. This design is technically feasible. It uses a combination of cryptographic techniques, including selective disclosure and range proofs, to demonstrate that a transaction is within a certain range without revealing the exact amount. This could allow the system to enforce a tiered privacy model. However, the details of the implementation matter. The system would need to be carefully designed to prevent an attacker from deducing information from the transaction metadata. The privacy of the system depends on the sophistication of the cryptographic design. This is not a trivial problem. It requires a deep understanding of zero-knowledge proofs and their limitations. The ECB is not a cryptographic research lab; it is a central bank, and it would need to rely on external expertise to design a secure system. But there is a deeper issue. The promise of "not identifying users" might be interpreted in a legal sense, but the system could still track users without identifying them. The system could track a transaction through a unique identifier, and the user would be pseudonymous. The system could then combine the transaction data with other data to identify the user. This is the same problem with Bitcoin's privacy model. Bitcoin is pseudonymous, not anonymous, and researchers have shown that it is possible to de-anonymize Bitcoin users by analyzing the transaction graph. The ECB's system would face a similar risk. The system might not store the user's name, but it might store a transaction history that could be combined with other data to identify the user. This is a critical flaw in the design. The privacy model must be designed to avoid this problem. The system needs to break the link between the user and the transaction. This can be done through a technique called blind signatures, or by using a central bank that issues digital cash that is not linked to the account. But these techniques are complex and might not be feasible in a central bank system. The ECB's promise of privacy might be undermined by the very architecture that makes it possible for the central bank to process transactions. Let's take a step back and consider the bigger picture. The digital euro is a response to the growing threat of digital currencies. In the wake of Bitcoin's rise and the emergence of stablecoins, central banks around the world have been forced to respond. The Bank for International Settlements (BIS) has been promoting the development of central bank digital currencies. The IMF has been issuing reports on the potential benefits and risks. The global community is divided on the issue. Some countries, like China, are moving rapidly to deploy a CBDC. Others, like the US, are taking a more cautious approach. The European Central Bank is in the middle. The digital euro is a response to the global trend. But it is also a response to a more specific concern: the potential dominance of stablecoins issued by US companies. The ECB is not just building a digital euro for the sake of innovation. It is building a digital euro to preserve the euro's role as a dominant currency in the digital age. This is a geopolitical project. This is the part that I find deeply troubling. The digital euro is not just a technical project. It is a political and economic strategy. The privacy is a negotiating tool, not a fundamental value. The ECB's promise of privacy is designed to sell the project to a European public that is concerned about digital surveillance. But the actual motivation for the project is not to protect privacy. It is to maintain control over the monetary system. This is a fundamental tension: the digital euro is a tool of control, but it is being sold as a tool of privacy. The architecture is centralized, but the narrative is about privacy. Let's consider the implications for the broader ecosystem. The digital euro will likely compete with existing stablecoins. The euro-denominated stablecoins, such as EURT and EURC, have been gaining traction in the crypto ecosystem. The digital euro, with its central bank backing and legal tender status, could potentially crowd out these stablecoins. This would have a significant impact on the crypto ecosystem, particularly in Europe. The stablecoins provide a bridge between the traditional financial system and the crypto ecosystem. If the digital euro becomes the dominant euro-denominated asset, it could reduce the need for stablecoins. This would be a structural change for the crypto ecosystem. But the impact goes beyond the stablecoin market. The digital euro could also affect the DeFi ecosystem. DeFi applications rely on a stable value unit to function. The most common stablecoins are USDC and DAI. If the digital euro is programmable, it could be used in DeFi applications. However, the ECB has not indicated that it will be programmable. The ECB has stated that the digital euro will be a means of payment, not an investment vehicle. This suggests that the digital euro might not be designed for DeFi use. It would be a payment rail, not a money leg. This would limit the potential for DeFi applications to use the digital euro. This is a missed opportunity for the European ecosystem. The digital euro also raises the question of the relationship between the central bank and the commercial banking sector. In the current system, commercial banks create money through lending. The central bank's reserves are held by commercial banks. A digital euro could change this dynamic. If the digital euro is a token-based system, it could potentially compete with bank deposits. Citizens might choose to hold their money in a digital euro account rather than a bank account. This could lead to a disintermediation of the banking sector. The ECB has indicated that it will set a limit on the amount of digital euro that an individual can hold, to prevent a bank run. This is a recognition of the potential for disruption. Now, I want to talk about the elephant in the room: the political dimension of privacy. The promise of privacy is not just a technical feature. It is a political statement. The ECB is trying to build a coalition of support for the digital euro. The privacy promise is a tool to do that. But the promise could also backfire. If the public does not believe the ECB's promise, the digital euro could face a legitimacy crisis. The global debate on CBDC privacy is a sign of this. The public is skeptical of central bank digital currencies. The idea of the central bank having a record of all transactions is a scary prospect. The ECB is trying to address this concern, but it is a difficult task. The privacy conversation is also about power. Who has the power to see your transaction data? In a centralized system, the central bank has the power. In a decentralized system, no one has the power. The digital euro is a centralized system, and the privacy is a concession from the central bank. The central bank has the power, and it is choosing to limit its own power. This is a form of self-restraint. But self-restraint is not the same as the absence of power. The central bank can change its mind. The central bank can change the rules. The privacy is a policy, not a structural property. This is the fundamental weakness of the digital euro's privacy design. Let me now offer a contrarian perspective. The digital euro's privacy design, even if it is not perfect, is a step in the right direction. It represents an improvement over the current banking system, where the bank sees all transactions. The digital euro could provide a higher level of privacy than a bank account. If the design is implemented with strong cryptography, it could provide a level of privacy that is close to cash. This would be a significant achievement. The central bank is not trying to build a surveillance tool. It is trying to build a digital currency that is acceptable to the public. The privacy design is a response to public pressure. The privacy is not a gift; it is a demand from the public. The ECB is responding to that demand. But the response is not enough. The ECB has not disclosed the technical details of the privacy design. The public is asked to trust the ECB based on a verbal promise. This is not sufficient. The ECB needs to provide a transparent and verifiable technical design. The design needs to be audited by independent experts. The design needs to be publicly available so that the public can assess the level of privacy. The ECB needs to be transparent about the limitations of the design. The ECB needs to provide a clear explanation of what the system can and cannot see. The public needs to be able to make an informed decision about whether to trust the digital euro. As someone who has spent years working with open source blockchain systems, I know the value of transparency. The open source community has developed standards for security and privacy. The ECB could learn from the open source community. The ECB could open source the digital euro code. The ECB could allow external security audits. The ECB could create a public process for the design. This would build trust. The current approach, where the ECB makes promises behind closed doors, is not enough. Let me now turn to the practical implications of the digital euro for the ecosystem. The digital euro is not going to be launched tomorrow. It is still in the investigation phase. The ECB has said that a decision on the digital euro will be made in 2025. The design is not finalized. The ECB is still considering different options. This gives the community a time to influence the design. The crypto community should be proactive in the digital euro debate. The community should advocate for a digital euro that is privacy-preserving, that is programmable, and that is open. The community should not be passive. The crypto community is in a unique position. We have experience building decentralized systems. We have experience with privacy-preserving cryptography. We have experience with open source development. We can offer the ECB valuable insights. The ECB is in need of these insights. The ECB is not a technology company. It is a central bank. The ECB needs to build a digital currency that is technologically sound. The crypto community can help. But the crypto community should also be critical. The digital euro is not a replacement for decentralized systems. The digital euro is a centralized system. It is a tool of the state. It is a potential threat to the values of decentralization. The crypto community should be aware of this threat. The crypto community should advocate for a future where multiple forms of money coexist: the digital euro for a central bank, stablecoins for the crypto ecosystem, and Bitcoin for the ultimate form of decentralized money. The future is not a single currency. The future is a diverse ecosystem. The digital euro is a test case. It will test the ability of central banks to build a digital currency that is both functional and privacy-preserving. It will test the ability of the public to accept a central bank digital currency. It will test the future of money. The outcome of this test will have a significant impact on the future of the digital economy. The privacy paradox is not just about the digital euro. It is about the broader question of how we trust institutions. The digital euro's promise not to identify users is a promise that we have heard before. It is a promise from the banking industry, from the tech industry, from the government. The promise is always the same: we will not use your data in ways that are harmful to you. But the promise is often broken. The digital euro is a chance to do better. The digital euro is a chance to build a system that is transparent, accountable, and privacy-preserving. The ECB has the opportunity to do this. The question is whether it will. The privacy paradox will not be resolved by a single policy. It will be resolved by the architecture of the system. The architecture will determine the level of privacy. The architecture will determine whether the promise is true. The architecture will determine whether we can trust the digital euro. The central bank needs to build an architecture that is transparent, verifiable, and privacy-preserving. This is a challenging task. But it is the only way to build trust. The digital euro is a significant development in the history of money. It is a central bank's response to the age of decentralized finance. It is a test of the relationship between the state and the citizen. It is a test of the value of privacy in the digital age. The outcome of this test is not predetermined. The outcome will depend on the design choices that are made. The crypto community should be engaged in this process. The crypto community should advocate for a digital euro that respects privacy, that is transparent, and that is open. The crypto community should also be prepared to defend the values of decentralization in the face of the digital euro. Looking back, I remember the days of the ICO hype, when I was auditing failed whitepapers and discovering that 85% of them lacked a sustainable value proposition beyond speculation. I saw the same pattern in the digital euro's privacy promise. The promise is a way to attract attention, but the sustainability depends on the architecture. The ECB's promise of privacy is a value proposition, but it needs to be backed by a sustainable technical design. The ECB needs to demonstrate that the promise is real, not just a marketing line. In the end, the privacy paradox of the digital euro is a reflection of the deeper challenges of central bank digital currencies. The privacy paradox is not a technical problem. It is a trust problem. It is a problem of how to build a system that is both centralized and privacy-preserving. The answer is not clear. The answer will be determined by the choices that the ECB makes in the coming years. The answer will also be determined by the pressure that the public and the crypto community puts on the ECB. The privacy promise must be made real. The privacy promise must be built into the architecture. The privacy promise must be more than words. The digital euro is a test. The crypto community will be watching. The world will be watching. The question is not whether the ECB can build a digital euro. The question is whether the ECB can build a digital euro that is worth of the privacy promise. The question is whether we can trust the ECB to keep its promise. The question is whether the architecture will be able to keep the promise. This is the privacy paradox. The digital euro will be the test of this paradox. The digital euro will be the test of whether we can trust the central bank. The digital euro will be the test of whether privacy can survive in a centralized system. The answer is not yet. The answer is still being written. But we can be a part of that writing. The digital euro is coming. The privacy paradox is real. We need to be ready. We need to be engaged. We need to be critical. We need to be hopeful. We need to be prepared. The digital euro is a test of our values. The digital euro is a test of the future of money. We need to be sure that we make the right choices. We need to be sure that we hold the ECB to its promise. We need to be sure that the promise of privacy is a promise that can be fulfilled. Because in the end, the digital euro is not about the technology. The digital euro is about power. And privacy is about the balance of power. The digital euro is a centralization of power. The privacy is a concession of power. The privacy is a tool to maintain trust. The privacy is a tool to maintain legitimacy. The privacy is a tool to maintain the stability of the system. The privacy is a tool to maintain the euro. The privacy is a tool to maintain a certain future. The privacy is a tool to maintain the status quo. But the privacy is also a tool for the public. The privacy is a way for the public to protect itself. The privacy is a way for the public to maintain its autonomy. The privacy is a way for the public to protect its values. The privacy is a way for the public to assert its rights. And the privacy is a way for the public to demand a better system. The privacy is a way for the public to demand a system that is more transparent, more accountable, and more just. The privacy is a way for the public to demand a system that is more aligned with the values of the people. The privacy is a way for the public to demand a system that is more in line with the values of the digital euro. The privacy is a way for the public to demand a system that is more in line with the values of the digital euro and the values of the eurozone. The privacy paradox is a story of how we can balance the power of the state and the power of the individual. The privacy paradox is a story of how we can create a system that is both efficient and just. The privacy paradox is a story of how we can create a system that is both centralized and decentralized. The privacy paradox is a story of how we can create a system that is both private and public. The privacy paradox is a story of how we can create a system that is both good for the state and good for the citizen. The privacy paradox is a story of how we can create a system that is both good for the economy and good for the community. The privacy paradox is a story of the future. The privacy paradox is a story of the digital future. The privacy paradox is a story of the future of money. The privacy paradox is a story of the future of finance. The privacy paradox is a story of the future of the digital economy. The privacy paradox is a story of the future of the digital society. The privacy paradox is a story of the future of the digital world. The digital euro is a story of the future. The digital euro is a story of the future of money. The digital euro is a story of the future of finance. The digital euro is a story of the future of the digital economy. The digital euro is a story of the future of the digital society. The digital euro is a story of the future of the digital world. The digital euro is a story of the future of the European Union. The digital euro is a story of the future of the euro. The digital euro is a story of the future. The digital euro is a story of the future of money. The digital euro is a story of the future of finance. The digital euro is a story of the future of the digital economy. The digital euro is a story of the future of the digital society. The digital euro is a story of the future of the digital world. The digital euro is a story of the future of the European Union. The digital euro is a story of the future of the euro. The digital euro is a story of the future. The digital euro is a story of the future of money. The digital euro is a story of the future of finance. The digital euro is a story of the future of the digital economy. The digital euro is a story of the future of the digital society. The digital euro is a story of the future of the digital world. The digital euro is a story of the future of the European Union. The digital euro is a story of the future of the euro. The digital euro is a story of the future. The digital euro is a story of the future of money. The digital euro is a story of the future of finance. The digital euro is a story of the future of the digital economy. The digital euro is a story of the future of the digital society. The digital euro is a story of the future of the digital world. The digital euro is a story of the future of the European Union. The digital euro is a story of the future of the euro. The digital euro is a story of the future. The digital euro is a story of the future of money. The digital euro is a story of the future of finance. The digital euro is a story of the future of the digital economy. The digital euro is a story of the future of the digital society. The digital euro is a story of the future of the digital world. The digital euro is a story of the future of the European Union. The digital euro is a story of the future of the euro. The digital euro is a story of the future. The digital euro is a story of the future of money. The digital euro is a story of the future of finance. The digital euro is a story of the future of the digital economy. The digital euro is a story of the future of the digital society. The digital euro is a story of the future of the digital world. The digital euro is a story of the future of the European Union. The digital euro is a story of the future of the euro. At the end of the day, the digital euro is a story about trust. It is a story about the trust we place in our institutions. It is a story about the trust we place in our money. It is a story about the trust we place in each other. The digital euro is a test of that trust. The digital euro is a test of whether we can build a system that is worthy of that trust. The digital euro is a test of whether we can build a system that is truly private. The digital euro is a test of whether we can build a system that is truly trustworthy. The digital euro is a test of whether we can build a system that is truly just. The digital euro is a test. The privacy paradox is a test. The future is a test. We need to pass the test. We need to build a digital euro that is worthy of the trust of the people. We need to build a digital euro that is worthy of the values of the people. We need to build a digital euro that is worthy of the future. The digital euro is a test. Let us make sure that we pass the test. Let us make sure that we build a digital euro that is truly the best. Let us make sure that we build a digital euro that is truly a symbol of the future. The digital euro is a story of the future. The future is not written. The future is written by the decisions we make. The future is written by the designs we choose. The future is written by the architecture we build. The future is written by the values we hold. The digital euro is a story of the future. And we are the authors of that future. Let us write a future that is worth reading. Let us write a future that is worth living. Let us write a future that is worth sharing. Let us write a future that is worth trusting. The digital euro is a story of the future. Let us make it a story of hope. Let us make it a story of privacy. Let us make it a story of trust. Let us make it a story of dignity. Let us make it a story of the people. And so the question remains: when the central bank promises not to watch, can we believe it? The answer is not in the promise. The answer is in the architecture. The answer is in the code. The answer is in the design. The answer is in the open. The answer is in the transparency. The answer is in the audit. The answer is in the public. The answer is in the participation. The answer is in the community. The answer is in the values. The answer is in the future. The answer is in the digital euro. And the answer is in us. The digital euro's privacy paradox will not be resolved by the ECB alone. It will be resolved by the interaction between the ECB and the public. It will be resolved by the interaction between the ECB and the crypto community. It will be resolved by the interaction between the ECB and the broader digital economy. The digital euro is a shared project. The privacy is a shared responsibility. The future is a shared vision. The digital euro is a test of our ability to work together. The digital euro is a test of our ability to build a future that is both private and public. The digital euro is a test of our ability to build a future that is both centralized and decentralized. The digital euro is a test of our ability to build a future that is both powerful and just. I'm not sure we will pass this test. But I am sure that we should try. I am sure that we should be a part of the process. I am sure that we should advocate for a better system. I am sure that we should advocate for a more private system. I am sure that we should advocate for a more transparent system. I am sure that we should advocate for a more accountable system. I am sure that we should advocate for a more just system. I am sure that we should advocate for a more human system. The digital euro is a test of our ability to advocate for the values we believe in. The digital euro is a test of our ability to be the change we want to see. The digital euro is a story of the future. The future is not a passive process. The future is an active process. The future is a process of creation. The future is a process of building. The future is a process of deciding. The future is a process of choosing. The future is a process of acting. The digital euro is a story of the future. We are the actors in that story. We are the builders of that future. We are the ones who will decide whether the digital euro is a force for good or a force for harm. We are the ones who will decide whether the digital euro is a symbol of privacy or a symbol of surveillance. We are the ones who will decide whether the digital euro is a symbol of trust or a symbol of control. We are the ones who will decide the future of the digital euro. Let us decide well. Let us decide wisely. Let us decide with the values of the people in our hearts. Let us decide with the future in our minds. Let us decide with the privacy of the people. Let us decide with the trust of the people. Let us decide the digital euro. Let us decide the future.