Node moderators
Overview
Node Moderators are a new feature in RUNEBond that allows node operators to delegate certain secondary actions on the platform to trusted external addresses. These moderators are explicitly authorized by the node operator to perform limited operations on their behalf, helping to streamline node participation while maintaining high security standards.
Motivation
One of the main friction points for node operators using RUNEBond has been the security risk of having to use their sensitive node address for all interactions, even for minor actions like replying in chat or updating listing terms. Since these node addresses are typically stored in highly secure environments, performing such tasks often required manual memo construction and direct transaction signing, limiting real-time engagement.
To overcome this, RUNEBond introduces Node Moderators—a flexible delegation system that improves usability without compromising security.
How It Works
Node Moderators are defined per node, and a single node can authorize as many moderators as needed. Each moderator is tied to a specific node and cannot act on behalf of other nodes.
Enabling a Node Moderator
To authorise a moderator, the node operator must send a transaction with the following memo:
NODE_ADDRESS: the operator’s THORChain address.MODERATOR_ADDRESS: the address being granted moderator permissions.
Disabling a Node Moderator
To revoke moderator privileges:
Permissions
Node Moderators are currently allowed to perform the following secondary actions on behalf of the node operator:
Chat Participation Moderators can send messages in RUNEBond chats on behalf of the node. These messages will appear as if sent by the node operator (with appropriate visual identification), even though they originate from a different address.
Node Listing Updates Moderators can update listing terms for the node, such as:
Bond target
Fee settings
Any other configurable listing parameters (where applicable)
⚠️ Important: Moderators do not have permission to perform sensitive or financial operations (e.g., approve bonding, unbonding, or node deletions).
Transaction Requirements
All moderator-related transactions must meet the following criteria:
Minimum amount:
0.1 RUNE
Last updated