Story Node Urgent Upgrade (EP8)

Hello everyone! This will be a quick but crucial update for all Story node operators. As of September 30, 2024, an issue has been identified with the story client that requires immediate attention. To ensure your node continues to operate smoothly, it is essential to upgrade your node as soon as possible.

Replace the Binary

All you need to do is to replace the story v0.10.1 binary file in the correct folder to resolve the issue.

If you followed my guide in the previous articles, you can find the structure of the binary folder as shown in the picture above.

Simply navigate to that location and replace the binary. Oh, and don’t forget to stop the node first. Let’s see how it works.

#naviage 
cd $HOME 
 
#get new binary 
wget https://story-geth-binaries.s3.us-west-1.amazonaws.com/story-public/story-linux-amd64-0.10.1-57567e5.tar.gz 
 
#extract files 
tar -xzvf story-linux-amd64-0.10.1-57567e5.tar.gz 
 
#stop service 
sudo systemctl stop story-consensus 
 
#replace the binary file 
cp $HOME/story-linux-amd64-0.10.1-57567e5/story $HOME/story_binary/story_client 
 
#reload daemon & restart service 
sudo systemctl daemon-reload 
sudo systemctl start story-consensus 
#see log 
sudo journalctl -u story-consensus.service -f

What really happen?

Let’s create a sample scenario for our discussion. Suppose a validator wants to unstake 1,000 tokens. These tokens are locked during the unbonding period of 1 hour (3600 seconds). During this period, an event, such as slashing or another penalty, reduces the validator’s tokens by 20, leaving only 980 tokens available.

The Problem: At the end of the unbonding period (after 1 hour), the network attempts to release the original 1000 tokens. However, since the validator’s available balance is now 980 tokens (due to the 20-token decrease), the system encounters an error — essentially, it tries to release more tokens than are actually available (1000 vs. 980). This could trigger a “system panic” or other network error because the balance no longer matches the original unstaking request.

The Fix: The fix ensures that, after the unbonding period, the system only releases the tokens that are still available. In this case, instead of attempting to release 1000 tokens and causing an error, the system checks the validator’s available balance and releases the correct amount of 980 tokens. This prevents the network from encountering errors due to mismatched balances.

Summary:

• Before the fix: Network tries to release 1000 tokens after unbonding, but only 980 are available, causing an error.
• After the fix: Network checks the available balance (980 tokens) and releases that amount, avoiding errors.

That’ s all for today. Thank you for reading.