HydraDX-node
HydraDX-node copied to clipboard
galacticcouncil
HydraDX node - cross-chain liquidity protocol built on Substrate
i would refactor all this as separeate task. _Originally posted by @enthusiastmartin in https://github.com/galacticcouncil/HydraDX-node/pull/708#discussion_r1432398217_
### Detailed Description We can not set a route containing pairs with LRNA, as LRNA can not be bought in omnipool. Right now the `set_route` extrinsic of route-executor fails with...
Currently we fetch all payment assets prices on initialize regardless if they are used or not. This is not very efficient, especially with a growing number of assets. https://github.com/galacticcouncil/HydraDX-node/blob/f617f3c63f24b37586bf79aecee03455e2a90cab/pallets/transaction-multi-payment/src/lib.rs#L81 Price...
### Description Soon we will have the best routes stored for each asset pairs. So it would mean we can cheaply get the price between two assets based on oracle...
to avoid spam and dust on the chain we should check that you cannot create or update omnipool position so its value is lower than some boud (for example 1000...
new extrinsic that will be similar to the `add_token`, but instead of specifying price directly it will refer to the oracle price instead
Currently sitting at 1HDX if we don't want to increase it in the future we should consider at least 10-100x to be future proof with permisionless asset registry.
gm I wonder if you're aware of the PoV sizes of the blocks produced by both Basilisk on Kusama and HydraDX on Polkadot. Our scraping services show that the PoV...
Metadata
Owner
Metadata
HydraDX node - cross-chain liquidity protocol built on Substrate