The RSS3 Network Mainnet has officially transitioned to its Production stage since Epoch 228, marking a significant milestone in our journey.

This update brings important changes and exciting opportunities for all network participants

Here’s what you need to know:

An Epoch in Production Mainnet

First, let's take a look at a particular Epoch on the RSS3 Mainnet after Production:

For Node Operators

Mandatory Upgrade

Node Operators must upgrade their Nodes to rss3/node:v1.0.0. This upgrade is mandatory for continued participation and rewards. A detailed guide on the upgrade process is available here:  https://docs.rss3.io/guide/operator/deployment/guide

• Grace Period: Operators have 28 Epochs to begin the upgrade. Starting from Epoch 256, Nodes that have not begun the upgrade process to the Production stage will no longer receive rewards of any kind.
• Irreversible Process: Once the upgrade begins, it cannot be stopped or reverted. Ensuring a stable network connection for your Node is critical, as it will be essential for its operation throughout its lifespan.

explorer.rss3.io provides a comprehensive step-by-step guide for the upgrade and configuration of an RSS3 Node. If you encounter any issues or have questions, join our community on Discord: https://link.rss3.io/discord.

1-click Deployment of Light Node

To expand the RSS3 Network and make Node operations more accessible, we’ve simplified the deployment process.

RSS3 Node can now be deployed as a light node:

• Operators can now deploy an RSS3 Node as a light node, which supports 1-click deployment to serverless environments such as Railway and Zeabur (not affiliated nor endorsed). This has been made possible through the Community’s effort.
• Light nodes require fewer resources by covering fewer open data protocols. While they may receive fewer requests and Operation Rewards, they are a great option for operators looking to contribute with minimal infrastructure.
• For advanced/hardcore Operators, you may continue to customize your Node’s functionality and coverage to maximize your Operation Rewards.

You can learn more here:

https://docs.rss3.io/guide/operator/deployment/light-mode

https://docs.rss3.io/guide/operator/deployment/serverless

Node Initialization

After deploying a production Node, it will undergo an initialization process, during which it will not be ready to serve requests. The duration of this process varies based on Node coverage and can take anywhere from a few hours to several days. During this period, Nodes will still receive Staking Rewards but will not be eligible for Operation Rewards.

Deferred Slashing Implementation

The slashing mechanism is not yet finalized, as outlined in REP-38 https://github.com/RSS3-Network/REPs/blob/main/REPs/REP-38.md. It will not be enforced during this stage. A separate announcement will be made before its implementation, and we encourage all participants to engage in the ongoing discussion on our forum.

For Delegators

Existing Chips

Current Chips will continue to receive Staking Rewards as usual. Multiple Chips can be optionally merged into a single Chip, as per REP-26.

New Chips

Delegators can continue to stake or entrust RSS3 tokens to any Nodes, receiving one Chip per transaction, in line with REP-26.

Chips Redemption

Delegators will have the opportunity to redeem their Chips right away. The redemption process involves 2 stages:

1. Begin redemption: This initiates a safety confirmation period of 30 Epochs, during which your Chips will not receive Staking Rewards. This step is irreversible.
2. Claim redemption: After the confirmation period, you can claim redemption, which will burn your Chips, and you will receive the underlying RSS3 tokens.

For Developers

We have sunset all previous RSS3 Network Data Sublayer(DSL). The DSL is now fully decentralized and backed by RSS3 Nodes operated by a diverse set of participants, including Google. These Nodes have been operational since the announcement of the Beta Stage, ensuring the provision of Public Goods to the Network.

While the DSL remains free at the moment, there is an ongoing discussion regarding future billing for usage, as outlined in REP-43. We encourage all participants to share their thoughts and engage in the discussion on our forum.

Conclusion

We are excited about this new chapter for the RSS3 Network and look forward to continued growth and innovation with our Community. Stay engaged, stay informed, and stay OPEN!