On May 20, 2026, both Ethereum and the regulatory world illuminated their respective "signs" on-chain, each seemingly unrelated yet profoundly meaningful: on one side, Vitalik Buterin rolled out three short-term tasks for achieving native privacy on Ethereum—making privacy protocol transactions first-class citizens through AA+FOCIL, introducing a keyed nonces mechanism, and transforming the access layer around Kohaku and private reads; on the other side, the on-chain analytics platform Arkham detected that a wallet controlled by the U.S. government would transfer assets related to FTX/Alameda, which were seized during the case process, into Coinbase Prime, including about 319 ETH, approximately 643,035 DAI, and around 290,416 USDT. At a glance, these appear to be two parallel news streams: since its inception, Ethereum, as a public blockchain, has adopted a transparent ledger design where all accounts and transaction records are publicly accessible by default. The long-standing lack of privacy has drawn criticism from developers and users, forcing those with genuine privacy needs to resort to third-party mixing tools or privacy protocols. Now, what Vitalik has provided is not a distant blueprint but a pragmatic list attempting to "accelerate implementation" within the existing architecture; meanwhile, the on-chain migration of the U.S. government's assets closely resembles the continuation of previous processes for dealing with seized crypto assets, interpreted by the market as a symbolic regulatory stance rather than an immediate change in price expectations.

AA+FOCIL and Keyed Nonces Driving Privacy

In this announcement, Vitalik broke down the "short-term tasks" into three parts: AA+FOCIL, keyed nonces, and what he collectively refers to as the access layer work, Kohaku and private reads. AA+FOCIL is directly categorized under the account abstraction-related modifications, with a clear objective—transforming transactions relying on privacy protocols from "external scripts" into first-class citizens on-chain, no longer passively attached to existing transaction formats as marginal roles. When privacy transactions are regarded as native objects, packaging nodes logically need to offer stronger inclusion commitments, so users no longer have to worry that such transactions might be discarded or delayed because they are deemed "non-mainstream," thereby providing privacy interactions with an assurance close to "infrastructure treatment" at the protocol layer.

The specifically named Keyed Nonces seem more like a key that has not yet been disclosed. By its literal meaning and contextual associations, it aims to address the replay risk and inter-scenario association issues of privacy transactions: if the counts under different "keys" are independent of each other, it theoretically makes traces left by the same account across multiple privacy paths harder to automatically connect, and can constitute an additional barrier against malicious duplication and replay transactions. However, so far, there has been no further explanation from the official side regarding the specific design, parameter choices, or rollout schedule of keyed nonces. Kohaku and private reads, mentioned alongside, fall under what Vitalik groups as "access layer work," playing the role of genuinely bringing these privacy capabilities to users—making the process of initiating, reading, and verifying privacy interactions as close as possible to today's intuitive experience of ordinary transactions. All these are included in the same "short-term checklist," yet there is no corresponding implementation timeline, nor a complete long-term roadmap in sight; it resembles a highlighted to-do list, reminding the community where to exert effort in the next steps, rather than a precisely scheduled construction blueprint.

From Transparency to Being Watched: Ethereum's Privacy Pain Points

From its design onset, Ethereum chose an account-based ledger that allows "everyone to see everything": the balance of every address, the time, parties, and amounts of each transaction are permanently written into the public blockchain. For developers and auditors, this means verifiable and traceable; but for ordinary users, it feels more like a glass city: when salaries are issued, what interactions occurred at which address, and how past positions are adjusted, once an address is linked to a real identity, the financial trajectory can be long-term and systematically traced. Many only find out that their so-called "wallet mask" has nowhere to hide in front of a fully transparent ledger when former colleagues, partners, or on-chain analytics tools "follow the trail."

The gap of lacking privacy capabilities at the protocol layer has been filled by successive generations of external solutions: some rely on mixers and privacy pools to obscure fund paths, some turn to L2/L3 solutions with privacy features, while many use various off-chain tools and temporary solutions to "erase footprints." However, these tools are hardly default capabilities of the main protocol, with high access thresholds and complex operations; if used incorrectly, they are more easily flagged; they also struggle to achieve "out-of-the-box" default safety at the wallet and infrastructure layers. Meanwhile, regulatory incidents surrounding privacy tools like Tornado Cash have pushed the notion that "on-chain privacy = evading regulation" to the forefront: complete anonymity instinctively makes regulators vigilant, while total transparency overly exposes ordinary users in terms of funds and actions, resulting in a prolonged dilemma for Ethereum caught between these opposing extremes. By including "native privacy" in the short-term checklist, Vitalik is essentially addressing a question that has been avoided for many years: can personal transactions be protected from being observed by the entire network without sacrificing decentralization and auditability, thereby carving out a viable compromise between auditing, compliance, and individual privacy?

Kohaku and Private Reads Enhancing Experience

In this short-term checklist, Kohaku and private reads are explicitly included in the "access layer work," alongside AA+FOCIL and keyed nonces as priorities for the same phase. Vitalik has deliberately shifted the focus one layer up from the consensus layer: the access layer refers to components like wallets, RPC, front-end interfaces, and node services that are directly touching the user, rather than hard forks rewriting consensus rules. By classifying Kohaku and private reads here, it is already a signal—privacy is no longer just an underlying attribute discussed in the white papers and EIPs by protocol designers, but must be perceived by ordinary users in wallet and DApp interfaces as part of product experience. Meanwhile, the current publicly available information lacks authoritative disclosures on the specific technical details and timeline for these two, serving more as a proclamation of direction: native privacy must be implemented at the "user entry" layer.

Once privacy issues are addressed at the access layer, the narrative logic changes. Ideally, users need not understand cryptographic terms like zero-knowledge proofs or commitment schemes; behind the scenes, wallets and front-ends would automatically help them select routes, sign, and interact with nodes based on mechanisms like Kohaku and private reads, with users simply toggling a "protect privacy" switch within familiar interfaces. Achieving this requires more than just unilateral pushing from protocol developers: wallet teams need to adapt the signing process and account models, infrastructure service providers must offer new privacy options in RPC interfaces and node services, and front-end developers should package these capabilities into clear, non-misleading interactions for users. If the access layer doesn't align, no matter how sophisticated AA+FOCIL or keyed nonces are, they can only remain within specifications and client implementations, and native privacy is unlikely to truly transition from proposals discussed by developers to the default paths used daily by users.

Transfer of FTX Old Assets to Coinbase Prime

On the same day that the Ethereum community discussed the pathways to the implementation of "native privacy," another directional movement was rapidly magnified: Arkham monitored that a wallet labeled as controlled by the U.S. government transferred about 319 ETH, around 643,035 DAI, and approximately 290,416 USDT to Coinbase Prime on May 20, 2026. The source addresses of these assets are related to FTX/Alameda and are widely regarded as part of the funds seized in their case. Coinbase Prime, a custodial and trading platform for institutions, has previously been used by the U.S. government multiple times to manage and dispose of seized crypto assets, making this transfer more of a procedural continuation rather than an isolated "black swan operation."

However, the market's reaction to this relatively small transfer amount has been somewhat emotional. Compared to mainstream institutions that often adjust positions in the hundreds of millions, a few hundred ETH combined with several hundred thousand dollars in value is unlikely to significantly influence long-term price structures on the liquidity front, thus being viewed by many participants as a form of "symbolic fluctuation": what is truly being traded is the expectation around regulatory attitudes and disposal rhythms, rather than the 319 ETH itself. So far, neither the on-chain behavior nor public information has shown any clear signals from the U.S. government regarding the impending sale or short-term liquidation of the assets transferred to Coinbase Prime, and directly equating routine custodial actions to "market crash premonition" demonstrates more a case of narrative-driven over-interpretation.

Next Steps for Ethereum Amid Privacy Acceleration and Regulatory Shadows

On the same day, with Vitalik throwing out a short-term task list including AA+FOCIL, keyed nonces, Kohaku, and private reads for native privacy, and a wallet controlled by the U.S. government transferring around 319 ETH and several hundred thousand DAI and USDT to Coinbase Prime, the temporal overlap starkly reflects the battleground Ethereum is currently in: on the tech side, there’s an attempt to build "stealth" into the protocol stack, while on the regulatory side, compliance custodial and disposal processes are reordering once-disordered on-chain assets. If the short-term proposals Vitalik has put forth are genuinely implemented along the lines of EIPs, client implementations, and wallet support, Ethereum’s inherent impression of being “default transparent, public accounts open” will be subtly shifted—privacy will no longer be merely an external tool used by few, but may become a regular option for ordinary users in their interactions with the protocol. However, the long-standing debates of "privacy vs compliance" and "transparency vs security" will not be simply overturned by a technical roadmap; what’s truly noteworthy is how AA+FOCIL retains necessary audit space while providing strong inclusion guarantees, and how mechanisms like keyed nonces, Kohaku, and private reads receive actual responses from various global regulators when entering specific EIPs and gaining mainstream client and wallet support. Observing this main thread going forward may not involve forcefully opposing privacy and regulation but rather watching whether Ethereum can find a running space that accommodates both user privacy and the tolerances of the real world amid the tug-of-war between these two forces.

Join our community, let’s discuss and become stronger together!
Official Telegram group: https://t.me/aicoincn
AiCoin Chinese Twitter: https://x.com/AiCoinzh
OKX Benefits group: https://aicoin.com/link/chat?cid=l61eM4owQ
Binance Benefits group: https://aicoin.com/link/chat?cid=ynr7d1P6Z

免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到support@aicoin.com，本平台相关工作人员将会进行核查。