This is the first edition of our weekly recap of the most interesting and spirited discussions on the Story Protocol Discord.
Node Operation and Troubleshooting
Validators frequently sought assistance on setting up, configuring, and managing their nodes. Issues such as node synchronization, incorrect file paths, restarting services, and updating binaries were common topics.
Validator Creation and Staking
Participants discussed the process of creating validators, the required amount of tokens, and how to stake or add more tokens to their validators. Additionally, there was a focus on minimum IP requirements and how to obtain them.
Software Upgrades and Maintenance
Several validators raised questions about software upgrades, such as updating geth binaries to the required version. The community exchanged guidance on commands for stopping, upgrading, and restarting services.
Validator Restoration and Backup
There was significant discussion about restoring validator nodes, specifically concerning the importance of the priv_validator_key.json
file. Validators shared their concerns about loss of keys and the potential impact.
Node Synchronization and Hardware Requirements
Validators discussed issues related to node synchronization, suitable hardware for running a validator, and storage requirements. Many validators struggled with slow synchronization and sought advice on server specifications to speed up the process.
Validator Setup and Recovery
Validators discussed the process of setting up nodes, restoring previous validators, and the importance of backing up the priv_validator_key.json
file. Questions about how to handle missed backups and the risks involved were common topics.Link
Staking and IP Requirements
Many validators asked about the staking process, required IP amounts, and how to increase their stake. The discussions included information on the minimum amount needed to join the active validator set and the difficulties of acquiring sufficient IP.
Snapshots and Node Updates
Validators often faced challenges with downloading snapshots, updating nodes to the latest versions, and addressing errors related to outdated or corrupted files.Link
Urgent Action for Node Operators: All node operators must upgrade to v0.9.3 before block height 1,069,000 to stay compatible with the Iliad network. Failure to do so will result in node incompatibility and could halt the consensus client, requiring a fresh instance to reconnect.
Track the Upgrade: Use this link to monitor the countdown to the upgrade.
Instructions: Follow the official guide for detailed upgrade steps.
Download: Get the v0.9.3 binaries here.
Immediate Action
All operators should also upgrade to v0.10.1 to fix a critical unstaking bug, which previously caused system panic during unbonding when the delegator's balance decreased (e.g., due to slashing). This update ensures only the remaining balance is unbonded.
Upgrade Now: Replace the current binaries with v0.10.1 and restart the Story client.
Download: Get the update here.