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 has borne too many expectations, and now that we have finally reached the era of AI Agent "applications", there is a sense of fear towards "chain". However, for AI Agents to make reliable autonomous decisions and collaborate with each other, they must inevitably trend towards "chainization".
Currently popular frameworks like ELIZA, ARC, and Swarms are basically still in the "concept phase", which cannot be falsified to zero, nor can it be verified to explode; they are essentially in a stage where valuation cannot be quantified. This is the first hurdle for issuing assets on GitHub; we need to find the possibility of grounding the frameworks and visions we outline to gain consistent market recognition.
If we take a closer look at frameworks like ELIZA, ARC, and Swarms, whether for extreme single AI Agent performance optimization or multi-AI Agent interactive collaboration frameworks, they essentially need to establish a traceable set of 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 and highly feasible off-chain trustless solution that can accelerate the autonomous decision-making process of AGI applications to AI Agents. From a longer-term perspective, a set of "on-chain consensus" is also needed to assist in making it more reliable.
For example, if ELIZA wants to build an autonomous private key custody solution for AI Agents based on its framework, it uses the TEE secure remote authentication capability of @PhalaNetwork, which ensures that the execution code of AI-Pool is not tampered with before calling the private key for signing. But this is only the first small step of TEE's application to AI Agent direction.
If we can embed complex preset execution logic into the Agent Contract and have Validators from the Phala chain participate in the validation together, a chain based on consensus constraints for TEE execution details will be established. At that time, the demand for TEE driven by AI Agents and the positive feedback loop of TEE driving chain empowerment will start to operate.
The logic makes sense; TEE can ensure that the private key is not visible, but how the private key is called, based on what preset rules it is called, how risk control emergency responses are triggered, etc. In the short term, transparency can be achieved through open-source code libraries, but in the long run, it all relies on a decentralized verification consensus for real-time validation, right?
Therefore, "chainization" can accelerate the AI Agent framework towards the actual application landing stage and also bring new incremental opportunities with Crypto infra.
The direction is already very clear; for most people, finding and being bullish on the earliest chainized AI Agent frameworks and the earliest old chains supporting AI Agents is the Alpha under the new trend of AI Agents.