Open
Conversation
warku123
reviewed
Nov 25, 2025
| 4. Sign and broadcast the transaction. | ||
| 1. Check Current Account Permissions | ||
| Use the getaccount command to query and review the current permission structure of the SR account. | ||
| 2. Prepare the New Witness Account. |
Contributor
There was a problem hiding this comment.
Maybe can mention about CreateAccount can create a new account.
| Use the getaccount command to query and review the current permission structure of the SR account. | ||
| 2. Prepare the New Witness Account. | ||
| 3. Stop the Current SR Node. | ||
| 4.Update Witness Permission via Smart Contract. |
Contributor
There was a problem hiding this comment.
Must ensure that MultiSign function is open.
Contributor
|
The steps for an SR to modify its account permissions are very clear and well-explained. However, it may be more appropriate to list the general steps for modifying account permissions here instead and add a note to illustrate that make sure the block-producing node stopped before modifying the account permission of SR. |
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
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.
This is an update for Procedure for Modifying Permissions
1. Permission Modification Operation Process
Use the getaccount command to query and review the current permission structure of the SR account.
4.Update Witness Permission via Smart Contract.
Using the SR's owner account, initiate the AccountPermissionUpdateContract transaction (cost: 100 TRX).
Warning!
You must stop the currently producing SR node before broadcasting the AccountPermissionUpdateContract transaction.
An SR node cannot package a transaction that modifies its own witness permission into a block. If a node attempts to produce a block containing such a transaction, the block will fail signature verification. As a penalty, the node will be disconnected from the network by other peers for 1 hour.