Merge protocol-next (P26) back to main - #5930
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR merges Protocol 26 (“protocol-next”) updates back into main, primarily updating XDR definitions and their generated Go bindings to reflect new ledger/key-freezing related semantics and updated result codes.
Changes:
- Update Stellar XDRs and regenerated Go bindings (new result codes; new config settings/types around frozen ledger keys and freeze bypass txs).
- Bump tracked XDR commit/hash metadata used by generation (
Makefile,xdr_commit_generated.txt,XdrFilesSHA256). - Adjust default Soroban resource instructions used by
txnbuild.NewPaymentToContract.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
xdr/xdr_generated.go |
Regenerated XDR Go bindings: adds new result codes and new config-setting-related types/unions for frozen keys + bypass txs. |
xdr/xdr_commit_generated.txt |
Updates the recorded XDR commit hash corresponding to regenerated artifacts. |
xdr/Stellar-transaction.x |
Updates transaction-related XDR enums/unions to include new *_TRUSTLINE_FROZEN and txFROZEN_KEY_ACCESSED codes. |
xdr/Stellar-contract-config-setting.x |
Adds EncodedLedgerKey and new config-setting structs/IDs for frozen keys and freeze-bypass tx sets/deltas. |
txnbuild/invoke_host_function.go |
Increases the default Soroban instruction budget used for “payment to contract” operations. |
Makefile |
Updates XDR_COMMIT to match the new generated XDR state. |
gxdr/xdr_generated.go |
Regenerated gxdr bindings reflecting new result codes and config-setting additions. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Shaptic
approved these changes
Apr 1, 2026
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
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.
PR Checklist
PR Structure
otherwise).
services/friendbot, orallordocif the changes are broad or impact manypackages.
Thoroughness
.mdfiles, etc... affected by this change). Take a look in the
docsfolder for a given service,like this one.
Release planning
CHANGELOG.mdwithin the component folder structure. For example, if I changed horizon, then I updated (services/horizon/CHANGELOG.md. I add a new line item describing the change and reference to this PR. If I don't update a CHANGELOG, I acknowledge this PR's change may not be mentioned in future release notes.semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.
What
Merge protocol-next (P26) back to main