Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Polkadot Wiki Migration] Interacting with Asset Hub #21

Closed
wants to merge 5 commits into from

Conversation

CrackTheCode016
Copy link
Collaborator

The " Interacting with Asset Hub" page was migrated from the existing Polkadot Wiki page: https://wiki.polkadot.network/docs/build-integrate-assets

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

develop/application-devs/system-parachains/interact-asset-hub.md|245 col 95| [Papermoon.Acronyms] Spell out 'III', if it's unfamiliar to the audience.
develop/application-devs/system-parachains/interact-asset-hub.md|245 col 98| [Google.Colons] ': E' should be in lowercase.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

develop/application-devs/system-parachains/interact-asset-hub.md|113 col 12| [Vale.Spelling] Did you really mean 'multilocation'?
develop/application-devs/system-parachains/interact-asset-hub.md|133 col 89| [Papermoon.Acronyms] Spell out 'REST', if it's unfamiliar to the audience.
develop/application-devs/system-parachains/interact-asset-hub.md|135 col 9| [Vale.Spelling] Did you really mean 'lookups'?
develop/application-devs/system-parachains/interact-asset-hub.md|135 col 9| [Papermoon.CustomDictionary] Did you really mean 'lookups'?
develop/application-devs/system-parachains/interact-asset-hub.md|138 col 71| [Papermoon.NotContractions] Use 'aren't' instead of 'are not'.
develop/application-devs/system-parachains/interact-asset-hub.md|156 col 5| [Papermoon.CustomDictionary] Did you really mean 'Tx'?
develop/application-devs/system-parachains/interact-asset-hub.md|156 col 5| [Vale.Spelling] Did you really mean 'Tx'?
develop/application-devs/system-parachains/interact-asset-hub.md|168 col 22| [Papermoon.Acronyms] Spell out 'DOT', if it's unfamiliar to the audience.
develop/application-devs/system-parachains/interact-asset-hub.md|168 col 26| [Papermoon.Acronyms] Spell out 'KSM', if it's unfamiliar to the audience.
develop/application-devs/system-parachains/interact-asset-hub.md|185 col 86| [Google.OptionalPlurals] Don't use plurals in parentheses such as in 'account(s)'.
develop/application-devs/system-parachains/interact-asset-hub.md|190 col 46| [Vale.Terms] Use 'relay chain' instead of 'Relay chain'.
develop/application-devs/system-parachains/interact-asset-hub.md|197 col 10| [Vale.Terms] Use 'relay chain' instead of 'Relay chain'.
develop/application-devs/system-parachains/interact-asset-hub.md|200 col 31| [Vale.Terms] Use 'relay chain' instead of 'Relay chain'.
develop/application-devs/system-parachains/interact-asset-hub.md|204 col 10| [Vale.Terms] Use 'relay chain' instead of 'Relay chain'.
develop/application-devs/system-parachains/interact-asset-hub.md|222 col 67| [Google.We] Try to avoid using first-person plural like 'we'.
develop/application-devs/system-parachains/interact-asset-hub.md|222 col 67| [Vale.Avoid] Avoid using 'we'.
develop/application-devs/system-parachains/interact-asset-hub.md|225 col 11| [Vale.Terms] Use 'relay chain' instead of 'Relay chain'.
develop/application-devs/system-parachains/interact-asset-hub.md|228 col 6| [Google.We] Try to avoid using first-person plural like 'We'.
develop/application-devs/system-parachains/interact-asset-hub.md|238 col 6| [Google.We] Try to avoid using first-person plural like 'We'.

@CrackTheCode016 CrackTheCode016 added B0 - Needs Review Pull request is ready for review and removed In Progress labels Sep 13, 2024
@nhussein11 nhussein11 self-requested a review September 23, 2024 19:21
the Asset Hub and use it natively. The relay chain will also accept DOT transfers from the Asset Hub
back to the relay chain for staking, governance, or any other activity.

Using the Asset Hub for DOT/KSM balance transfers will be much more efficient than the relay chain
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Up to you here, but I'd suggest using "the relay chain native token" or something like that rather than DOT/KSM


#### Paying Transaction Fees in Another Asset

Users in the Asset Hub can pay the fees of their transactions with assets other than DOT. The only
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, maybe:

Users have the option to pay transaction fees using assets other than the relay chain's native token.


Using the Asset Hub will require running a system parachain node to sync the chain. You can follow [these guidelines](https://github.com/paritytech/polkadot-sdk/tree/master/cumulus#asset-hub-){target=\_blank} to set up an Asset Hub node.

### Asset Transfer API
Copy link
Collaborator

@nhussein11 nhussein11 Sep 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we also will cover asset transfer API, sidecar API and TxWrapper documentation, I'm not sure if it's worth explaining those here. Maybe we can just link to the sections in the future

examples to showcase the slight differences:

1. For an XCM transfer from a parachain to a relay chain
_([example](https://polkadot.subscan.io/xcm_message/polkadot-3effaf637dd2a3ac5a644ccc693cbf58a6957d84){target=\_blank})_:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems like something is missing here since we can colons at the end

@dawnkelly09
Copy link
Collaborator

Closing this PR. This information is covered in PR #112

@dawnkelly09 dawnkelly09 closed this Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants