Starting January 2019: Limited Participation

The Limited Participation period for Darknodes will begin in the first week of January 2019. In the first month, we will guide core community members individually through the setup process. This will ensure that there are plenty of active community members that understand the Mainnet Beta setup process — encouraging the growth of community-driven support and feedback. It will also ensure the continued stability of Mainnet Beta as Darknodes begin to be run by the community for the very first time.

As more community run Darknodes come online we will gradually reduce the number of Darknodes run by our team in order to help accommodate a greater level of community participation, while maintaining a stable level of economic incentive for Darknodes.

In the first week of January 2019, Limited Participation will begin.

Rollout Details

Due to the limited nature of viable Darknodes available during the Limited Participation period, technical support from the team will be initially provided to:

Ren Ambassadors

Members of the Telegram group for Testnet Darknode Operators

These groups have experience running testnet Darknodes and supporting the team, so we will prioritize that user base to ensure that the initial set of Darknodes are reliably operated and that valuable feedback can be obtained at an early stage.

There will be no restrictions for the deployment of a Darknode. Anyone will be able to set up a Darknode from January onward if they wish to. However, if launching a Darknode won’t be profitable it will be highly discouraged via the notification system in the Darknode Command Center.

An example notification from the Darknode Command Centre.

Darknode deployment instructions and technical assistance from the team will only be initially provided to the aforementioned groups.

Darknode Participant Guidelines

In light of limited Darknode availability, we’d encourage those that setup Darknodes to follow these guidelines such that we can maximize community participation and benefit.

Only run one (1) Darknode per participant

Setup your Darknode using the default configurations and do not disable auto updates

Assist in ongoing testing and provision of feedback for Darknode operation

Notify the team if you are terminating a Darknode

As a permissionless decentralized protocol, you are not bound by these guidelines but we’d like to reiterate that following these guidelines will greatly help the project’s progression and community involvement as we transition to an openly run network.