feat: robust stacks transaction fee estimation #368
Merged
Conversation
This file contains 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
jferrant
approved these changes
Jul 30, 2024
jferrant
reviewed
Jul 30, 2024
Base automatically changed from
233-support-estimating-contract-calls-fees
to
main
July 30, 2024 20:32
…as a parameter and be robust to wonky fee prices by capping the tx fee.
djordon
force-pushed
the
366-robust-stacks-transaction-fee-estimation
branch
from
62a8cce to
0aba7ba
Compare
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Closes #366. And is a follow-up to #361.
Changes
Testing information
The existing tests we updated to support the new functionality.