-
Notifications
You must be signed in to change notification settings - Fork 300
Girazoki dual token transferrable #683
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
Girazoki dual token transferrable #683
Conversation
…tial future where sending multiple assets is possible
…they have the same reserve
Codecov Report
@@ Coverage Diff @@
## master #683 +/- ##
==========================================
- Coverage 74.80% 74.44% -0.36%
==========================================
Files 82 82
Lines 7073 7150 +77
==========================================
+ Hits 5291 5323 +32
- Misses 1782 1827 +45
Continue to review full report at Codecov.
|
Several tests to be added yet (specially for errors) but major changes have been:
|
This is a draft proposal (still many things to polish) for being able to send distinct asset and fee assets, as long as they have the same reserve chain. This is intended for chains that only accept a small subset of assets as for xcm fee payment. For instance. imagine Parachain A has
pallet_assets
with an assetAssetA
andpallet_balances
with its native token isNativeA
.A reciving parachain B would only need to support xcm payments in
NativeA
, and thus if one wants to sendAssetA
it would need to send alsoNativeA
for fee payment. This is intended to potentially limit the assets a parachain supports for fee payment.Additionally, a refactor is included in preparation for the possibility to, in the future, send more than just 2 tokens to a chain