Skip to content

Commit 3ad1215

Browse files
authored
Shaloo/ar 9251 xcs wallet (#140)
* bug fix - destination in the example is Scroll, not optimism * Revert "Fix: #AR-9464 intent fixes" This reverts commit f9b67c6.
1 parent 5c16424 commit 3ad1215

File tree

3 files changed

+9
-21
lines changed

3 files changed

+9
-21
lines changed

includes/text-snippets/ca/intent.md

Lines changed: 6 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,19 @@
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.
22

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:
144

155
* **Source Chains:** The blockchains where the user has funds/tokens.
166
* **Destination Chain:** The blockchain where the transaction will occur (where the user lacks liquidity).
177
* **Tokens and Amounts:** Specifies which tokens and how much from each source chain will be used.
188
* **Fees:** Includes CA gas fee (for cross-chain operations), protocol fee (for the service), solver fee (for the liquidity provider), and any supplied gas.
199
* **Total Amount:** The full cost, combining the transaction amount and all fees.
2010

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.
2214

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.
2415

2516
<figure markdown="span">
2617
![Example Intent Details]({{config.extra.arcana.img_dir}}/an_intent_details_example.{{config.extra.arcana.img_png}}){ .an-screenshots }
2718
<figcaption>Intent Details</figcaption>
28-
</figure>
29-
19+
</figure>

includes/text-snippets/ca/solver.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
In {{config.extra.arcana.company_name}}'s chain abstraction protocol, a solver facilitate cross-chain transactions by supplying liquidity on the destination chain.
1+
In {{config.extra.arcana.company_name}}'s chain abstraction protocol, solvers facilitate cross-chain transactions by supplying liquidity on the destination chain. After a user signs and authorizes an intent, a solver instantly provides the liquidity. In an optimal decentralized setup, multiple solvers compete to fulfill published intents.
22

3-
After a user signs and authorizes an intent, the protocol ensures that the required funds are collected on the source chains via the user's EOA and publishes the request for funds as per the user's [[concept-intent|intent]]. Solvers listen for the published intent and compete with other solvers to instantly provides the required liquidity on the destination chain.
4-
5-
In return for the liquidity provisioning services provided by the respective solvers, the CA protocol periodically settles funds periodically. While settling, it aggregates all the successful transactions made by the solver and pays through the funds collected on the source chains from the user's EOA, as agreed to in the intent.
3+
The protocol periodically settles funds with solvers who have successfully completed user intents, using tokens from the supported source chains.

includes/text-snippets/ca/unified_balance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ For instance, let us take the case where a user intends to spend 18 USDC on Scro
99

1010
To spend 18 USDC on Scroll (destination chain) with the given liquidity fragmentation, it would typically require multiple clicks and steps for swapping or bridging different assets available on the source chains, so that user can convert the assets to the desired token balance on Scroll.
1111

12-
Through chain abstraction and ability to swap cross-chain, users have the convenience to view the consolidated token balance across supported tokens and chains. This simplifies the process of sending 18 USDC on Optimism, as users can sign the intent without the need for bridging, swapping, or considering the optimal routes.
12+
Through chain abstraction and ability to swap cross-chain, users have the convenience to view the consolidated token balance across supported tokens and chains. This simplifies the process of sending 18 USDC on Scroll, as users can sign the intent without the need for bridging, swapping, or considering the optimal routes.
1313

1414
The cross-chain swap enables users to:
1515

0 commit comments

Comments
 (0)