HydraDX-node
HydraDX-node copied to clipboard
HydraDX node - cross-chain liquidity protocol built on Substrate
We don't have test where router.set_route() fails due to change in tradability flags of omnipool assets. https://github.com/galacticcouncil/HydraDX-node/blob/a0c524a6c3d7613635614588901a51546782b341/pallets/omnipool/src/types.rs#L31-L35 Scenario: DOT has BUY disabled sell DOT->HDX will pass but HDX->DOT will fail...
This PR adds: * runtime-mock - TestExternalities of the HydraDX runtime with rich data setup. This is used by the fuzzer and can be used by local (runtime integration) tests...
- [ ] DCA takes transaction fee from the budget, in the case of insufficient assets this should be swapped immediately and not accumulated by the treasury - [ ]...
If we can sneak in manual oracle activation for XYK pools would be nice (By some governance body, preferably technical commitee) _Originally posted by @jak-pan in https://github.com/galacticcouncil/HydraDX-node/issues/768#issuecomment-1959156024_
Dust the amount of tokens that are to be claimed instead of failing the transaction to exit / claim.
LM farms can be created currently only for the Omnipool subpools via a feature specific implementation @ https://github.com/galacticcouncil/HydraDX-node/tree/master/pallets/omnipool-liquidity-mining Task is to analyse which other pools would be suitable for farms...
``` Swapped { who: AccountId, pool: PoolType, operation: ( Buy | Sell ), asset_in: AssetId, asset_out: AssetId, amount_in: Balance, amount_out: Balance, fee_rate: Permill batch: Option } ``` batch is nonce...
this was recently re-benchmarked and that increased weight 30x, caused by staking dependency - this has to be optimized to be more efficient