Recently, there has been a lot of discussion around @dappOS_com Intent Execution Network. Many people say that after Paradigm threw out intent-centric, only the AI Agent intelligent matching engine was hot for a while, and the overall progress of the intent track was not ideal.
So, what are the crux of the intent track? How should the decentralized Solver execution network be implemented? Next, let's talk about the system's views:
1) For a long time after Paradigm threw out intent-centric, the intent track was indeed lively for a while, including Anoma, Essential, dappOS, Brink and other projects. The intent track simplifies the threshold for users to participate in DeFi, can effectively connect with AI, and fits the characteristics of Mass Adoption. It is regarded as a major narrative in the bull market expectation.
However, the "abstract" nature of the concept of intent itself makes it difficult to focus on one direction and implement it in the short term. In addition to AI Agent as an optional implementation path for the intent execution network, execution methods including account abstraction, chain abstraction, trading bot, and even CEX can be included in the scope of the intent track.
Although AI intent is disruptive, it is too early and develops slowly. Other abstract intents are operating independently and cannot form a synergy. This is the ultimate reason why Paradigm threw out the intent-centric concept and then fell silent.
2) In my opinion, the slow development of the intent track mainly faces two core cruxes:
1. Intent abstraction challenges: It seems simple to say that intent can simplify users' on-chain operations, but now the on-chain environment is becoming increasingly complex. For example, new problems such as (LRT redemption, MEME's preemptive MEV) continue to introduce new complexities, making the development speed of standard simplified operation infrastructure such as cross-chain bridges, chain abstraction, and account abstraction much lower than the complexity of on-chain operations.
The single-chain environment that intent needs to solve includes: payment of Gas, social recovery, anti-MEV, one-click Approve-Cancel, minimization of slippage, automated execution, etc., involving multi-chain environments, and there will also be smart contract compatibility between chains, codec compatibility, liquidity interoperability, standard uniformity, and other complex issues such as security consensus.
In addition, there are many users whose intentions cannot rely solely on pure on-chain solutions. Currently, only asset management institutions with large capital scale and diversified trading strategies have relatively ideal solutions in terms of cost and speed: for example, when MEME coins are listed on CEX, the cheapest liquidity is usually market makers or VIP big customers of exchanges, and redeeming income assets such as LRT through DEX or official channels is far less than that of institutions that issue LRT or run nodes.
In short, it is extremely challenging to try to solve the intention experience by integration and optimization on the original complex chain infrastructure.
2. Wide range of intent: I have also written an article to analyze that common intents include centralized intent (CEX), structured intent (Pre-Confirmation), distributed intent (decentralized Solver market), and intelligent intent (AI Agent).
In my opinion, centralized intent and structured intent including account abstraction and chain abstraction are not within the key development scope of the intent track. They are all basic conditions that already exist in the track, and they need to further optimize the user experience on their basis before they can be included. As for intelligent intent, it will take until the AI Agent market matures before it can be included in the scope. At present, the development of the intent track we are discussing is more centered around the decentralized Solver market.
3) The development and implementation of the intent track is essentially about how to build a decentralized Solver execution network. How to do it? An objective and reasonable solution is:
Build a unified middleware network layer and ensure a new user experience, convenient and efficient compatible interoperability, and a decentralized security consensus mechanism, unified liquidity in line with the application market, etc.
Next, let's take @dappOS_com as an example to analyze what difficulties are faced in building a decentralized Solver market? And what product and mechanism innovations has dappOS explored?
1. Build a decentralized Solver execution network
There is a natural contradiction between the "fuzzification" of user intent and the programmability of the solution provided by the Solver solver. For example, a user who only has assets in chain A inputs a demand: I want to complete interactive hair on chains B and C. When this demand reaches the Solver open market, normally Providers will first break down the user's needs:
1) 0 wear and tear cross-chain; 2) Swap chooses ultra-low transaction slippage; 3) Avoids the high gas stage of chain transactions; and finally, after the complex path planning, bidding, platform matching, etc. of the Solver, the task is finally completed with extremely low gas wear and tear in a network with unified liquidity compatible with B and C chains.
In this process, what if the user raises a demand but the Solver does not accept it? What if the Solver runs away and rugs? What if the Solver price is too high? What if multiple Solver suppliers are competing for this task? How to incentivize if the task is successful, and how to punish if it fails, etc. A free and open Solver market must solve these problems.
The idea of dappOS is to give up asking the Solver to break down the clear and definite execution steps, and only focus on the execution results that users want (for example, B and C chains have completed the interactive staking), let the Solver provide a general quotation and tell the user what authorizations are needed (for example, authorizing the Solver to use 10USDT of the A chain, and finally the interactive staking dApp contract), and the entire execution process is fully handed over to the Solver to complete, and the user does not need to pay attention to the details of the execution process.
The result-oriented execution logic is as follows: Solver can achieve the optimal cost and efficiency by combining the "on-chain + off-chain" path.
In many cases, the cost loss will inevitably occur when sending transactions one by one on the chain. If the off-chain solution is interspersed, the comprehensive consideration of cost and efficiency can be achieved, giving users an optimal solution:
For example, if the Solver is a VIP or market maker of the exchange, the cost advantage gained by using the identity resource advantage is far greater than directly calling the AMM contract. When signing, users can choose to have a certain Solver execute. Solver can also obtain the user's fund authorization and can flexibly decide to execute the transaction on-chain or off-chain (user needs can also be aggregated and executed in parallel). In the end, only the result is the standard, giving users the cheapest and fastest execution result.
For example: In the scenario involving cross-chain funds, you can choose the cross-chain bridge on the chain or go directly to CEX for deposit and withdrawal. Solver can decide which solution to use; for example: in the scenario of redeeming LRT, the normal logic is to aggregate user redemption requests and execute them centrally. Transactions have to queue and may encounter gas congestion. Advanced logic can first advance low-interest loans on the chain and then flexibly redeem.
Anyway, with "results" as the guide, the goal is to allow Solvers to fully compete with each other, mobilize various resources and authority advantages to give users space for optimization in cost and speed. The question is, if there is "opacity" in the execution process, how to ensure security? As follows:
2. OMS minimized pledge operation mechanism
The idea of OMS (Optimistic Minimum Stake) is to predetermine the amount of compensation to users when each task fails, and then there is no need to care about how the Solver completes the task. If it fails, just liquidate the compensation assets pledged by the Solver.
At the same time, the pledge amount can be minimized for the Solver, and it only needs to exceed the compensation amount involved in the task being executed. This will also reduce the pressure on the Solver's funds. The Solver only needs to ensure that the current task is completed, and his own funds can be used for various other businesses at the same time to ensure the maximum efficiency of fund use.
3. Unified liquidity intention assets
Originally, many assets were idle on different chains, and not only liquidity could not be aggregated, but also subsequent financial derivatives such as Yield could not be innovated. dappOS defines an intentAsset intention asset, which is an asset that is completed through the dappOS intent execution network and has the Yield function.
Simply put, intent assets are like a unified liquidity layer that connects various heterogeneous chains. USDT on chain A and USDC on chain B can both circulate in the form of intentUSD on the dappOS chain. Users mint intentUSD just like gathering other on-chain assets into a "Yu'ebao" pool, and can use intentUSD as USDT on chain A or USDC on chain B.
This unified liquidity solution not only solves the problem of asset splitting caused by cross-chain environmental differences, but also solves a series of cross-chain wear and tear and idle asset income problems, killing two birds with one stone. In addition, IntentAsset itself also adopts a decentralized, non-custodial operating mechanism setting.
Why can intent assets have both convenience and Yield attributes? On the one hand, the Solver market can solve most of the user's intent needs, and there is no obvious difference from holding ordinary USDT; on the other hand, after calling the Solver comprehensive authority and capabilities, there will be a "profit" space for intersecting pure on-chain operations, and the saved capital loss will also become Yield.
Above.
Previously, I have seen many decentralized solver platform construction plans, all of which ignored the error problems of fuzzy matching and aimed to pursue 100% correctness. However, it is impossible for the intention transaction execution itself to be 100% correct. On the contrary, this framework with fault tolerance and corresponding governance mechanism constraints is more conducive to the normal operation of the solver market.
In short, although the intention track is full of difficulties, it is undeniable that it is the only way for the Crypto market to enter Mass Adoption. Because it solves the B side of Crypto composability, in the current market with too much Lego abstraction, this paradigm of hiding transaction execution and focusing only on results can bring in a larger number of users onboard.
Note: If you find the article useful, please support it with "one-click triple click" as a thank you. Friends who recognize my continuous dry content input can visit my Twitter homepage and click Substack column to subscribe (currently free), and more in-depth and professional investment research and analysis content, especially content that is not suitable for public sharing on Twitter, will be seen there.
