0xbbbb.eth

ERC-8065 author | Building @wallet_aa & @0xpantarhei

[0xbbbb.eth @0xbbbb_eth]

Keep building

[walletaa @wallet_aa]

🚀 https://t.co/sCOS4SlvyJ has gone open source!
The codebase includes:
🧠 Backend
🌐 Server
💻 Website

We welcome contributions from the community. Let’s build a more open future for account abstraction together!
👉 [GitHub link] (https://t.co/mQoOECrIDb)

[0xbbbb.eth @0xbbbb_eth]

https://t.co/gss1Dp5gRL

https://t.co/KxDdV6zbFz

https://t.co/vyWecew2PA

https://t.co/GfT2cJ7T3H

[0xbbbb.eth @0xbbbb_eth]

🚨 A new form of address poisoning is emerging with EIP-7702

Attackers use EOAs as contracts to batch mint fake NFTs or batch send ETH, flooding your history with lookalike addresses

Make them seem familiar (even like your own) and trick you into sending funds to the attacker

[vitalik.eth @VitalikButerin]

Now, account abstraction.

We have been talking about account abstraction ever since early 2016, see the original EIP-86: https://t.co/E4xJymAxiH

Now, we finally have EIP-8141 ( https://t.co/YD9nIpsxcC ), an omnibus that wraps up and solves every remaining problem that AA was intended to address (plus more). Let's talk again about what it does.

The concept, "Frame Transactions", is about as simple as you can get while still being highly general purpose. A transaction is N calls, which can read each other's calldata, and which have the ability to authorize a sender and authorize a gas payer. At the protocol layer, *that's it*.

Now, let's see how to use it.

First, a "normal transaction from a normal account" (eg. a multisig, or an account with changeable keys, or with a quantum-resistant signature scheme). This would have two frames:

* Validation (check the signature, and return using the ACCEPT opcode with flags set to signal approval of sender and of gas payment)
* Execution

You could have multiple execution frames, atomic operations (eg. approve then spend) become trivial now.

If the account does not exist yet, then you prepend another frame, "Deployment", which calls a proxy to create the contract (EIP-7997 https://t.co/sIQrtJDXLt is good for this, as it would also let the contract address reliably be consistent across chains).

Now, suppose you want to pay gas in RAI. You use a paymaster contract, which is a special-purpose onchain DEX that provides the ETH in real time. The tx frames are:

* Deployment [if needed]
* Validation (ACCEPT approves sender only, not gas payment)
* Paymaster validation (paymaster checks that the immediate next op sends enough RAI to the paymaster and that the final op exists)
* Send RAI to the paymaster
* Execution [can be multiple]
* Paymaster refunds unused RAI, and converts to ETH

Basically the same thing that is done in existing sponsored transactions mechanisms, but with no intermediaries required (!!!!). Intermediary minimization is a core principle of non-ugly cypherpunk ethereum: maximize what you can do even if all the world's infrastructure except the ethereum chain itself goes down.

Now, privacy protocols. Two strategies here. First, we can have a paymaster contract, which checks for a valid ZK-SNARK and pays for gas if it sees one. Second, we could add 2D nonces (see https://t.co/1cRegaXpHM ), which allow an individual account to function as a privacy protocol, and receive txs in parallel from many users.

Basically, the mechanism is extremely flexible, and solves for all the use cases. But is it safe? At the onchain level, yes, obviously so: a tx is only valid to include if it contains a validation frame that returns ACCEPT with the flag to pay gas. The more challenging question is at the mempool level.

If a tx contains a first frame which calls into 10000 accounts and rejects if any of them have different values, this cannot be broadcasted safely. But all of the examples above can. There is a similar notion here to "standard transactions" in bitcoin, where the chain itself only enforces a very limited set of rules, but there are more rules at the mempool layer.

There are specific rulesets (eg. "validation frame must come before execution frames, and cannot call out to outside contracts") that are known to be safe, but are limited. For paymasters, there has been deep thought about a staking mechanism to limit DoS attacks in a very general-purpose way. Realistically, when 8141 is rolled out, the mempool rules will be very conservative, and there will be a second optional more aggressive mempool. The former will expand over time.

For privacy protocol users, this means that we can completely remove "public broadcasters" that are the source of massive UX pain in railgun/PP/TC, and replace them with a general-purpose public mempool.

For quantum-resistant signatures, we also have to solve one more problem: efficiency. Here's are posts about the ideas we have for that: https://t.co/xzG3Jp7Yky https://t.co/WikL7gJ5qg

AA is also highly complementary with FOCIL: FOCIL ensures rapid inclusion guarantees for transactions, and AA ensures that all of the more complex operations people want to make actually can be made directly as first-class transactions.

Another interesting topic is EOA compatibility in 8141. This is being discussed, in principle it is possible, so all accounts incl existing ones can be put into the same framework and gain the ability to do batch operations, transaction sponsorship, etc, all as first-class transactions that fully benefit from FOCIL.

Finally, after over a decade of research and refinement of these techniques, this all looks possible to make happen within a year (Hegota fork).
https://t.co/p7XOgId5NN

[walletaa @wallet_aa]

ERC-8065: A New Paradigm for Privacy

[0xbbbb.eth @0xbbbb_eth]

ERC-8065 isn’t just for wrapped ERC-20 with privacy.

One unified interface. Seamless compatibility across native tokens, ERC-20s, NFTs, and beyond.

One standard. Many asset types. Native privacy.

https://t.co/ACU37P2Phx

[walletaa @wallet_aa]

Zero-knowledge Wrapped NFT (ZWNFT) is live 🚀
Privacy-preserving NFTs are no longer theoretical.

ERC-8065 isn’t just for ERC-20 — a unified interface enabling seamless compatibility across native tokens, ERC-20s, NFTs, and more. One standard, many asset types.

[0xbbbb.eth @0xbbbb_eth]

Protocol Insights #35
https://t.co/EXXV3qaXOk 🦐

[walletaa @wallet_aa]

ERC-8065 Sharing by WalletAA Team @ Pop-X Kuala Lumpur

[Joe Wait @JoeWaitOfficial]

https://t.co/Ykf8tb2FGz

[walletaa @wallet_aa]

ERC-8065 Update #5
- ERC-8065 has been accepted as a draft ERC: https://t.co/YWkLpy1Ad5
- https://t.co/FmY8quFPIg now supports ZWETH (Zero-Knowledge Wrapped ETH): https://t.co/GmnorpA4Qq
- Improved https://t.co/FmY8quFPIg UX: https://t.co/O6bPl35SPp

[walletaa @wallet_aa]

https://t.co/FmY8quFPIg UX improvements:

- Remintable balance can now be scanned directly from the asset information panel.

- The latest burn is now displayed as a hint.

Thanks to the community for the feedback!

[0xbbbb.eth @0xbbbb_eth]

ERC-8065 lets any token be permissionlessly "zk-ified" into a zk wrapper token (like ETH → WETH), adding a private layer while preserving full composability.

No dApps needed, supports both fungible & non-fungible tokens, and makes privacy a native feature of all tokens.

[walletaa @wallet_aa]

ERC-8065 has been accepted 🎉

It permissionlessly brings privacy to standard tokens using zero-knowledge proofs and a burn-and-remint pattern inspired by @EIP7503.

Let’s make privacy a native feature of tokens on Ethereum.
https://t.co/oH3ZNqSkcg

[0xbbbb.eth @0xbbbb_eth]

Wow — privacy-preserving Wrapped ETH, Wrapped ERC20, and Wrapped NFTs 🤯

[walletaa @wallet_aa]

Zero-knowledge Wrapped Ether (ZWETH) is live 🚀
Privacy-preserving WETH is here.
Try it here: https://t.co/CVQqjMdCBz

ZWERC20 (e.g. ZWUSDC) is also live: https://t.co/XplbsyS7Sg

Next up: ZWNFTs (ZWERC721 & ZWERC1155).

The generality of ERC-8065 is now proven.

[walletaa @wallet_aa]

ERC-8065 Update [2025.12.22]
Specs
- Added `data` to deposit and withdraw for extensibility：https://t.co/HufExAhAwM
- Removed fee definitions to allow flexible fee models and added preview functions for deposit, withdraw and remint: https://t.co/m7RYq9MN3i

[0xbbbb.eth @0xbbbb_eth]

The era of Account Abstraction is quietly approaching.

[walletaa @wallet_aa]

$1B EIP-7702 TVL. Not a vision. Not a promise. Already here.
https://t.co/UKJqf8Z0To

[L2BEAT 💗 @l2beat]

At DevConnect Buenos Aires, the details of EIL @ethinteroplayer - Ethereum Interoperability Layer were unveiled.

We’ve been deep-diving interop protocols for months and our initial assessment of EIL contracts (deployed on testnets already) is following 🧵👇

[zyrav21.eth @ZyraV21]

Our proposal is ready to go, looking forward for contributors and EVM enjoyers to discuss about this.

Thanks a lot to my partner in crime @0xbbbb_eth who also made this possible

@ethereum

https://t.co/lDQszpB31J

[0xbbbb.eth @0xbbbb_eth]

Protocol Insights #34
https://t.co/Nf69nrio4U 🦐

[0xbbbb.eth @0xbbbb_eth]

Protocol Insights #33
https://t.co/W9OKjiMSoK🐣

[0xbbbb.eth @0xbbbb_eth]

Keep Ethereum decentralized

https://t.co/Gi69ucYtF8

[zyrav21.eth @ZyraV21]

https://t.co/EabHAeYsB2

this is the cost of sending encrypted messages using blockchain on @base , almost free. Private messaging has a lot potential over blockchain