go-algorand 3.27.0-stable Release PR #6178
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
Co-authored-by: John Jannotti <[email protected]> Co-authored-by: cce <[email protected]>
…d#6171) Co-authored-by: Gary Malouf <[email protected]> Co-authored-by: cce <[email protected]>
… and cert from response (algorand#6163)
gmalouf
approved these changes
Nov 25, 2024
algorandskiy
approved these changes
Nov 25, 2024
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.
Overview
This release provides performance improvements and network stability, as well as includes other enhancements and upgrades. Note that the AVM changes while present in the codebase, are in fact 'consensus-gated'; they will be available upon the next consensus upgrade.
Important Note: For performance reasons, we no longer report extra details for failed app transactions by default. This was useful if you were debugging a smart contract, but also had a significant processing performance impact. This behavior is still available if you use the developer API by setting
EnableDeveloperAPI: true.What's New
Changelog
Enhancements
/v2/block/{round}/headeromits transactions and cert from response (#6163)Bugfixes
Protocol Upgrade
This release does not contain a protocol upgrade.
Additional Resources