|
1 |
| -In the [[concept-ca|chain abstraction]] context, an intent represents an objective to transact on a destination chain where user does not have sufficient funds available. |
| 1 | +In the [[concept-ca|chain abstraction]] context, an intent represents a user's request to execute a cross-chain transaction when they lack sufficient funds or liquidity on the destination blockchain. An intent specifies what the user is willing to offer (tokens from various source chains) to cover the transaction amount, gas fees, solver fees, and the {{config.extra.arcana.company_name}} chain abstraction (CA) protocol service fee. |
2 | 2 |
|
3 |
| -An intent specifies what the user is willing to offer (tokens from various source chains) to cover the transaction amount, gas fees, solver fees, and the {{config.extra.arcana.company_name}} chain abstraction (CA) protocol service fee for receiving the desired liquidity on the destination chain. |
4 |
| - |
5 |
| -By signing the intent, user agrees to perform the following in one shot: |
6 |
| - |
7 |
| -* Allow the {{config.extra.arcana.company_name}} CA protocol to collect necessary assets available in the EOA across one or more source chains to pay for the transaction and the fees. |
8 |
| -* Enable the available [[concept-solver|solvers]] in the ecosystem to provide the desired liquidity on the destination chain in the user's EOA. |
9 |
| -* Let the {{config.extra.arcana.company_name}} CA protocol settle deposited funds and applicable fees with the solvers at regular intervals. |
10 |
| - |
11 |
| -As part of the {{config.extra.arcana.company_name}} CA protocol setup, the user must complete a one-time set up of [[concept-allowances|allowances]] on every source chain. This is required before an intent can be raised for a chain abstracted transaction. Allowances are used to specify the limits of funds that can be deposited per source chain in order to receive the required funds on the destination chain. |
12 |
| - |
13 |
| -Each intent specifies: |
| 3 | +The following information is part of an intent: |
14 | 4 |
|
15 | 5 | * **Source Chains:** The blockchains where the user has funds/tokens.
|
16 | 6 | * **Destination Chain:** The blockchain where the transaction will occur (where the user lacks liquidity).
|
17 | 7 | * **Tokens and Amounts:** Specifies which tokens and how much from each source chain will be used.
|
18 | 8 | * **Fees:** Includes CA gas fee (for cross-chain operations), protocol fee (for the service), solver fee (for the liquidity provider), and any supplied gas.
|
19 | 9 | * **Total Amount:** The full cost, combining the transaction amount and all fees.
|
20 | 10 |
|
21 |
| -The intent processing begins when the user signs an intent and authorizes a transaction. Once the intent is signed by the user and submitted to the protocol, each intent is assigned a unique identifier. For every chain abstracted transaction, users can click on the 'view intent' link to see the intent details or to note down the intent identifier for future references. [[concept-intent-explorer#arcana-ca-wallet|Learn more...]] |
| 11 | +The intent processing begins when the user signs an intent and authorizes a transaction. A [[concept-solver|solver]] (a liquidity provider) steps in to supply the necessary funds on the destination chain. The protocol is responsible for settling the source chain funds with the respective solver. The intent details shows which solver provided liquidity once the intent is successfully processed. |
| 12 | + |
| 13 | +Intents are tracked via a unique identifier. Users can supply this identifier in the [{{config.extra.arcana.ca_intent_explorer_name}}]({{config.extra.arcana.ca_intent_explorer}}]) to check the intent’s status or details later. |
22 | 14 |
|
23 |
| -This intent identifier is used to track the intent status. Users can supply the intent identifier in the [{{config.extra.arcana.ca_intent_explorer_name}}]({{config.extra.arcana.ca_intent_explorer}}]) to check the intent’s status or details later. |
24 | 15 |
|
25 | 16 | <figure markdown="span">
|
26 | 17 | { .an-screenshots }
|
27 | 18 | <figcaption>Intent Details</figcaption>
|
28 |
| -</figure> |
29 |
| - |
| 19 | +</figure> |
0 commit comments