Written by Stephen Monn

Compiled by: Xiaobai Navigation Coderworld

In the ever-evolvingBlockchainIn the DeFi and decentralized application landscape, more and more attention is being drawn to the concept of users defining intent rather than pure transactions. This frees users from having to worry about navigating the growing complexity of DeFi and unlocks a host of additional use cases that are only now being conceived.

As individual apps already use their own different and incompatible intent structures, creating a single intent that can be used by all users, apps,walletIt makes sense for common intent standards to be shared and understood by software, solvers, searchers, etc.

To help composability and lower barriers to entry, we propose ERC-7521, a smart contract that supportscontractwalletStandards of general intent.

What is User Intent?

Since this space is so new, the definition of intent is a bit vague at the moment. In general, the term is often used to refer to a user’s expression of a desired on-chain outcome or final state. For the purposes of this specification,intentionDefined as a set of actions and expectations set by the user. These actions and expectations can be combined with other intent actions and expectations in an effort to satisfy the common interests of all parties involved.Xiaobai NavigationSame and greatest interests.

The series of on-chain operations that satisfy all parties involved is calledsolutionSpecialized solvers (similar to bundlers in ERC-4337) will compete to find the solution that provides the highest satisfaction to users. This can be achieved, for example, by finding the best/most efficient on-chain path, leveraging off-chain liquidity sources, combining the intent of different users to leverage common needs, etc., even including their own intent.

Adding user intent to the account abstraction

The key to enabling universal intent is to use intelligence-basedcontractSimilar to ERC-4337, intents are signed as messages and then verified on-chain via separate transactions. These signed messages are then propagated in their own memory pool.

这个规范的目标不是在链下如何精确处理、构造或管理意图的技术细节，而是为智能contractwalletCreate a framework that integrates and automatically supports the wide range of possibilities defined by the signed intents themselves. Therefore, as new intent use cases emerge, the framework also needs to allow for seamless and permissionless upgrades and code extensions.

Single entry and unlimited intent standards

To help facilitate this seamless and permissioned upgrade and expansion process, the EntryPoint contract in ERC-4337 is modeled after, but also split into two distinct parts. The first part, called the EntryPoint, is the main entry point for submitting intent resolutions and is responsible for validating intent signatures as well as running high-level intent processing logic.

The specifics of the intent handling logic are defined in separate contracts, called intent standards, which are specified by the signed intent itself. Entry points call these contracts to process an intent. It is the intent standard that defines how attached intent data and execution are handled, as well as basic off-chain rules related to denial of service attack vectors inherent to intents, such as how messages are passed to resolvers and protection mechanisms against DoS attack vectors inherent to intents.

These intent standards should be established on their own, independent of this specification. We expect that as the intent landscape becomes more mature, optimization niches emerge, and emerging use cases emerge, new intent standards with additional functionality will be created. Adoption and support of these standards will be driven by social consensus among wallet developers and intent resolvers, as well as demand from end users.

To ensure that our proposed ERC has significant functionality at an early stage, we have developed an asset-based intent standard to support most currentBlockchainWe will refine this standard (and this ERC) in the open to suit the needs of the ecosystem.

Vague but powerful structure of intent

User intent contains main data that can be broken down into two parts:

• Necessary authentication data used by the Entry Point contract to verify messages with the sender before executing them.

• Intent Standard specific additional data specified by the intent.

Intent standard data can be anything, but is always broken down into separate parts called intents.part.

The Entry Point contract does not explicitly understand what the data is, but does recognize the division into segments. The Entry Point contract calls the Intent Standard contract to process one segment at a time and enforces that the segments of an intent are always processed in the specified order. However, Entry Point allows other intents to be processed between execution segments.

These intent segments usually consist of an action that the user wants to process or check whether some condition is met. In addition, one segment can pass data to the next segment during processing. This data is called intent context data and is very useful in verifying changes between segments and avoiding recalculation of useful data. Again, making full use of this data is determined by the Intent Standard specification.

Combine intentions for maximum satisfaction

During intent processing, an intent is able to be unsatisfied for any type of condition, whether it's an unexpectedly low balance or any condition that the intent criteria might be looking for that evaluates to false. When this happens, the entire transaction is rolled back, including unrelated intents that might have occurred before it was processed.

Only when a set of intents are submitted and processed in an order that satisfies all parties are they considered spent and the resulting state is allowed to persist on-chain. It is these combinations of intents that constitute the solution and are passed to the Entry Point contract for processing.

However, just submitting a list of intents is not enough, since the segments of different intents can be in different orders. Therefore, one solution also specifies how the different intent segments should be ordered during processing (how to interleave different intent segments).

Part of the solving process typically involves the solver formulating an intent that helps satisfy a set of other intents so that they can maximize user satisfaction while generating some profit.

Conclusion: Enhancing Intent-DrivenBlockchainInteraction

The focus of the specification is to define a basic framework for smart contract wallets to connect and unlock powerful intent expressions for users, even as the landscape continues to evolve. Defining intents as a collection of smaller intent segments provides a great experience for users, reducing the number of times users need to sign. Intent segmentation and shared contextual data also help unlock powerful features without using a lot of gas. Intents can trust that all of their segments will be processed in order without manual inspection.

Universal user intent opens up a whole new world that is only now beginning to be explored. From simple gasless TokenFrom more complex conditional intents to automate processes like fund transfers from cold wallets to hot wallets or daily coin purchases with a single signed message, the possibilities for intents are vast! Our specification of the asset-based intent standard is to makeCommunityBe able to take advantage of the first of many iterations of this new framework.

The article comes from the Internet:ERC-7521 Draft: Adding User Intent to Account Abstraction Wallet

Related recommendation: Musk: Adversity has shaped me, and my pain threshold has become very high

What kind of growth experience is hidden behind the courage to take risks and high tolerance for risks? Editor: Liu Yudian Editor's Note In early 2022, a year after SpaceX successfully launched 31 satellites, Tesla sold nearly 1 million electric vehicles, and Elon became the richest man on earth, he was slightly sentimental about the motivation behind his repeated dramatic conflicts...