This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Implement FIX_LINKAUTH_RESTRICTION protocol feature #7025
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Change Description
Resolves #6672.
This PR adds support for the
FIX_LINKAUTH_RESTRICTIONprotocol feature which removes the restriction oneosio::linkauthfor non-native actions named one of the five special action names:updateauth,deleteauth,linkauth,unlinkauth, orcanceldelay. The restriction still remains for these special actions names on the contract deployed on theeosioaccount.Consensus Changes
Makes the
FIX_LINKAUTH_RESTRICTIONprotocol feature available. See above description and #6672 for details.API Changes
Documentation Additions