This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
Use authorization of bidder for bidrefund deferred transaction - v1.9.x #383
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
When someone outbids an existing account name, the system contract generates a deferred transaction containing the
eosio::bidrefundaction to return the funds of the account that was outbid. Prior to this PR, this action was authorized by theactivepermission of theeosioaccount which meant the CPU/NET costs of the entire deferred transaction was billed to theeosioaccount. This PR changes the authorizer of theeosio::bidrefundaction to theactivepermission of the account that was outbid.Deployment Changes
API Changes
Documentation Additions