galacticcouncil / galacticcouncil/hydration-node
omnipool initialize limit
Open
- Dominant language
- Rust
- Stars
- 208
- Forks
- 109
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 3
Description
with recent introduction of slip fee based, we need to clear up a storage in on_finalize
for this purpose, we need to allocate a weight for this operation in on_initialize
Currently, there is iteration of all assets in omnipool - and it is not bounded.
with current state of omnipool - this is no issue but in theory, although very unrealistic, it could take a lot of block weight.
Introduce a max limit or propose another solution.
Contributor guide
Assessment
This issue has not been assessed yet.