Skip to content

Conversation

gztensor
Copy link
Contributor

Description

  • Update u64 to u128 for liquidity storage
  • Migration to fix overflowing liquidity ticks and reserves

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Other (please describe):

Breaking Change

  • Ticks map is replaced with Ticks128, which returns a different Tick type (Tick128):
pub struct Tick128 {
    pub liquidity_net: i128,
    pub liquidity_gross: u128,
    pub fees_out_tao: I64F64,
    pub fees_out_alpha: I64F64,
}
  • CurrentLiquidity map is replaced with CurrentLiquidity128, which returns u128 instead of u64

Checklist

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have run cargo fmt and cargo clippy to ensure my code is formatted and linted correctly
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

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.

1 participant