Symbiont{s} | Steem DAO | Wallet Development Update 3.1

Greetings!

This is a minor complementary update to our previous update. It includes style refinements, new alerts, bug fixes, and other improvements. Following this update, we will conduct additional community testing and plan to open a pull request to the main repository before October 31, 2025. We shipped this minor update independently to decouple it from the upcoming segmented features.

List of changes

🟩 Green: Pre-existing implementations

🔵 Blue: Newly added implementations

🟥 Red: Planned or pending implementations

🟪 Purple: Community-suggested-added implementations

Routes and power down alerts

We added two new color-coded account alerts, one indicating an active power down and another showing configured withdraw routes. The wallet interface is kept clean and free from persistent or non-dismissable alerts to maintain clarity and usability.

Taking action on the routes alert now takes users directly to the routes form. If the alerts are dismissed, two key rules apply:

• The power down alert will reappear when the user changes the power down amount.

• The routes alert will reappear when configured routes are modified.

Other minor changes

• Based on community feedback, we added a toggle to the power down feature to further reinforce the importance of checking withdraw routes before initiating a power down.
• There was a bug on steemitwallet.com where users could see the withdraw routes of other accounts if they visited those profiles before using their own routes feature. This issue has now been fixed.

• On Steem, a witness is marked as disabled when the signing key is set to STM1111111111111111111111111111111114T1Anm. However, the Steemit wallet currently applies a broader rule: a witness is considered disabled either when this null key is used or when the account has not confirmed a block for more than seven days. This condition is calculated by comparing the head_block and last_confirmed_block_num, assuming an average block interval of roughly three seconds. While this logic works well for higher-ranked witnesses that produce blocks regularly, it becomes unreliable for lower-ranked witnesses who may go long periods without producing a single block due to lower scheduling priority. In some cases, a low-ranked witness might only produce one block in six months or even a year, yet remain fully functional and correctly configured. We made sure to push a small fix reflects the actual blockchain data. Some witness accounts also display the age of their last activity, while others do not. The is because the system uses a helper function to calculate and show how long a witness has been inactive, and if the inactivity exceeds 104 weeks, the time detail is omitted and only the “disabled” status is shown. Looking ahead, we may also introduce a small rework of the witness page when time allows, with the goal of improving clarity, accuracy, and the overall presentation of witness-related information.

This issue was initially reported by @kafio.

• Further improvements to the FAQ.
• Removal of some dead links in the sidebar.

^{// Human-written, AI-enhanced}

Thank you for your continued support,

The Symbionts Team,

Contact us,