The Moment Privacy Moves Into the Account, Users No Longer Need to Worry About It
The rise of privacy-native wallets:
Accounts evolve, wallets must adapt
※ This post is published as a preliminary version and will be updated to the final Daily Crypto Times (DCT) format in two days.
The network is moving from the “age of scalability” into the “age of privacy.” Vitalik’s recent short-term roadmap—Account Abstraction (AA), FOCIL, keyed nonces, and access-layer privacy— signals a shift toward redesigning the account model itself around privacy.
This is not just another feature upgrade. Inside the protocol, AA smart accounts equipped with FOCIL-based privacy modules are emerging, while external wallets like MetaMask can no longer remain as mere “signing tools.”
Accounts are evolving to have privacy built in by default,
and external wallets are being redefined as platforms that connect, manage, and extend these smart accounts.
In other words:
- Privacy is moving into the account layer itself,
- and wallets are no longer the primary providers of privacy features,
but interfaces that host and operate smart accounts with embedded privacy logic.
MetaMask is not going away. But its identity as an EOA-centric wallet can no longer be sustained. Going forward, it must evolve to support AA-based smart accounts plus FOCIL-based privacy modules as a default.
Below, we break down this transition along three main axes.
1) After AA, wallets become “privacy-native” by design
AA is a technical turning point that transforms accounts from legacy EOAs into smart contract–based “smart accounts.” This shift has a direct impact on how privacy is implemented.
Wallets execute privacy logic on behalf of the user
AA-based accounts can automatically perform actions such as:
- Automatic address rotation
- Automatic stealth address generation
- Automatic attachment of ZK proofs
- Automatic metadata hiding
- Pattern hiding via keyed nonces
In short, privacy functionality becomes embedded inside the wallet’s account logic.
Privacy becomes the default without user intervention
Today, users must opt into privacy by using separate apps or protocols. After AA, the wallet can handle this automatically on the account’s behalf.
The UX of privacy disappears
Users simply send transactions as they always have. Privacy is enforced automatically inside the wallet’s smart account logic.
AA is the foundational technology that makes “privacy-native wallets” possible.
2) How AA and FOCIL relate
If AA makes accounts smart, FOCIL (First-Class Object for Code-Independent Logic) turns those smart accounts into flexible, modular platforms.
AA is the foundation that makes accounts smart
- Accounts are no longer bound to fixed EOA logic
- Accounts can execute their own custom logic
- It opens the door for privacy features to live inside the account
FOCIL extends smart accounts into a “modular platform”
- Account logic is freed from rigid, code-locked designs
- Features can be attached and detached like plugins
- Different logic can be selected automatically depending on context
- Privacy can be expanded as modular components at the account layer
AA makes the account smart,
and FOCIL turns that smart account into a flexible, extensible privacy platform.
3) How account-layer FOCIL changes privacy
FOCIL transforms accounts from “static chunks of code” into “upgradable logical objects.” This brings three major innovations to privacy.
Adding privacy features to accounts like plugins
Wallets can freely equip accounts with privacy modules such as:
- Stealth address modules
- ZK proof modules
- Metadata-hiding modules
- Address separation modules
- Keyed nonce modules
In other words, privacy functionality moves inside the account itself.
Automatically choosing different privacy strategies by context
Privacy requirements differ by situation, for example:
- Stealth addresses for specific counterparties
- ZK proofs for particular transactions
- Metadata hiding in certain network environments
FOCIL-based accounts can evaluate the context and automatically apply the appropriate privacy module. Users still just send transactions as usual.
Privacy becomes part of account logic and evolves continuously
When new privacy techniques emerge, they can be added as modules at the account layer.
- No need to redeploy the entire account
- Wallet updates can extend privacy capabilities over time
- Accounts can keep pace with advances in privacy technology
This completes a structure in which accounts evolve with privacy at their core.
Conclusion: Accounts evolve around privacy, wallets must adapt
The account model is evolving toward a world where privacy is not an option but the default. AA and FOCIL turn accounts into smart, flexible privacy platforms, and privacy becomes a native function of the account layer rather than an external protocol.
Legacy wallets like MetaMask, however, will inevitably fall behind if they fail to adapt to this shift.
The future of accounts: Privacy-centric by design
- Privacy modules are built in
- Privacy strategies are applied automatically based on context
- Modular expansion of capabilities
- The account itself becomes a privacy engine
- Privacy becomes the default of the network
The future of wallets: Evolving into smart account platforms
- They must move beyond EOA-centric designs
- They must natively support AA-based smart accounts
- They must redefine themselves as platforms that activate FOCIL-based privacy modules
- The competitiveness of a wallet will be determined by its level of privacy automation
- Wallets will no longer “provide” privacy directly,
but connect and manage privacy-native accounts as interfaces
We are entering an era where privacy is not a choice but the default state of the system. This shift will reshape not only the account model, but the entire wallet ecosystem built around it.
Younchan Jung
Researcher exploring structural shifts in AI, blockchain, and the on‑chain economy.
If you would like to read this article in Korean, please click the button below.
댓글
댓글 쓰기