For asset -> asset pool runtime representation i chose double_map, identified by both asset ids. Don't sure if it's a good approach, as then we need to constantly apply some rule to ensure correct order. Thought about hashing or some arithmetic operations performed for both identificators, though couldn`t figure out appropriate algorithm.
generic-assets dependency replaced in favor of Currency trait on dex_parachain side, which makes implementation much more flexible. (dex_xcmp reworking still work in progress)
AssetBalances runtime storage introduced for the purpose of tracking other parachain assets. ( which are not supported on dex parachain natively)
Introduced treasury account for further fee charge.
Overflow risks are partially resolved. (Still need to rework exchange related methods).
Direct token pools implemented.
double_map
, identified by both asset ids. Don't sure if it's a good approach, as then we need to constantly apply some rule to ensure correct order. Thought about hashing or some arithmetic operations performed for both identificators, though couldn`t figure out appropriate algorithm.generic-assets
dependency replaced in favor ofCurrency
trait ondex_parachain
side, which makes implementation much more flexible. (dex_xcmp
reworking still work in progress)AssetBalances
runtime storage introduced for the purpose of tracking other parachain assets. ( which are not supported on dex parachain natively)Closes: https://github.com/subdarkdex/subdex-chain/issues/2 Partially implements https://github.com/subdarkdex/subdex-chain/issues/9