Open joepetrowski opened 1 year ago
Asset Conversion LPFee Should Use a Per{Something} Instead of u32
no plans so far
Add Benchmarking/Weights for Signed Extensions
no plans so far
ChargeAssetTxPayment should accept multiple instances of Fungibles (may actually be sorted with LocalAndForeignAssets).
already done
ChargeAssetTxPayment Should Handle Fee Withdrawal Better When an Account Does Not Exist in System
this now should be possible with swap credit implementation, but not planned.
ChargeWeightInFungibles Should Use Asset Conversion Instead of Default BalanceToAssetBalance
implementation is ready - https://github.com/paritytech/polkadot-sdk/pull/1845 needs to be integrated into runtimes (planned with the next release)
Configure Polkadot <> Kusama Bridge to Use Asset Conversion to Buy Execution #104
should be done, when the item above is done
Allow Asset Conversion Subscriptions
We aim to have a merged (into polkadot-sdk) solution in 24Q2
[Asset Conversion] Incentives Extension
We aim to have a merged (into polkadot-sdk) solution in 24Q2
Can we update the issues?
Add Benchmarking/Weights for Signed Extensions
no plans so far
Should become possible with https://github.com/paritytech/polkadot-sdk/issues/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 https://github.com/paritytech/substrate/pull/12984 and https://github.com/paritytech/substrate/pull/14340. However, there are still many things to address.
The Plan
ChargeAssetTxPayment
should accept multiple instances ofFungibles
(may actually be sorted with LocalAndForeignAssets).Related