Update gas and gas-prices Parameters in CLI Commands #44
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
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.
This PR modifies CLI commands in the documentation to reflect updated gas and gas-prices values for better performance and compliance with network requirements.
Updated gas value from "200000" to "300000" across all applicable commands.
Added gas-prices parameter with a value of "7.0route" to ensure transactions are prioritized correctly.
Applied the changes uniformly to all relevant commands in the sections:
The previous values for gas and the absence of gas-prices were causing inefficiencies in transaction processing and potential rejections under certain network conditions. These changes optimize transaction execution and align with the network's updated guidelines.
All updated commands have been tested in a local environment to ensure proper functionality and compatibility.
No breaking changes were introduced.
Let me know if further refinements are needed! 😊