Skip to content

Commit bba86df

Browse files
committed
Update content
1 parent d2f25a5 commit bba86df

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

llms.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -559,7 +559,7 @@ From a UX perspective, when designing cross-chain applications, consider who wil
559559

560560
- Option 2 - Additional sender cost:
561561

562-
- **Receiver gets**: full 100 USDT + 0.01 DOT (for ED).
562+
- **Receiver gets**: Full 100 USDT + 0.01 DOT (for ED).
563563
- **Sender pays**: 100 USDT + 0.01 DOT (for ED) + transaction and XCM fees.
564564
- More expensive for the sender, but the receiver gets full amount.
565565

@@ -22704,7 +22704,7 @@ Through the use of [asset conversion](https://wiki.polkadot.network/learn/learn-
2270422704

2270522705
### Transaction Fees
2270622706

22707-
On Asset Hub, both sufficient and non-sufficient assets can be used for paying transaction fees. For sufficient assets, Asset Hub natively converts the native asset (e.g., DOT) amount required to an asset balance, and the signer pays that asset to a collator. And for non-sufficient assets on Asset Hub, developers can leverage [asset conversion](https://wiki.polkadot.network/learn/learn-asset-conversion-assethub){target=\_blank} via a [swap](/tutorials/polkadot-sdk/system-chains/asset-hub/asset-conversion/) or an XCM `ExchangeAsset` instruction to swap the non-sufficient asset for any asset that has a [liquidity pool set up](https://wiki.polkadot.network/learn/learn-guides-asset-conversion/#create-a-liquidity-pool){target=\_blank} against the native asset or sufficient asset and use those tokens to cover for transaction fees.
22707+
On Asset Hub, both sufficient and non-sufficient assets can be used for paying transaction fees. For sufficient assets, Asset Hub natively converts the native asset (e.g. DOT) amount required to an asset balance, and the signer pays that asset to a collator. And for non-sufficient assets on Asset Hub, developers can leverage [asset conversion](https://wiki.polkadot.network/learn/learn-asset-conversion-assethub){target=\_blank} via a [swap](/tutorials/polkadot-sdk/system-chains/asset-hub/asset-conversion/) or an XCM `ExchangeAsset` instruction to swap the non-sufficient asset for any asset that has a [liquidity pool set up](https://wiki.polkadot.network/learn/learn-guides-asset-conversion/#create-a-liquidity-pool){target=\_blank} against the native asset or sufficient asset and use those tokens to cover for transaction fees.
2270822708

2270922709
!!!note
2271022710
Existing UI's, wallets, and tools may have limitations because of design decisions and/or constraints it places e.g. constructing the XCM call in a specific manner and therefore limiting the end user when in reality the Asset Hub system parachain encompasses more functionality than exposed in the third-party UI, such as the ability to pay transaction fees and XCM delivery fees in any asset.
@@ -22728,7 +22728,7 @@ For non-sufficient assets, this can be done by calling [asset conversion's swap]
2272822728

2272922729
- Option 2 - Additional sender cost:
2273022730

22731-
- **Receiver gets**: full 100 USDT + 0.01 DOT (for ED).
22731+
- **Receiver gets**: Full 100 USDT + 0.01 DOT (for ED).
2273222732
- **Sender pays**: 100 USDT + 0.01 DOT (for ED) + transaction and XCM fees.
2273322733
- More expensive for the sender, but the receiver gets the full amount.
2273422734

polkadot-protocol/architecture/system-chains/asset-hub.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ Through the use of [asset conversion](https://wiki.polkadot.network/learn/learn-
147147

148148
### Transaction Fees
149149

150-
On Asset Hub, both sufficient and non-sufficient assets can be used for paying transaction fees. For sufficient assets, Asset Hub natively converts the native asset (e.g., DOT) amount required to an asset balance, and the signer pays that asset to a collator. And for non-sufficient assets on Asset Hub, developers can leverage [asset conversion](https://wiki.polkadot.network/learn/learn-asset-conversion-assethub){target=\_blank} via a [swap](/tutorials/polkadot-sdk/system-chains/asset-hub/asset-conversion/) or an XCM `ExchangeAsset` instruction to swap the non-sufficient asset for any asset that has a [liquidity pool set up](https://wiki.polkadot.network/learn/learn-guides-asset-conversion/#create-a-liquidity-pool){target=\_blank} against the native asset or sufficient asset and use those tokens to cover for transaction fees.
150+
On Asset Hub, both sufficient and non-sufficient assets can be used for paying transaction fees. For sufficient assets, Asset Hub natively converts the native asset (e.g. DOT) amount required to an asset balance, and the signer pays that asset to a collator. And for non-sufficient assets on Asset Hub, developers can leverage [asset conversion](https://wiki.polkadot.network/learn/learn-asset-conversion-assethub){target=\_blank} via a [swap](/tutorials/polkadot-sdk/system-chains/asset-hub/asset-conversion/) or an XCM `ExchangeAsset` instruction to swap the non-sufficient asset for any asset that has a [liquidity pool set up](https://wiki.polkadot.network/learn/learn-guides-asset-conversion/#create-a-liquidity-pool){target=\_blank} against the native asset or sufficient asset and use those tokens to cover for transaction fees.
151151

152152
!!!note
153153
Existing UI's, wallets, and tools may have limitations because of design decisions and/or constraints it places e.g. constructing the XCM call in a specific manner and therefore limiting the end user when in reality the Asset Hub system parachain encompasses more functionality than exposed in the third-party UI, such as the ability to pay transaction fees and XCM delivery fees in any asset.

0 commit comments

Comments
 (0)