fix: upgrade fuels to 0.103.0 and bakosafe to 0.6.2#517
Merged
Conversation
Aligns SDK with fuel-core 0.47.1 to fix gas price estimation causing transaction submit failures (max fee too low).
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
fuelsde0.101.3para0.103.0em api, socket-server e workerbakosafede0.6.0para0.6.2em api e socket-serverContexto
Transacoes multisig falhando com "max fee can't cover transaction cost" — gas price estimado ~1570, minimo exigido 2200. SDK calculava fees com regras do fuel-core 0.43.1 enquanto o node ja roda 0.47.1.
Test plan