Why should AI Agent framework standards be "chained"?

avatar
PANews
12-26
This article is machine translated
Show original
Here is the English translation:

Many people still do not understand why I have been advocating for AI framework standard project parties to move towards "chainification"? Perhaps it was during the previous two Bull and Bear periods, when the Chain infra carried too many expectations, and finally the era of AI Agent "applications" arrived, and everyone has a sense of fear towards the "chain". However, for AI Agents to make more reliable autonomous decisions and collaborative cooperation, they must inevitably trend towards "chainification".

The currently popular frameworks such as ELIZA, ARC, and Swarms are basically still in the "conceptual stage". This stage cannot be falsified and reduced to zero, nor can it be verified and exploded. It is basically in the stage of infancy where the valuation cannot be quantified. This is the first hurdle for issuing assets on Github, to find the possibility of landing the outlined frameworks and visions, in order to gain the consensus recognition of the market.

Whether it is to optimize the ultimate single AI Agent performance or to build a multi-AI Agent interaction and collaboration framework, ELIZA, ARC, Swarms and other frameworks essentially need to sort out a set of traceable logic and rules for calling the AGI large model API.

After all, the data is off-chain, the reasoning process is difficult to verify, the execution process is opaque, and the execution results are uncertain.

From a short-term perspective, TEE provides a set of low-cost and highly feasible off-chain Trustless landing solutions that can accelerate the application of AGI to the autonomous decision-making of AI Agents. From a longer-term perspective, a set of "on-chain consensus" is also needed to assist in becoming more reliable.

For example, ELIZA wants to build an autonomous private key custody solution for AI Agents based on its framework foundation, using the TEE secure remote authentication capability of @PhalaNetwork to ensure that the execution code of the AI-Pool is not tampered with before calling the private key signature, but this is only the first small step of TEE's role towards the AI Agent.

If we can put the complex preset execution logic into the Agent Contract, and let the Validators of the Phala chain participate in the verification together, a chain that constrains the execution details of TEE based on chain consensus will be connected. At that time, the AI Agent will drive the demand for TEE, and the TEE will drive the empowerment of the chain, and the positive flywheel will start to spin.

The logic makes sense, TEE can ensure that the private key is invisible, but how to call the private key, based on what preset rules to call, how to trigger the risk control and emergency response, etc. In the short term, it can be implemented through the open source code library to achieve transparency, but in the long run, doesn't it all rely on a decentralized verification consensus to verify and confirm in real time?

Therefore, "chainification" can accelerate the AI Agent framework to move towards the actual application and landing stage, and can also bring new incremental opportunities to the Crypto infra.

The direction is already very clear, for most people, finding and Bullish on the earliest chainified AI Agent framework and the earliest chain supporting AI Agents, this is the Alpha in the new trend of AI Agents.

Source
Disclaimer: The content above is only the author's opinion which does not represent any position of Followin, and is not intended as, and shall not be understood or construed as, investment advice from Followin.
Like
Add to Favorites
Comments