The abstraction of accounts is not the problem; the problem is that the 'future wallet form' has become something that only developers can barely use, and is a project experiment that ordinary users should not touch at all.

Recently, a key feature promoted by Kite is the account abstraction wallet, which is said to enable AI agents to achieve 'social recovery', 'gasless transactions', and 'batch operations'—these advanced functionalities. As a developer who has been navigating Web3 for three years, I spent a week deeply testing this system, and the conclusion is that the ideal is grand, but the reality is stark. First, let's discuss the concept of account abstraction; simply put, it upgrades traditional external accounts (EOA) to smart contract accounts, allowing for programmable control over wallet behavior. For instance, you can set up multi-signatures, whitelists, daily limits, automatic execution strategies, etc. It indeed sounds much safer and more flexible than the 'one private key rules all' model of MetaMask. Kite implemented the GokiteAccount contract based on the ERC-4337 standard, deployed on its L1 chain, with the address 0x93F5310eFd0f09db0666CA5146E63CA6Cdc6FC21. When I registered, I needed to create a traditional EOA wallet first as the 'owner', and then deploy my AA wallet instance through this contract. The entire process took about ten minutes, mainly waiting for on-chain confirmation.