🎉 Share Your 2025 Year-End Summary & Win $10,000 Sharing Rewards!
Reflect on your year with Gate and share your report on Square for a chance to win $10,000!
👇 How to Join:
1️⃣ Click to check your Year-End Summary: https://www.gate.com/competition/your-year-in-review-2025
2️⃣ After viewing, share it on social media or Gate Square using the "Share" button
3️⃣ Invite friends to like, comment, and share. More interactions, higher chances of winning!
🎁 Generous Prizes:
1️⃣ Daily Lucky Winner: 1 winner per day gets $30 GT, a branded hoodie, and a Gate × Red Bull tumbler
2️⃣ Lucky Share Draw: 10
Recently, I experimented with a AI agent payment system called Kite on the testnet, and it turned out to be quite interesting. Initially, I wasn't very optimistic—there are too many public chains claiming to be AI-focused these days—but after a few days of testing, my opinion really changed.
In terms of actual operation, creating an agent wallet on the Ozone testnet was surprisingly simple. Traditional multi-signature wallets are complex enough to drive you crazy, but this solution uses a three-layer identity structure: my main account has the highest permissions, the AI agent is granted intermediate permissions, and there's a temporary session layer dedicated to handling scattered transactions. The clever part of this design is that I can set a daily spending limit of 50 USDC for the agent, and any attempt to exceed that is automatically rejected—no need to worry about it smartly spending all the money.
What was most impressive was experiencing the smoothness of micro-payments. The test scenario was as follows: each API call prompts the agent to pay $0.00001. On Ethereum, this tiny amount is impossible to handle because gas fees would kill you. But Kite uses state channels to reduce transaction costs to almost negligible levels, with response times under 100 milliseconds. I ran several hundred small payments in one go, and the entire process was incredibly smooth.
Of course, I also encountered some pitfalls. Closing state channels cooperatively went smoothly, but I specifically tested dispute closing, which required waiting for a challenge period to complete arbitration. This part of the experience was a bit more complex, but for most normal scenarios, it shouldn't be necessary.