Author: Haotian
Many people still do not understand why I have been calling for AI framework standard projects to move towards 'chainization'? Perhaps during the last two rounds of bull and bear markets, Chain infra carried too many expectations, and now that we have finally arrived at the AI Agent 'application' era, everyone feels a sense of dread towards 'chain'. However, for AI Agents to make more reliable autonomous decisions and collaborate, they must inevitably trend towards 'chainization'.
Currently, the popular frameworks like ELIZA, ARC, and Swarms are basically still in the 'concept phase'. This phase cannot be falsified to zero, nor can it be verified to explode; it is essentially in a cradle phase where valuation cannot be quantified. This is the first hurdle for issuing assets on GitHub; we need to find the feasibility of the outlined frameworks and visions in order to gain market consensus.
Upon closer examination, whether optimizing the performance of a single AI Agent to the extreme or creating a multi-AI Agent interaction and collaboration framework, frameworks like ELIZA, ARC, and Swarms essentially need to clarify a traceable logic and rules for the AGI large model API calls.
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 low-cost, high-feasibility off-chain trustless solution that can accelerate the integration of AGI applications into the autonomous decision-making process of AI Agents. From a longer-term perspective, a set of 'on-chain consensus' is also needed to assist in making this more reliable.
For example, if ELIZA wants to build an autonomous private key custody solution for AI Agents based on its framework, it can utilize @PhalaNetwork's TEE secure remote authentication capabilities to ensure that the execution code of the AI-Pool is not tampered with before invoking the private key for signing. However, this is just the first small step of TEE's role in the direction of AI Agents.
If we can embed complex preset execution logic into the Agent Contract and allow Validators of the Phala chain to participate in verification, a chain based on consensus constraints for TEE execution rules will be established. At that time, the TEE demand driven by AI Agents will set in motion a positive feedback loop empowering the chain.
The logic makes sense; TEE can ensure that private keys are not visible, but how are private keys invoked, and based on what preset rules, how are risk control emergency responses triggered, etc.? In the short term, transparency can be achieved through open-source code repositories, but in the long run, isn't it necessary to rely on a decentralized verification consensus for real-time validation?
Thus, 'chainization' can accelerate the practical application phase of AI Agent frameworks and bring new incremental opportunities alongside Crypto infra.
The direction is already very clear; for most people, finding and being bullish on the earliest chainized AI Agent frameworks and the oldest chains supporting AI Agents is the Alpha under the new trend of AI Agents.