galacticcouncil / galacticcouncil/hydration-node

omnipool initialize limit

Open
#1,382 0 comments 0 reactions 0 assignees View on GitHub
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

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.