Recently I came across an interesting case that is worth breaking down.

In mid to late September, Halborn conducted a comprehensive audit of KITE's core contracts—GokiteAccount, KiteAirdrop, and Subnet, leaving none behind. The audit results were quite solid: only 1 low-risk issue was found, along with 5 informational feedbacks, all of which were 100% resolved. From the triggering of the safeTransfer event to the detailed handling of deadline checks, everything was meticulously examined. Later, Certik Skynet also monitored 24/7, combined with the shift-left practices of DevSecOps and the support of multi-signature wallets, the entire system remained rock solid by December 22.

The most attractive design here is actually KITE's three-layer key architecture. Many projects tout a three-layer key as a marketing gimmick, but KITE's implementation is serious—it follows the BIP32 standard directly.

How is it layered? The root key is held by the user's hardware wallet and will never be exposed. The delegated key is managed by the proxy party, making autonomous decisions within the scope of authorization. The session key is burned after use, in a single-task mode, and is destroyed immediately after the task is completed. This design perfectly fits the multi-agent scenarios of enterprises in the account abstraction implementation of GokiteAccount.sol.

Let's look at a real case to see the effect. A cross-border e-commerce company uses KITE to manage the overseas warehouse replenishment process: the purchasing agent has a monthly budget of 500,000 for general expenses and 1,000,000 for electronic products, with on-chain mandatory execution constraints, a single transaction limit of 30,000, and a daily cumulative maximum of 100,000. For suppliers on the whitelist, inventory cannot exceed 30 days. In the event of exchange rate fluctuations, non-urgent purchases are suspended—this logic was run 17 times, ultimately avoiding a potential loss of 800,000.

The more ruthless point is that even if a hacker intercepts the session key, it can only affect a single transaction. The root key is secure, and the system can trigger a full network freeze at over 150% of the limit, which can be restored after manual intervention. The transfer of permissions is also seamless—when a manager leaves, the permissions are directly inherited, and the audit logs are completely traceable.

From technical architecture design to practical application, the KITE case demonstrates the true value of account abstraction in enterprise-level scenarios.