docs: warn that profitMargin overrides don't retroactively update built fee configs - #96
Open
munikes wants to merge 1 commit into
Open
Conversation
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.
profit defaults to configDefaults.transactionFees.profitMargin, but that default parameter is resolved at call time, not read live afterwards. Default network fee configs are built once at module load time in config-networks.ts using whatever profitMargin holds at that point. Overriding profitMargin later in MY-CONFIG.ts silently does nothing to fee configs already built for a network — you have to call setFeesForNetworkEVM(chain, feeConfigL1(ratio)) again after the override for it to take effect. Added an explicit comment next to feeConfigL1 warning about this.