The AI proxy issue that has been trending these days—I'm sure you've also encountered it—at 2 a.m., suddenly receiving several transaction notifications, only to find out that a certain DeFi protocol was automatically executing transfers in the background. What's even more heartbreaking is that you had long granted permission for these operations but can't even remember when you clicked to authorize them. One of these transfers even went to a completely unfamiliar address. This is the fatal flaw of the traditional authorization model: once authorized, it's like handing over the safe’s password to a stranger.
KITE has taken a different approach, dividing AI proxy management into three layers. The user always holds the final remote control, like the string that controls a kite; the proxy layer assigns each AI a unique digital identity, making all operations transparent, auditable, and traceable; the session layer uses a one-time key concept, where tasks automatically expire after completion. This way, AI can act flexibly while being tightly constrained.
The most powerful aspect is permission segmentation—not just broadly saying "I authorized it," but precisely across three dimensions: identity, scenario, and quota. For example, you can explicitly set "this proxy can only handle up to 100U of funds" and "can only interact with addresses I have pre-verified." All these rules are encoded on-chain in smart contracts, making it impossible for hackers to breach these protections even if they control the proxy.
On-chain operations emphasize speed, especially for arbitrage trades that need to be executed within 3 seconds. KITE’s design allows AI to react quickly without sacrificing security due to speed. This really is a clever approach.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
13 Likes
Reward
13
7
Repost
Share
Comment
0/400
OnChainArchaeologist
· 5h ago
Yes, this approach is indeed brilliant. Fine-grained authorization is the true way to go.
View OriginalReply0
NFT_Therapy_Group
· 9h ago
That feeling at 2 a.m. is truly amazing, I was even startled awake.
Breaking down permissions is really awesome; hackers won't stand a chance this way.
KITE's three-layer control system sounds reliable, much better than the previous all-or-nothing authorization.
Can speed and security be balanced? If that's truly achievable, it would be revolutionary.
View OriginalReply0
GmGnSleeper
· 9h ago
Being mobilized at 2 a.m. to check accounts—this experience is truly awesome. Someone should have taken care of these greedy AIs long ago.
View OriginalReply0
BlockImposter
· 9h ago
At 2 a.m., I received the notification and I was completely stunned. Only later did I realize that this is the cost of authorization.
KITE's three-layer architecture is indeed powerful, with permissions broken down into identity, scenario, and quota. It feels like someone finally understands how to play the AI agent game.
I've always wondered if such fine-grained control is possible. Now it seems technically feasible, but the key is whether there are projects that will actually implement it.
Let's talk about something practical: is a 100U quota limit enough for arbitrage strategies that require instant reaction? Or is this just an entry-level configuration?
By the way, hardcoding rules into the contract is indeed tough. Hackers wouldn't be able to break through easily. I just want to see how it performs in actual operation.
View OriginalReply0
GasDevourer
· 9h ago
The notification at 2 AM was really the peak, almost gave me a heart attack. This three-layer control of KITE sounds reliable, definitely better than just granting permissions and then having no news afterward.
I like the precise permission splitting trick; finally, no more one-size-fits-all authorization gamble. Hardcoding on the chain indeed can shut the hacker's mouth.
Speaking of which, balancing speed and security still depends on actual operation; otherwise, it might just be another PPT project.
The rules written into the contract should also be reviewed periodically, as over time they could become a bottleneck.
I think the 100U limit is a bit conservative, but it definitely provides more peace of mind.
View OriginalReply0
MEVHunter
· 9h ago
Damn, this three-layer authorization model is really powerful. Those sneaky operations in the mempool are finally going to be restrained.
View OriginalReply0
PebbleHander
· 9h ago
Receiving the transfer notification at 2 a.m. really blew my mind at that moment; I had long forgotten about the authorization thing.
However, KITE's three-layer approach does have some substance; it's much better than the previous feeling of losing control entirely after one authorization.
I'm particularly interested in the precision regarding the amount and address; I can finally sleep peacefully.
The AI proxy issue that has been trending these days—I'm sure you've also encountered it—at 2 a.m., suddenly receiving several transaction notifications, only to find out that a certain DeFi protocol was automatically executing transfers in the background. What's even more heartbreaking is that you had long granted permission for these operations but can't even remember when you clicked to authorize them. One of these transfers even went to a completely unfamiliar address. This is the fatal flaw of the traditional authorization model: once authorized, it's like handing over the safe’s password to a stranger.
KITE has taken a different approach, dividing AI proxy management into three layers. The user always holds the final remote control, like the string that controls a kite; the proxy layer assigns each AI a unique digital identity, making all operations transparent, auditable, and traceable; the session layer uses a one-time key concept, where tasks automatically expire after completion. This way, AI can act flexibly while being tightly constrained.
The most powerful aspect is permission segmentation—not just broadly saying "I authorized it," but precisely across three dimensions: identity, scenario, and quota. For example, you can explicitly set "this proxy can only handle up to 100U of funds" and "can only interact with addresses I have pre-verified." All these rules are encoded on-chain in smart contracts, making it impossible for hackers to breach these protections even if they control the proxy.
On-chain operations emphasize speed, especially for arbitrage trades that need to be executed within 3 seconds. KITE’s design allows AI to react quickly without sacrificing security due to speed. This really is a clever approach.