RPC client create_validator uses the configuration as input
#3226
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
sisou
approved these changes
Jan 7, 2025
sisou
changed the title
create_validator uses the client configuration as inputcreate_validator uses the configuration as input
Eligioo
approved these changes
Jan 8, 2025
jsdanielh
approved these changes
Jan 8, 2025
jsdanielh
force-pushed
the
iicruz/rpc-restrict-create-validator-tx
branch
from
4feeaeb to
7869b71
Compare
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.
What's in this pull request?
The RPC client's operations for the validator were designed to be applied to the local validator. The create validator was the exception. This PR standardizes it.
To submit txs regarding other validators one can use the send raw transaction.
This fixes #3225.
Pull request checklist
clippyandrustfmtwarnings.