Staking Mechanics

The staking system is one of the last components being tuned before Relix moves beyond testnet. This page will be updated with full technical details once the final parameters are locked in and the on-chain modules are ready for long-term use.

For now, you can think of staking on Relix as a structured process with a few clear steps:

  1. Choose a validator or operate your own

  2. Bond RLX as stake (self-stake or delegation)

  3. Accrue rewards while the stake is active and the validator performs correctly

  4. Unbond and wait through a defined exit period

  5. Withdraw stake and rewards once the unbonding delay has passed

The exact numbers and rules behind each of these stages are what this section will formalize.


What this section will define

When complete, the Staking Mechanics page will cover, in precise terms:

1. Validator set and epochs

  • How the active validator set is chosen (by stake weight, limits per set, rotation rules).

  • How time is divided into epochs or other accounting periods used for:

    • Reward calculation

    • Updating stake snapshots

    • Applying slashing or other penalties

2. Minimums, caps, and stake granularity

  • Minimum stake required to:

    • Run a validator

    • Delegate to an existing validator (if delegation is live)

  • Any maximum stake per validator or recommended bounds to avoid over-concentration.

  • The smallest unit in which stake can be moved or delegated, aligned with RLX decimals.

3. Reward calculation model

  • How protocol-level rewards are computed for each period:

    • Inputs such as total staked RLX, target participation, and network parameters.

    • Whether rewards follow a fixed schedule, curve, or pool-based design.

  • How rewards are split between:

    • Validator operators (commission or base cut).

    • Delegators, proportional to their share of stake.

  • Whether rewards are:

    • Auto-compounded into stake, or

    • Accrued separately and claimed via transaction.

4. Unbonding and withdrawal

  • The unbonding period: how long RLX remains locked after a user initiates an unstake or undelegation.

  • Rules for:

    • Partial vs full unbonding.

    • Cancelling an unbonding request before it completes (if allowed).

    • Handling rewards during the unbonding window (continue to accrue or not).

5. Slashing and penalties

  • Conditions that can lead to penalties, such as:

    • Extended downtime or missed participation.

    • Double-signing or equivocation.

    • Other consensus-level violations.

  • The size and type of penalties:

    • Reduced rewards for mild issues.

    • Actual stake slashing for severe misbehavior.

  • How slashed amounts are handled (burned, redistributed, or allocated to specific pools).

6. Delegation logic (if enabled)

  • How RLX holders can delegate stake to validators:

    • One validator vs multiple validators per delegator.

    • Minimum delegation amount and any limits.

  • How commissions are set and changed by validators:

    • Initial commission rate.

    • Rules or notice periods for changing rates.

  • How delegators can:

    • Move stake from one validator to another.

    • Monitor their share of rewards and effective APR.

7. Operational details for validators

  • How validators:

    • Register and update metadata (name, website, contact).

    • Set or update commission rates within allowed bounds.

    • Safely rotate keys or migrate infrastructure without losing stake.

  • Recommended operational practices to:

    • Minimize downtime.

    • Avoid accidental double-signing.

    • Handle upgrades without dropping out of the active set.


Testnet behavior vs mainnet guarantees

On Relix Testnet, staking parameters may be adjusted several times as:

  • New versions of the node software are rolled out.

  • Reward curves and penalty models are tested.

  • Feedback from validator operators and delegators is incorporated.

Important points until this page is finalized:

  • Testnet RLX and testnet staking are experimental. Values, rates, and even entire flows can change as we iterate.

  • Mainnet will have a frozen specification. Before mainnet launch, this section will be updated with:

    • Finalized parameters.

    • Links to staking contracts or modules.

    • Clear diagrams and examples of reward and penalty scenarios.


How to prepare in the meantime

While the detailed mechanics are being finalized, potential validators and delegators can:

  • Learn and practice the operational side:

    • Running full nodes and validators on testnet.

    • Setting up monitoring, alerting, and backup strategies.

  • Familiarize themselves with the Staking & Rewards high-level model.

  • Follow the official channels for announcements about:

    • Testnet staking changes.

    • Public validator onboarding waves.

    • Mainnet economic and governance proposals.

Once the staking specification is locked, this page will become the primary technical reference for how RLX moves through the staking system and how your operational choices translate into rewards, risk, and long-term participation in securing Relix.

Last updated