Rayls validator economics explainer

Clarifying Rayls Validator Economics and Fee Flows

Some thoughtful questions were recently raised by members of the community regarding Rayls validator incentives, fee flows, and the structure of the network. We welcome this kind of scrutiny, and healthy discussion around tokenomics is exactly what a serious ecosystem should have.

So, here is a clarification of how the system works today and how the documentation should be interpreted.

TL;DR

The simplest way to understand Rayls tokenomics is this:

The more Rayls Private Chain clients and the more Public Chain transactions, the more demand for RLS there will be.

Activity across the Rayls ecosystem ultimately feeds into the RLS token economy. Those fees are then used to either reduce supply (via burns) or reward the participants securing and supporting the network.

For anyone who wants to go deeper, the following documents are the official and most up-to-date sources of information on Rayls tokenomics and network mechanics:

• Rayls Litepaper: https://www.rayls.com/litepaper
• MICAR-Compliant Whitepaper: https://www.rayls.com/micar-whitepaper
• Buybacks Blog Post: https://www.rayls.com/blog/rayls-tokenomics-automated-buybacks-burn-and-the-rayls-reserve
• Tokenomics Blog Post: https://www.rayls.com/blog/rayls-tokenomics-a-united-tradfi-defi-economy

If older graphics, posts, or community discussions appear to contradict these documents, the content in these links should be considered the current canonical reference.

How Fees Enter the System

Economic activity across the Rayls ecosystem ultimately feeds into the RLS token economy.

For the Rayls Public Chain, transaction fees are generated directly from network usage. Fees are paid in stablecoin and then automatically converted into RLS by a DEX-purchase mechanism.

For Rayls Private Chains, the fee structure may be different. These networks are typically deployed for enterprise clients, and they operate under licensing agreements to cover transaction fees. In practice this could mean fixed monthly payments depending on client size or deployment scale. For example, a smaller deployment paying a lower monthly fee and a large institutional deployment paying more.

We already have clients paying these fees and they will be the same for similar types of clients. We will provide more details into exactly how much each type of client pays in later posts, but the key point is that these fees ultimately integrate into the RLS tokenomics system.

These fees related to transaction costs (both from private chains and the public chain) are used to buy back RLS tokens from the market, after which up to 50% of those tokens are burned. At launch the network will begin with 50% burned, although that parameter may evolve over time as the ecosystem matures.

This mechanism directly links network adoption to token scarcity.

The remaining portion of fees flows into what is commonly referred to as the Network Security Pool, which supports the infrastructure and participants responsible for securing and operating the network.

The older 33% / 33% / 33% Graphic

Some community members have referenced an earlier infographic that showed a 33% / 33% / 33% split between validators, the Foundation, and the Ecosystem Fund.

That graphic reflected an early conceptual version of the tokenomics and is now outdated. The model evolved into the simpler 50% burn / 50% network incentives structure described in the litepaper and MiCAR whitepaper.

As the design matured, the goal was to create a clearer and more direct link between network activity, token scarcity, and network security.

Institutions Running Privacy Nodes

Another important clarification concerns institutions running Rayls Privacy Nodes or Private Chains.

These nodes run inside the institution’s own infrastructure, typically powering internal applications or systems.

When those systems interact with the Rayls Public Chain, the institution pays fees in RLS. Those fees then enter the tokenomics framework described above.

In other words, institutions using Rayls infrastructure are contributors to the network’s economic activity, helping generate demand for RLS and the fee flows that support the ecosystem.

Validators and Block Production

Validators secure the Rayls Public Chain by validating blocks and maintaining network consensus.

If an institution is running a privacy node and also runs a public chain validator node, it may receive rewards for the service of helping secure the public network, just like any other validator.

However, the validator selected to produce any given block is not deterministically tied to the entity generating the transaction activity. Generating transactions does not automatically mean capturing validator rewards associated with them.

This separation ensures that validator rewards remain tied to network security, not simply to network usage.

Participation Through Staking

It’s also important to highlight that running a validator is not the only way to participate in the network.

Any RLS holder can participate in the network’s security economy through staking. Staking allows token holders to contribute to the validation process and share in the distribution of network incentives.

Over time, staking will play a key role in expanding participation beyond the initial validator set.

Validator Set at Launch

Like many networks designed to support institutional-grade infrastructure from day one, Rayls will begin with a permissioned validator set during the early stages of mainnet.

Starting with a smaller group of known validators helps ensure reliability, security, and operational stability while the ecosystem bootstraps.

However, this should be understood as a phased decentralization model, not a permanent structure. As the network grows, validator participation can expand according to defined technical and governance criteria.

Continuing to Improve Documentation

Finally, the questions raised by the community highlight something positive: engaged communities help improve clarity.

We will continue refining public documentation as the network evolves, particularly around validator participation, staking mechanics, fee flows, and the roadmap toward broader validator decentralization.

Feel free to join our weekly AMA (every Thursday), and we appreciate the thoughtful engagement and look forward to continuing to build the Rayls ecosystem together.

‍