Discussion Focus
- Do you support removing the product entrypoints and pages related to rBNB, rSOL, and rMON from the StaFi rToken App website?
- Do you agree to use May 11, 2026 as the current proposed target date for the rToken App shutdown, while reserving a one-month transition window before the shutdown so users can complete redeem / unstake and other necessary actions?
Background
Over the past period, StaFi has been continuously advancing new priorities across both product and ecosystem development.
On one hand, we have become increasingly clear that our long-term focus should be on LSaaS and AI, with the goal of building around a clearer infrastructure positioning and supporting StaFi’s future product integration, resource allocation, and ecosystem expansion. On the other hand, the actual activity and usage of some legacy rToken products have declined significantly. Continuing to maintain full entrypoints, pages, and documentation for these products on the StaFi rToken App website would not only disperse maintenance resources, but could also create confusion for new users about StaFi’s current core direction.
In the current market environment, the overall competitive landscape in crypto is changing significantly, and products need to become more focused and efficient in allocating resources toward directions with real long-term growth potential. For StaFi, this means gradually moving from a previously more fragmented product structure toward a clearer LSaaS + AI direction.
At the same time, the StaFi appchain (such as StaFi Chain) has already been removed, and FIS has already migrated to Ethereum. This also marks an important milestone in StaFi’s effort to adapt to the next stage of development and gradually complete the adjustment of its infrastructure and product structure.
Based on the above considerations, we are opening this discussion to communicate with the community in advance regarding the proposed removal and consolidation of certain rToken product entrypoints on the StaFi rToken App website.
Why This Discussion
The core purpose of this discussion is not simply to remove a few pages, but to complete a clearer product consolidation:
- Further focus StaFi’s core direction: concentrate resources on LSaaS- and AI-related development.
- Reduce the ongoing maintenance cost of low-activity products: including frontend entrypoints, explanatory documentation, operational communication, and future compatibility costs.
- Reduce product-level information noise: so users can more clearly understand what StaFi is truly prioritizing for the long term.
- Prepare for future architecture and brand expression: unify external messaging and reduce the cognitive burden caused by a more fragmented historical product structure.
Proposed Scope
According to the current internal discussion, the proposed adjustment mainly involves the unified consolidation of certain rToken product entrypoints, pages, and related explanations on the StaFi rToken App website.
The products currently proposed to be included in this removal plan are:
- rBNB
- rSOL
- rMON
Different from rBNB, rSOL, and rMON, notifications and follow-up arrangements related to hHYPE would be more appropriately handled by the Hito side. As for sSONIC, its entrypoints and follow-up arrangements are expected to be communicated and handled by the Chaos side. Therefore, the focus of this discussion remains on the removal and consolidation of entrypoints and pages related to rBNB, rSOL, and rMON on the StaFi rToken App website.
Proposed Arrangement
If this discussion receives basic community support, we suggest proceeding in the following way: first publish the Discussion to explain the background and scope → reserve a transition window → gradually move forward with removing the relevant entrypoints from the StaFi rToken App website.
The purpose of this arrangement is to leave enough time for existing users to take necessary actions, while also allowing the pages, documentation, and product structure on the StaFi rToken App website to be consolidated in a smoother way. Overall, we would prioritize clarifying the removal scope, supplementing necessary guidance, and then gradually removing relevant website entrypoints and outdated content after the transition period.
1. Scope of Removal
If the direction outlined in this discussion receives community support, StaFi would gradually remove related content from the StaFi rToken App website, including but not limited to:
- frontend product entrypoints for the relevant rTokens
- related product pages and redirect entrypoints
- outdated explanations in the relevant docs
- guidance content that will no longer be maintained on the StaFi rToken App website
Among them, if the direction of this discussion receives community support, the rToken App is tentatively proposed to be taken offline on May 11, 2026. At that time, the entrypoints and pages on the StaFi rToken App website that fall within the scope of this discussion are also expected to enter removal or maintenance sunset status accordingly.
2. User Action Window
We are inclined to reserve an approximately one-month transition period after this discussion is published, allowing users to complete the necessary actions, while taking May 11, 2026 as the current proposed shutdown date for the rToken App.
The reason for this arrangement is that the unstake period for the related products is generally within 10 days, so from an operational perspective, around one month should usually provide a relatively sufficient processing window. During this period, if users still hold related positions, we recommend completing redeem / unstake and other related actions in advance according to the existing process.
Relevant operation guides are as follows: rBNB, rSOL, rMON.
3. Entrypoint Ownership After Removal
The main focus of this proposed adjustment is the removal of the relevant frontend entrypoints and pages maintained by the StaFi team on the StaFi rToken App website, and it should not be simply understood as meaning that all related functions will disappear at the same time.
As long as the relevant contracts remain in place, third parties may still, in principle, provide frontend access based on those contracts.
However, as the removal plan moves forward, the related contract functions will also enter the predefined sunset logic. At that stage, stake will no longer be available, and the implementation of unstake / redeem will also differ from the current version. Therefore, even if third-party access continues to exist in the future, it would be closer to supporting the remaining redemption flow, rather than maintaining the current full product form.
Conclusion
The goal of this discussion is to gradually complete the consolidation and cleanup of certain legacy rToken product entrypoints on the StaFi rToken App website, without affecting the basic processing window needed by users.
We believe this would help:
- make StaFi’s product structure clearer
- make resource allocation more focused and efficient
- help the community and external users better understand the direction StaFi is truly prioritizing at the current stage
If the community generally agrees with the overall direction of this discussion, we will further refine the execution timing and specific operational instructions based on feedback, and provide a clearer follow-up notice afterward.
We welcome everyone to continue sharing feedback and suggestions under this post.