Show actual band range in dashboard, document tick spacing limits#62
Merged
Conversation
Add RESET_BANDS env variable that triggers emergency withdrawal of all existing bands on startup, then lets the bot re-mint with the current config. Band close events are recorded so historical bands remain visible in the chart. Change DEV range from 3% to 1%.
Dashboard now calculates actual range from band ticks instead of showing config values. Document minimum band width constraint per fee tier, env-specific pool configs, data persistence, band reset, and all health/dashboard endpoints in README.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Test plan