Luis Enrique Muñoz Martín
Luis Enrique Muñoz Martín
Move this thread to its own issue to be solved as a tech-debt of #1805 _Originally posted by @lemunozm in https://github.com/centrifuge/centrifuge-chain/pull/1805#discussion_r1562039612_
### Description We want the macro found here: https://github.com/centrifuge/centrifuge-chain/blob/629dcfdc7495faf0427df20fb58e47fb05bccd01/runtime/integration-tests/src/utils/env.rs#L85 into the `generic` framework of `integration-test` to be able to check several events quickly and choose the `EventRange` we want to...
### Description This implies port: - `evm` module. Done in https://github.com/centrifuge/centrifuge-chain/pull/1801 - `rewards` module. Done in https://github.com/centrifuge/centrifuge-chain/pull/1805 This allows: - Remove all utilities needed right now just for the above...
# Description Continue work from https://github.com/centrifuge/centrifuge-chain/pull/1408 ~~**NOTE**: Modify base branch once [polkadot-v1.1.0](https://github.com/centrifuge/centrifuge-chain/pull/1756) is merged~~
### Description This would imply configuring a whole state with pools/loans/oracles... and later call different methods from PoolsAPI
### Description Currently, we use our runtime type `CustomMetadata` in most of our tests. This forces us to have a runtime dependency in pallets, making it harder to do refactorizations...
### Description We should determine the weight of `Oracle::update_collection()` with `PostDispatchInfo` to reduce significantly the cost of this extrinsic. Similar to what we do with `Loans::update_portfolio()`
### Description `pallet-pool-registry` is quite simple on its own. Nevertheless, the mock and benchmarks use a lot of knowledge comming from `pool-system`, breaking `pool-registry` each time `pool-system` changes. We should...
### Description Currently, `pallet-anchors` have some minor undesired issues: - 4 tests are ignored when they should have been enabled. - Some unsafe arithmetics - It uses `pallet-aura` in testing/benchmarks...
### Description The minimum fulfillment amount of a currency is computed in the backend for each currency. Now, it's stored in the `Order` struct. But this amount does not depend...