Create non-disruptive_fee_updates.md #371
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
AfeworkShalom09
approved these changes
Nov 24, 2024
AfeworkShalom09
approved these changes
Nov 24, 2024
|
From discussion with SpyCheese: Limited depth of chains for "fixed fees" is bad, because malicious actor may prepare chain in such a way that 1024 depth will be reached in the middle of 3rd-party protocol (DEX for instance) causing disruption of this protocol. |
|
|
||
| - **Chain Depth Limit**: What should the chain depth limit be for applying old fees? | ||
|
|
||
| - **Fee Decrease Scenario**: In the case of a fee decrease, do we want to keep the old (higher) fees for running chains? |
There was a problem hiding this comment.
Hopefully contracts do not mind that they get extra TON relative to what they expected. Given that there are no guides to nanoTON-precise fee management, this is a safe assumption.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
No description provided.