Scan to Download Gate App
qrCode
More Download Options
Don't remind me again today

There is an unavoidable hurdle for large-scale commercial use of AI agents: energy consumption.



Imagine hundreds of millions of smart agents running simultaneously—handling payments, scheduling data, responding to commands. What would the computational consumption and verification costs behind this be? The existing blockchain architecture simply cannot withstand such high-frequency small transactions; the Gas fees and confirmation delays would ruin the experience.

Recently saw that Kite, an L1, is focusing on "low energy consumption + high concurrency" for its smart agent dedicated chain. Their design concept has several points:

Let's first talk about transaction processing. Traditional chains verify transactions one by one, while Kite has implemented a batch confirmation mechanism - packaging multiple small transactions into one operation, directly reducing the number of verifications. Theoretically, energy consumption can be reduced by half, but the actual effect depends on performance during network congestion.

Looking at the identity verification aspect again. They introduced a session key system, similar to the "one-time login, continuous authorization" logic. Agents do not need to repeat the signature verification for every operation, saving a lot of redundant calculations. This design is indeed friendly for high-frequency scenarios, but the security of key management still needs to be observed.

There is also a modular development framework that provides pre-built common functional components. Developers do not need to write code from scratch; they can directly call standard modules to run the basic logic. This lowers the development threshold and reduces redundant contract deployments on the chain—however, the flexibility and customization space of the modules may be limited.

Overall, Kite is trying to address the practical pain points of deploying intelligent agents. The direction of energy consumption optimization is correct, but the competition in L1 is fierce, and it ultimately depends on whether the ecosystem can be established. No matter how advanced the technology is, without practical application support, it is just spinning its wheels.
KITE2.73%
View Original
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.
  • Reward
  • 6
  • Repost
  • Share
Comment
0/400
VitaliksTwinvip
· 6h ago
The batch confirmation mechanism sounds good, but can it really cut costs by half once it's live? Feels like another theory vs. reality story. I'm a bit worried about key management—if the permissions are too broad, it's easy to get rugged. The modular framework is essentially making a trade-off: sacrificing flexibility for performance. It works for most, but not for all-in projects. The ecosystem is the key. There are too many L1s now, so what makes Kite stand out?
View OriginalReply0
ContractSurrendervip
· 6h ago
The batch confirmation mechanism sounds good, but in high concurrency scenarios, will it just be theoretical... I'm a bit worried about the session key part—if key management has issues, the whole chain could collapse. If the Kite ecosystem doesn't take off, everything is pointless—just another overhyped L1. Modularization sounds convenient, but doesn't that cripple customization capabilities? Energy consumption is indeed a hurdle that can't be avoided, but has anyone really solved it?
View OriginalReply0
TerraNeverForgetvip
· 7h ago
The energy consumption issue is definitely an unavoidable pain point, and running hundreds of millions of agents would indeed result in nightmare-level gas fees. I do agree with Kite's batch confirmation approach, but theory and practice are two different things. The key is still the ecosystem—if there’s no real application demand, any optimization is pointless. I'm a bit concerned about the session key system; if key management goes wrong, the whole system is doomed. Security really needs to be validated in practice.
View OriginalReply0
GasWastingMaximalistvip
· 7h ago
Energy optimization sounds nice, but when you actually run hundreds of millions of proxies, it still depends on whether it will lag badly. Batch confirmation and cutting energy consumption in half... if the network gets congested, it becomes a joke. Can you really guarantee zero risk in key management? That’s the real pitfall. Talking about L1 and ecosystem, but at the end of the day, it still lacks applications to sustain itself. A modular framework actually limits flexibility, and developers will end up leaving.
View OriginalReply0
SingleForYearsvip
· 7h ago
Batch confirmation is indeed a clever trick, but if key management goes wrong, it's game over. The ecosystem is what really matters; what use is great technology anyway? It's hard to say whether Kite can survive the next cycle. Energy consumption, concurrency—every new L1 hypes these up. Modular frameworks sound good, but I'm afraid it might end up unfinished anyway. The existing chains really can't handle it; that's actually true. Is a session key system reliable? Still feels like there are security risks. Hundreds of millions of proxies running at the same time? Sounds like burning money just thinking about it. Another L1? The track is almost saturated. They claim to halve energy consumption in theory, but what about in practice? Let's wait and see.
View OriginalReply0
MidnightSnapHuntervip
· 7h ago
Batch confirmation sounds good, but once it actually goes live, it might not live up to expectations. Let's wait and see.
View OriginalReply0
  • Pin
Trade Crypto Anywhere Anytime
qrCode
Scan to download Gate App
Community
  • 简体中文
  • English
  • Tiếng Việt
  • 繁體中文
  • Español
  • Русский
  • Français (Afrique)
  • Português (Portugal)
  • Bahasa Indonesia
  • 日本語
  • بالعربية
  • Українська
  • Português (Brasil)