Document check_auth CAP-85 impact - #2861
Draft
leighmcculloch wants to merge 1 commit into
Draft
leighmcculloch wants to merge 1 commit into
leighmcculloch wants to merge 1 commit into
Conversation
Contributor
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.
What
Add a callout to the check_auth guide and the Complex Account example noting that Protocol 28 introduces a new
ContractExecutable::ExternalRefvariant in contract-creation auth contexts.Why
rs-soroban-sdk#2057 documents that custom accounts implementing
__check_authnow see this new variant when authorizing contract deployments, and accounts built with an SDK version that predates it will panic if they exhaustively matchContractExecutablewithout a matching arm.