Many people still do not understand why I have been advocating that AI framework standard projects should move towards 'chainization'? Perhaps during the previous two bull and bear cycles, Chain infra carried too many expectations, and now that we have finally reached the AI Agent 'application' era, there is a sense of dread towards 'chains'. However, for AI Agents to make more reliable autonomous decisions and collaborate, they must inevitably trend towards 'chainization'.
The currently popular frameworks like ELIZA, ARC, and Swarms are basically still in the 'concept stage', a stage that cannot be falsified and go to zero, nor can it be verified and explode; it is essentially in a period where valuation cannot be quantified. This is the first hurdle for issuing assets on GitHub; we need to find landing possibilities for the outlined frameworks and visions to gain market consensus.
If we examine frameworks like ELIZA, ARC, and Swarms, whether optimizing the performance of a single AI Agent or facilitating multi-AI Agent interaction and collaboration, they fundamentally need to outline a traceable logic and rules for 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, highly feasible off-chain trustless solution that can accelerate the application of AGI 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 to become more reliable.
For example, if ELIZA wants to build an autonomous private key custody solution for AI Agents based on its framework, it uses @PhalaNetwork's TEE secure remote authentication capability, which ensures that the execution code of the AI-Pool is not tampered with before calling the private key for signing. However, this is just the first small step of TEE's application to the AI Agent direction.
If we can put complex pre-set execution logic into the Agent Contract and have the Validators of the Phala chain participate in the verification together, a chain based on consensus constraints TEE execution rules will be established. At that point, the AI Agent will drive the demand for TEE, and the TEE will activate a positive feedback loop of chain empowerment.
The logic makes sense; TEE can ensure that private keys are invisible, but how private keys are called, based on what preset rules they are called, how risk control emergency responses are triggered, etc. can be temporarily entrusted to open-source code libraries to achieve transparency. However, looking further ahead, doesn't it all rely on a decentralized verification consensus for real-time validation?
Therefore, 'chainization' can accelerate the AI Agent framework towards practical application and also bring new incremental opportunities with Crypto infra.
The direction is already 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.