-
Notifications
You must be signed in to change notification settings - Fork 0
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
Asset Conversion Roadmap #33
Comments
no plans so far
no plans so far
already done
this now should be possible with swap credit implementation, but not planned.
implementation is ready - paritytech/polkadot-sdk#1845
should be done, when the item above is done
We aim to have a merged (into polkadot-sdk) solution in 24Q2
We aim to have a merged (into polkadot-sdk) solution in 24Q2 |
Can we update the issues?
Should become possible with paritytech/polkadot-sdk#2415 |
The Vision
Introduced in Statemint Update.
The primary goal of Asset Conversion is to close some vulnerabilities discovered by SR Labs that relate to using fixed balance conversion between DOT and other assets, even when they are
sufficient
. The number one priority for this feature is to enable fee payment in any asset such that the fee handler (i.e. the thing that sends fees to collators/treasury/burn/etc.) only receives the native asset (DOT).Much of the initial work on this was done in paritytech/substrate#12984 and paritytech/substrate#14340. However, there are still many things to address.
The Plan
LPFee
Should Use aPer{Something}
Instead ofu32
polkadot-sdk#88ChargeAssetTxPayment
should accept multiple instances ofFungibles
(may actually be sorted with LocalAndForeignAssets).ChargeAssetTxPayment
Should Handle Fee Withdrawal Better When an Account Does Not Exist inSystem
polkadot-sdk#86ChargeWeightInFungibles
Should Use Asset Conversion Instead of DefaultBalanceToAssetBalance
polkadot-sdk#105Related
The text was updated successfully, but these errors were encountered: