program: Expand comment on SetAuthority instruction#54
Merged
Conversation
lorisleiva
approved these changes
May 11, 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
2 participants
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.
Problem
The
SetAuthorityinstruction allows changing the authority on buffer accounts even if a buffer account has a non-canonical derivation. This might look unusual, since the new authority will not be able to initialize the metadata account. The rationale is that it might be useful to allow this in order to simplify the process of writing data, but always require the program upgrade authority (canonical) or the authority in the address derivation (non-canonical) to initialize the metadata account.Solution
Clarify this aspect on the documentation of the
SetAuthorityinstruction.