Skip to content

chore(v4/upgrade): apply Option C dynamicfee params in v4 migration#326

Merged
tbruyelle merged 3 commits into
mainfrom
tbruyelle/chore/dynamicfee-params
Apr 26, 2026
Merged

chore(v4/upgrade): apply Option C dynamicfee params in v4 migration#326
tbruyelle merged 3 commits into
mainfrom
tbruyelle/chore/dynamicfee-params

Conversation

@tbruyelle
Copy link
Copy Markdown
Collaborator

@tbruyelle tbruyelle commented Apr 24, 2026

Closes #285

@tbruyelle tbruyelle changed the title feat(v4/upgrade): apply Option C dynamicfee params in v4 migration chore(v4/upgrade): apply Option C dynamicfee params in v4 migration Apr 24, 2026
@tbruyelle tbruyelle force-pushed the tbruyelle/chore/dynamicfee-params branch from 27cf5a9 to 346b846 Compare April 24, 2026 11:55
Copy link
Copy Markdown
Collaborator

@giunatale giunatale left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

@tbruyelle tbruyelle merged commit d4fbeb2 into main Apr 26, 2026
14 checks passed
@tbruyelle tbruyelle deleted the tbruyelle/chore/dynamicfee-params branch April 26, 2026 12:24
giunatale added a commit that referenced this pull request May 4, 2026
…micfeeParams` (#330)

In #326 the code missed adding an important piece that would create a
panic if state is exported and then imported again, and in any case an
inconsistency that may also cause unexpected behavior:

The param changes where only set in the store with `SetParams`, but
where not actualized in the same way done by `UpdateParams`.

This PR adds the missing `NewState` plus `SetState` required to complete
#326
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Investigate dynamicfee module behavior

3 participants