-
Notifications
You must be signed in to change notification settings - Fork 608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor[CL]: remove freezeDuration as a parameter #4724
Conversation
This reverts commit 0c1bc13.
@@ -101,7 +101,7 @@ func (n *NodeConfig) StoreWasmCode(wasmFile, from string) { | |||
|
|||
func (n *NodeConfig) WithdrawPosition(from, liquidityOut string, positionId uint64) { | |||
n.LogActionF("withdrawing liquidity from position") | |||
cmd := []string{"osmosisd", "tx", "concentratedliquidity", "withdraw-position", fmt.Sprint(positionId), liquidityOut, fmt.Sprintf("--from=%s", from)} | |||
cmd := []string{"osmosisd", "tx", "concentratedliquidity", "withdraw-position", fmt.Sprint(positionId), liquidityOut, fmt.Sprintf("--from=%s", from), "--gas=auto", "--gas-prices=0.1uosmo", "--gas-adjustment=1.3"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: Make an issue regarding this gas adjustment that had to be made for this transaction to go through
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Issue created #4774
"/osmosis/poolmanager/v1beta1/{pool_id}/estimate_out/" | ||
"single_pool_swap_exact_amount_out"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checked this, apparently it happens automatically from the proto linter, weird.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would like to see the reply to how the position updates are currently handled.
Other than that, ready to approve. Great work!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Great work.
It will be helpful to update architecture.md
with the state and updates in this PR but not-blocking for merge.
Closes: #4651
What is the purpose of the change
We no longer need the freezeDuration parameter, as we are now utilizing accumulators for all positions, and simply force users to forfeit accumulated rewards if they leave prior to the rewards minimum uptime charging period.
This PR removes the parameter and refactors various tests to achieve this.
Most notably, we no longer determine forfeiting incentives as binary, and rather iterate a position ID over the various rewards accumulators to determine if the position has existed long enough to claim its share of the rewards, or forfeit them due to not being in the position long enough.
Brief Changelog
Testing and Verifying
This PR refactors existing tests
Documentation and Release Note
Unreleased
section inCHANGELOG.md
? (yes / no)x/<module>/spec/
) / Osmosis docs repo / not documented)