RLS (RLS) Price

RLS is the native staking and rewards token of the Rayls ecosystem, not the gas token for everyday transactions on Rayls Public Chain. Public-chain users pay gas in USDr; validators stake RLS and receive RLS rewards. RLS exists on Rayls Public Chain and in a representation bridged to Ethereum through LayerZero. Therefore, RLS held directly or represented cross-chain should be distinguished from USDr, which is used on the public chain to pay dollar-denominated gas: they are connected in fee settlement, but serve different functions.

Rayls Public Chain has users pay gas for each transaction in USDr so fees are denominated in dollars; RLS is used for staking, validator rewards, and the burn process after fee settlement. USDr is pegged to $1 and collateralized by USDC.e locked in an on-chain custody contract; USDC.e in turn corresponds to USDC locked on Ethereum through LayerZero. To obtain USDr, a user can bridge USDC from Ethereum: USDC is first locked on Ethereum, and Rayls Public Chain mints corresponding USDC.e; USDC.e is then locked in a 1:1 custody contract, which mints an equal amount of USDr to the user. The bridge normally completes both steps automatically. On exit, USDr cannot be bridged directly back to Ethereum: it must first be converted back to USDC.e, and USDC.e is then bridged back. USDr circulation is therefore confined to Rayls Public Chain.

Public-chain fees are first paid by users in USDr and only then converted into RLS rewards and burns; USDr is not paid directly to validators. The Fees Aggregator continuously collects the USDr fees from each transaction, and validators trigger distribution at the end of each 24-hour epoch. The aggregator swaps USDr accumulated during that epoch for RLS in the on-chain RLS/USDr automated market-maker pool at the market rate at that time. The resulting RLS is split equally: 50% goes to the validator pool's Rewards Distributor for payment to validators under the rules; the other 50% is bridged to Ethereum through LayerZero, first accumulated at the designated burn address, then burned in batches every few months. Accordingly, fee volume, the pool price at swap time, and actual on-chain activity all affect how much RLS is swapped in a given epoch; 50/50 is a distribution ratio, not a fixed amount of RLS paid by users.

RLS is used so validators' security costs and income are denominated in the same asset. Validators must stake RLS and participate in batch proposals, head voting, and commitment anchoring in Axyl consensus; in return, they collectively receive 50% of the RLS swapped in each 24-hour epoch. The officially described initial validator set consists of vetted, identity-verified permissioned institutions, rather than allowing anyone to run a validator unconditionally. Staking is not only about rewards: the protocol has a slashing mechanism to constrain dishonest behavior. Becoming a validator therefore requires more than holding RLS; it also requires admission to that permissioned set and compliance with network rules. RLS staking links the economic constraints of consensus participation to the reward source generated by public-chain fees, but reward levels are not determined solely by a fixed annual yield.

Yes. Holders can delegate RLS to a permissioned validator to participate in staking without running validator infrastructure themselves; this differs from becoming a validator. A delegator does not gain a validator seat as a result: the validator remains responsible for consensus work and subject to network rules and slashing. Delegation returns are funded by the share of RLS rewards produced by swapping public-chain fees in each epoch, not by additional issuance. Actual outcomes vary with on-chain fees, the USDr-to-RLS swap result, validator performance, and applicable delegation and distribution rules; if a validator fails to meet protocol requirements, mechanisms such as slashing also mean delegation should not be understood as a fixed return.

RLS has a maximum supply of 10 billion tokens, described officially as fixed supply. Of the RLS obtained by swapping public-chain fees, 50% enters the burn process, so burning permanently removes the corresponding amount from circulation. A fixed maximum supply does not mean all tokens circulate at the same time, nor does it mean burns or usage produce a certain price outcome. The official initial allocation is 50% to community and ecosystem, 22% to initial investors, 17% to initial contributors, and 11% to technology providers; the latter three categories each have a four-year vesting period. Public-chain genesis also has a balancing design: an equal amount of RLS is burned alongside RLS allocated to validators as genesis stake, so genesis staking and pool-liquidity deployment themselves do not cause a net supply impact. Subsequent public-chain burns depend on fees actually collected and swapped.

On Rayls Sovereign chains or private networks, usage fees are calculated by usage and must be settled in RLS with the Rayls Foundation. This differs from the public-chain path, where users first pay gas in USDr and the protocol then swaps it for RLS. If an institution does not yet directly hold crypto assets, the official description provides for a broker to collect off-chain fiat and purchase RLS on its behalf to pay fees, but this method carries a premium. Proof of Usage (PoU) records the transaction-fee value of private institutional networks on Rayls Public Chain, allowing outsiders to observe the value of private-side usage without requiring the private transactions themselves to be disclosed. It addresses verifiability of private activity; a PoU record and private-fee settlement are not themselves equivalent to each public-chain gas payment, and they do not establish that any institution's transaction volume or RLS purchases must grow.

RLS governance is currently handled by the Rayls Foundation. The official description presents a future migration to the Rayls Governance DAO as a plan, not as a governance transition that has already been completed. DAO governance rights whose specific timing and rules have not yet been announced should therefore not be treated as rights current holders can already exercise directly. This transitional arrangement relates to token utility: the current design already uses RLS for validator staking, private-chain fees, and network incentives, but the eligibility, voting method, implementation date, and specific powers for governance migration remain subject to the formal rules in effect at that time.