Symbiont{s} | Steem DAO | Wallet Development Update #3

Greetings!

This is our second update related to the wallet upgrade proposal. The first update can be found here, and the second one here.

We continue to work diligently on the wallet, implementing the necessary changes guided by the previously announced objectives as well as feedback from the community. Recently, there was a disruption in funding and some interference with our work, which required us to revisit certain parts of the codebase to ensure full compliance with established development standards and project style conventions. This third wallet update addresses style adjustments and introduces several community-requested improvements.

List of changes

🟩 Green: Pre-existing implementations

🔵 Blue: Newly added implementations

🟥 Red: Planned or pending implementations

🟪 Purple: Community-suggested-added implementations

Withdraw route rework

As added to the FAQ

A withdraw route on Steem is simply an instruction on your Steem account that tells the blockchain where your weekly power down payouts should go. When Steem Power (SP) is powered down, the withdrawn amount is divided according to the configured routes, if they exist, and each destination may receive either liquid STEEM or additional SP via automatic power up. Users can also remove routes at any time, regardless of whether the power down process is in progress.

The number of permissible routes is defined by the blockchain. The account holder can allocate up to a total of 100% across all routes. If the configured routes sum to 100%, the entire payout is redirected to designated recipients; if the sum is below 100%, the remaining percentage normally returns to the owner’s account as STEEM, unless specified otherwise.

Although this feature could be confusing for general users, we have taken care to make it as intuitive as possible. To achieve this, we introduced several indicators that explain both the available actions and their constraints.

On the Steem blockchain, the parameter STEEM_MAX_WITHDRAW_ROUTES defines the maximum number of withdrawal routes a user can create, currently limited to 10. Additionally, the total distribution cannot exceed 100%, even if fewer than 10 routes are in place.

Case 2 occurs when a user attempts to allocate a percentage higher than what remains available:

Case 3 is triggered when all 10 routes have already been defined:

Case 4 occurs when the total distribution has already reached 100%:

When configuring a route, users can choose whether the payout is sent as STEEM or powered up as Steem Power (SP). This option can be toggled in the same way as for standard transfers:

Key point:

• The goal was to ensure the form fully respects the established style conventions.
• Proper indicators were added to support quick and informed decision-making.
• Relevant information has been incorporated into the FAQ.
• Baselines for indicators were established for consistent use in other parts of the wallet.

Another important aspect to highlight is the expectation that users may not always be aware of what is happening in the background. To address this, the next step was to add clear indicators to ensure that when a user initiates a power down or already has one in progress, it is immediately clear that withdrawal routes are set. This brings us to our next additions.

Expanded power down indication

If a user has already defined withdrawal routes, the following table will be displayed when opening the power down form:

This table serves as a clear visual indicator that multiple accounts are configured as routes. As the user increases the power down amount, the corresponding values in the table update in real time. This dynamic feedback improves transparency and provides immediate confirmation of how funds will be distributed.

In addition, we introduced an alternative way to review existing routes directly from the power down indication area:

When the user clicks this option, a detailed table of all configured routes is displayed:

A general alert related to routes and power down is work in progress.

Better exposure for witnesses and proposals

We received feedback from the community that many users were having difficulty locating the Witness and Proposal pages, despite both being pivotal governance mechanisms for all Steem users. To address this, we have repositioned these pages so they are immediately visible and accessible, placing them directly under the user’s navigation. In addition, we introduced a few adjustments to improve usability and ensure that governance features remain a central part of the wallet experience.

Users can now review other accounts’ witness and proposal votes directly from within the wallet. To minimize confusion, we applied a neutral gray color scheme and disabled hover/click interactions when the user is either not logged in or viewing a witness page that does not belong to their own account.

To reduce confusion, users will not be able to vote on other people’s pages. However, work is still in progress to establish a clear visual pattern using color indicators so that users can immediately recognize when they are viewing another user’s page. In addition to further testing.

Improved FAQ section

The FAQ has been updated to resolve most of the significant issues related to data relevance, and additional up-to-date information has been incorporated. While the work is not yet complete, these improvements ensure that users have access to more accurate and current references. Further refinements will continue as part of our ongoing effort to maintain a reliable and comprehensive FAQ.

More history details

There were several occasions where users needed to obtain the transaction ID of a transfer to resolve issues with an exchange or with transfers made without a memo. Users can now access the transaction ID directly from the wallet. Each transaction ID is also linked to the current official block explorer used by major exchanges such as Binance, making it easier to verify and share transaction details when needed.

However, we are also considering a longer-term solution that would allow users to access transaction history going back several months without placing excessive load on the API. This improvement would not only help users meet tax-related requirements but also provide an overall better experience for everyone by making historical data more accessible and reliable.

Minor Bug fixes

We identified an issue where the transfer form appeared to be correctly filled out, but transfers would fail if there was a white space before or after the account name. While this issue has existed for some time, we implemented a minor change that automatically trims any leading or trailing white spaces across all forms. This ensures that transfers and other form submissions are processed correctly without requiring manual input adjustments from the user.

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

Thank you for your continued support,

The Symbionts Team,

Contact us,