Important Notice
This white paper describes the intended design of the Reaction Racing ecosystem, including gameplay systems, token mechanics, governance framework, and related technical architecture. It is provided for informational purposes only.
This white paper does not constitute investment advice, legal advice, or tax advice, and does not constitute an offer or solicitation to acquire securities, financial instruments, or any regulated product. Nothing in this white paper is intended as or should be interpreted as a promise or representation of future value, liquidity, market price, profit, yield, return, appreciation, or support of token value.
Reaction Racing, RRX, and RRGV are described in this white paper solely in relation to intended gameplay, progression, governance, and related ecosystem functions. RRX is intended primarily as a gameplay and ecosystem utility token and not as equity, debt, profit participation, or any claim on assets, revenues, treasury funds, or distributions.
For purposes of this white paper, the phrase “closed-loop digital economy” refers to the intended internal recirculation of RRX through gameplay rewards, entry fees, upgrade expenditures, staking, treasury retention, and other authorized ecosystem uses. It does not mean that RRX is non-transferable or permanently confined to the Reaction Racing ecosystem where external transfer or use is technically enabled and legally permitted.
Any transferability, secondary-market trading, third-party custody, or external use of RRX depends on technical implementation, third-party support, market conditions, and applicable law and may not always be available. The crypto-asset described in this white paper may lose value in part or in full, may not always be transferable, and may not be liquid. The utility token described herein may not always be exchangeable for the gameplay or ecosystem functionality described in this white paper, especially in the event of project failure, discontinuation, or material modification.
Any feature, mechanism, integration, or future ecosystem concept described in this white paper is subject to technical, legal, security, commercial, and operational review and may be modified, delayed, implemented in a different form, implemented only by third parties or separate entities, or not implemented at all.
Participation in blockchain-based systems involves technical, legal, market, and operational risks. The treatment of digital assets, governance rights, taxation, consumer protection, transferability, and related matters may vary by jurisdiction and by the circumstances of each user. Readers should assess these matters independently and obtain professional advice where appropriate.
Abstract
1. Introduction
Games that attach transferable digital assets to player activity have generally faced a common problem. Rewards can be issued quickly, but the mechanisms for re-use inside the game are often weak. When players are rewarded faster than the economy gives them reason to spend, stake, upgrade, or re-enter competition, the system becomes dominated by extraction rather than participation. Under those conditions, game balance deteriorates and long-term retention becomes difficult.
Reaction Racing is designed as a response to this problem. It is a multiplayer racing game based on reaction-time skill, car progression, rank advancement, and season-based competition. The token layer is not treated as a separate speculative feature added around the game, but as part of the game loop itself. Players use RRX (Reaction Racing Token) to improve vehicles, enter competitions, align through staking, and progress through increasingly demanding racing classes.
A key part of the design is the distinction between FREE and VESTED balances. FREE balances are transferable where enabled. VESTED balances remain usable for gameplay functions, but are not immediately available for open transfer. This allows rewards to support progression and continued play while reducing the amount of newly issued value that can exit the system at the moment it is earned.
The governance layer is also separated from the utility layer. RRX serves gameplay and progression. Governance is administered through RRGV (Reaction Racing Governance), a non-transferable token earned through participation and ecosystem contribution. This separation is intended to keep the core economy focused on play while allowing governance influence to broaden over time.
The paper describes the structure of the game economy, the reward and sink model, the balance architecture, the staking system, the token allocation, and the phased governance framework.
2. Game Overview
Reaction Racing is a competitive multi-player play-to-earn racing game built around reaction-time gameplay, car progression, rank advancement, and season-based competition against other players. Players begin in the lowest racing category (R4.7) and progress toward the highest racing category (R1.0) by earning points, improving their car and winning championships. Competitive progression depends on both player skill and continued use of in-game resources. The token design is intended to support utility, progression, and long-term player retention.
3. Token Utility and Balance Architecture
RRX (Reaction Racing Token) powers the core game loop. It is used for car upgrades, season entry fees, staking, and other approved ecosystem utilities. Reaction Racing uses two functional token states: FREE and VESTED. FREE balances are immediately transferable and withdraw-able where enabled. VESTED balances are usable in-game but remain locked from open transfer for a period of 3 years. This balance architecture is intended to support player progression while managing liquid float.
3.1 Closed-Loop Recirculation Design
Reaction Racing uses a closed-loop digital economy in which RRX circulates continuously between player balances, gameplay sinks, and protocol-controlled balances. RRX is distributed through race rewards, season rewards, onboarding incentives, referral rewards, promotion rewards, and other approved emissions. Distributed balances are then used for upgrades, Cup entry fees, staking, and other approved ecosystem utilities. A portion of RRX spent through gameplay is redistributed to players under the published reward rules, while the remainder is retained by the DAO through protocol fees, rake, treasury receipts, and other approved sinks. Treasury-held RRX remains available for redeployment to approved ecosystem uses under the applicable protocol rules.
In this white paper, the term “closed-loop digital economy” denotes the internal recirculation of RRX through gameplay activity, treasury retention, and subsequent ecosystem distribution. FREE balances remain transferable and withdraw-able where enabled. VESTED balances remain usable in-game but restricted from open transfer until the applicable vesting period expires. External holding or transfer of FREE balances does not alter the internal recirculation design of the game economy.
The FREE/VESTED balance architecture supports this recirculation model by separating transferable balances from gameplay balances subject to vesting. Most gameplay-issued RRX is credited as VESTED unless otherwise specified in the published rules. FREE balances form the principal transferable reward layer. VESTED balances remain available for upgrades, entry fees, staking, and other approved ecosystem utilities, and therefore reinforce continued reinvestment into progression and competitive participation. This structure is intended to support player progression, manage liquid float, and preserve the functional role of recurring sinks and treasury recirculation over time.
4. Emissions, Sinks, and Progression Logic
The primary sources of RRX emissions are race rewards and season rewards, with additional onboarding support through welcome bonuses and referral rewards. Racing category promotion rewards and special event rewards also contribute to ecosystem issuance under the published game rules. These reward flows are paired with meaningful in-game sinks, principally upgrades, season entry fees, cup rake, and staking lock-up. The design objective is to allow committed players to continue progressing while limiting the immediate conversion of most game-issued tokens into liquid market supply. Welcome bonuses, referral rewards, and a substantial share of non-race distributions are structured to support gameplay progression rather than immediate liquidity.
4.1 Token States and Reward Distribution
Reaction Racing uses two functional token states: FREE and VESTED. FREE balances are transferable and withdraw-able where enabled. VESTED balances remain usable in-game for upgrades, entry fees, staking, and approved ecosystem utilities, but remain restricted from open transfer until the applicable vesting period expires.
Cup championship standing rewards determine the FREE portion of the economy. At R4 and R3, 100% of cup standings are free. At R2, 80% is free and 20% vested. At R1, 65% is free and 35% vested. All race rewards, single-season rewards, season standings, promotion rewards, welcome bonuses, referral rewards, and other approved game emissions are vested unless otherwise specified in the applicable rules.
4.2 Reward Summary Tables by Rank
Rewards increase with each racing category. As players advance from R4 to R1, race rewards, season rewards, Cup prize pools, entry fees, and promotion rewards all increase to reflect larger grids, longer seasons, and higher competitive difficulty.
The tables below summarize the core reward structure of the game economy, including race rewards, bonus rewards, single-season standings, Cup championship distributions, and promotion rewards. Single-season standings are credited as VESTED balances. Cup championship standings form the principal FREE reward layer, subject to the published rank-based FREE/VESTED split.
This structure is intended to align higher rewards with higher commitment, stronger performance, and continued progression through the competitive ladder.
| Metric | R4 | R3 | R2 | R1 |
|---|---|---|---|---|
| Grid size | 10 drivers | 14 drivers | 18 drivers | 20 drivers |
| Races per season | 6 | 7 | 8 | 9 |
| Metric | R4 | R3 | R2 | R1 |
|---|---|---|---|---|
| P1 race reward (in RRX) | 5 | 7 | 9 | 10 |
| Lowest earning position (in RRX) | P5 (1) | P6 (1) | P7 (1) | P8 (1) |
| Total per race (all positions) (in RRX) | 15 | 22 | 31 | 39 |
| + Fastest lap bonus (in RRX) | +1 | +1 | +1 | +1 |
| + Race complete bonus (in RRX) | +1 | +1 | +1 | +1 |
| Metric | R4 | R3 | R2 | R1 |
|---|---|---|---|---|
| P1 season reward (in RRX) | 15 | 30 | 45 | 60 |
| Lowest earning position (in RRX) | P6 (1) | P7 (1) | P9 (1) | P10 (1) |
| Total per season (all positions) (in RRX) | 35 | 73 | 134 | 191 |
| Token type | VESTED | VESTED | VESTED | VESTED |
| Metric | R4 | R3 | R2 | R1 |
|---|---|---|---|---|
| P1 cup reward (in RRX) | 50 | 100 | 200 | 400 |
| P2 cup reward (in RRX) | 15 | 50 | 105 | 215 |
| P3 cup reward (in RRX) | 8 | 30 | 70 | 145 |
| Lowest earning position (in RRX) | P8 (1) | P14 (1) | P18 (2) | P20 |
| Total prize pool (in RRX) | 85 | 234 | 552 | 1,200 |
| Driver Cup entry fee (in RRX) | 10 | 20 | 40 | 80 |
| Entry fees collected (in RRX) | 100 | 280 | 720 | 1,600 |
| DAO rake (in RRX) | 15 (15%) | 46 (16%) | 168 (23%) | 400 (25%) |
| FREE token % | 100% | 100% | 80% | 65% |
| VESTED token % | 0% | 0% | 20% | 35% |
| Metric | R4 | R3 | R2 | R1 |
|---|---|---|---|---|
| Major rank promotion (in RRX) | — | 200 | 400 | 800 |
| Sub-rank promotions (×7) (in RRX) | 10–40 | 50–80 | 100–130 | 150–500 |
4.3 Onboarding Support
Onboarding incentives decrease as the player base matures. All direct onboarding rewards are credited as VESTED tokens and are therefore usable in-game while remaining subject to the applicable vesting rules. The objective of these incentives is to reduce early progression friction, improve initial retention, and help new players reach meaningful competitive participation without making immediate liquidity the primary purpose of onboarding.
| Phase | New User Bonus | Referral Reward | Context |
|---|---|---|---|
| Founding players | 1,000 RRX | 200 RRX | Maximum incentive to seed the initial community |
| Initial (launch → Month 6) | 500 RRX | 150 RRX | Strong incentive while building critical mass |
| Mature (Month 6+) | 100 RRX –200 RRX | 100 RRX | Sustainable long-term acquisition cost |
In addition to welcome bonuses and referral rewards, Reaction Racing uses a temporary Reward Doubler as an onboarding accelerator. The Reward Doubler increases eligible gameplay rewards for a limited number of seasons and is intended to help new players build momentum during their initial progression period. This mechanism is designed to support learning, retention, and early competitive engagement, while declining over time as the ecosystem matures and organic player growth becomes less dependent on front-loaded incentives.
The duration of the Reward Doubler is highest for Founding Players, lower during the public growth phase, and lowest in the standard phase. This phased structure allows Reaction Racing to use stronger early acquisition support when network effects are most important, while moving toward a more sustainable long-term onboarding cost profile as the player base expands.
| Reward Doubler | Reward Doubler Duration |
|---|---|
| Founding players | First 30 seasons: 2x rewards |
| Initial phase | 10 seasons |
| Standard (mature) | 3 seasons |
4.4 Principal Sink Categories
Reaction Racing relies on recurring in-game sinks to offset reward emissions and support the protocol’s recirculating gameplay economy. The principal sinks are Cup entry fees, DAO rake, dynamic car upgrade costs, and staking lock-up. These mechanisms require continued reinvestment by active players and are intended to support long-term balance between token issuance, gameplay progression, and retained in-game utility.
Entry Fees. Cup participation requires an entry fee that increases with rank. As players move from R4 to R1, grid sizes, total entry-fee pools, prize pools, and DAO rake all increase. A portion of entry fees is returned to players through Cup rewards, while the remainder is retained by the protocol as DAO rake. This structure makes higher ranks more economically demanding and strengthens sink pressure at the upper end of the competitive ladder.
| Rank | Drivers | Entry Fee (in RRX) | Total Pool (in RRX) | Prize Pool (in RRX) | DAO Rake (in RRX) |
|---|---|---|---|---|---|
| R4 | 10 | 10 | 100 | 85 | 15 (15%) |
| R3 | 14 | 20 | 280 | 234 | 46 (16%) |
| R2 | 18 | 40 | 720 | 552 | 168 (23%) |
| R1 | 20 | 80 | 1,600 | 1,200 | 400 (25%) |
Car Upgrades. Car progression is supported by a dynamic pricing model for upgrade components. Upgrade costs are lower at earlier component levels and rise gradually as components approach their maximum level. This makes initial progression more accessible while requiring materially greater in-game expenditure for advanced optimization.
The price for car upgrade components uses a dynamic formula to calculate the upgrade pricing:
Upgrade Cost = Base_Cost – ((( 34 – Component_Level)/100) * Base_Cost)| Upgrade Component | Base Cost (in RRX) | Price at Starting Level 16 | Price at Max Level 50 |
|---|---|---|---|
| Engine | 100 | 82 | 116 |
| Fast Corners | 50 | 41 | 58 |
| Medium Corners | 50 | 41 | 58 |
| Slow Corners | 50 | 41 | 58 |
Booster and Turbo consumables are separate one-time capacity purchases per rank class and are not subject to dynamic pricing.
| Car Upgrade Consumable | Upgrade Cost (in RRX) |
|---|---|
| Booster | 100 |
| Turbo | 250 |
5. Staking System
Staking in Reaction Racing is a gameplay-alignment mechanism, not a passive-yield mechanism. By staking RRX, players may obtain modest increases in car performance and in race and season rewards. These benefits apply only through active racing and are intended to support progression, retention, and long-term participation in the game economy. Staking does not create guaranteed returns or any fixed entitlement to profit.
The staking tiers are intentionally limited in scale. Their purpose is to reward commitment without overwhelming the importance of player skill, race execution, or car quality. At higher staking levels, players may also receive a governance-weight bonus, as described in Section 7.
Unstaking returns balances subject to the applicable account logic and vesting rules.
Staking Tiers
| Level | RRX Staked | Performance Bonus | Reward Bonus |
|---|---|---|---|
| SL0 | 0 | 0% | 0% |
| SL1 | 100 | 1% | 1% |
| SL2 | 500 | 2% | 2% |
| SL3 | 2,000 | 3% | 3% |
| SL4 | 5,000 | 4% | 4% |
6. Token Allocation
The total supply of RRX is fixed at 50,000,000,000. Of this amount, 95% is allocated to the Community & Ecosystem and 5% is allocated to the Core Team / Operations / Founder. This allocation is intended to place the substantial majority of supply within gameplay, player growth, ecosystem support, and community use, while reserving a limited portion for development, security, legal, operational, and founder-related functions.
Total allocation
| Allocation | Share | RRX |
|---|---|---|
| Community & Ecosystem | 95% | 47,500,000,000 |
| Core Team / Operations / Founder | 5% | 2,500,000,000 |
Community & Ecosystem sub-allocation
| Bucket | Share of Total Supply | RRX |
|---|---|---|
| Racing & Cup Rewards | 80% | 40,000,000,000 |
| Player Growth & Onboarding | 6% | 3,000,000,000 |
| Staking / Gameplay Utility Incentives | 4% | 2,000,000,000 |
| Ecosystem / Liquidity / Exchange Support | 3% | 1,500,000,000 |
| Community Governance & Events | 2% | 1,000,000,000 |
Core Team / Operations sub-allocation
| Bucket | Share of Total Supply | RRX |
|---|---|---|
| Core Team & Development | 1.5% | 750,000,000 |
| Founder | 1.0% | 500,000,000 |
| Marketing / Growth / Partnerships | 0.8% | 400,000,000 |
| Legal / Compliance / Corporate | 0.7% | 350,000,000 |
| Security / Audits / Infrastructure | 0.5% | 250,000,000 |
| Treasury Reserve / Strategic Operations | 0.5% | 250,000,000 |
No Token Sales
Reaction Racing has no private token sale, no venture capital token allocation, and no external investor token round. The project is founder-funded. No token supply is reserved for outside investor classes with preferential pricing, early liquidity, or special distribution rights.
This allocation structure is intended to support a community-first ecosystem with broad player participation and without concentrated external token overhang.
7. Governance
Reaction Racing uses a phased DAO governance structure. Governance is separate from the core game economy. RRX is the utility token for gameplay, upgrades, entry fees, and staking. Governance is administered through a separate non-transferable token, RRGV, intended to reflect participation and ecosystem alignment rather than economic ownership. In the early stages, governance is founder-led. Over time, governance broadens as the community earns RRGV through participation. The framework consists of community-earned RRGV, Founder Base Governance Weight, and temporary founder protection rights exercised through a Founder Protection Multisig during the first seven years following TGE. The design described in this Section reflects the intended launch structure and may be adjusted for technical, legal, or security reasons at deployment.
7.1 Governance Token: RRGV
| Name | Reaction Racing Governance Token |
|---|---|
| Ticker | RRGV |
| Transferability | Non-transferable |
| Monetary value | None. RRGV cannot be bought, sold, exchanged or used as collateral. |
| Purpose | Governance participation, voting weight, governance-linked in-game utility |
RRGV does not confer any ownership interest, entitlement to protocol surplus, dividend, redemption claim, or economic right of any kind. It exists solely as a governance participation metric earned through gameplay and ecosystem contribution.
7.2 Governance Power Structure
Governance power in Reaction Racing arises from two sources. The first is Community Governance Power, earned through the issuance of non-transferable RRGV through gameplay, progression, and participation. The second is Founder Governance Power, consisting of Founder Base Governance Weight (FBGW) assigned at genesis, together with any RRGV separately earned by the founder through ordinary gameplay. FBGW is non-transferable, non-economic, and exists solely for governance purposes. The founder’s governance weight is highest at launch and declines over time under the phase-reduction framework, while community governance expands through continued RRGV issuance.
7.3 Founder Base Governance Weight
At genesis, the founder is assigned 1,500,000,000 units of Founder Base Governance Weight. This allocation is separate from the RRX token economy and confers no economic right. It exists solely to support founder-led governance during the bootstrap phase. The founder’s effective voting weight is determined by applying the declining Founder Phase Multiplier to FBGW, and then adding any RRGV earned by the founder through ordinary gameplay.
Founder Voting Weight = (FBGW × Founder Phase Multiplier) + Founder Earned RRGV7.4 Founder Phase Reduction Schedule
The Founder Phase Multiplier declines by reference to ecosystem growth, measured in verified users. The purpose of the schedule is to provide a visible path from founder-led governance toward broader community governance while preserving founder majority during bootstrap and early scale.
| Phase | Trigger | Founder Phase Multiplier | Effective Founder Base Weight | Est. Founder Share |
|---|---|---|---|---|
| Ph. 0 | Pre-launch / closed alpha | 1.00x | 1,500,000,000 | — |
| Ph. 1 | Public launch / Founding Players | 0.95x | 1,425,000,000 | ~100% |
| Ph. 2 | 1,500 verified users | 0.90x | 1,350,000,000 | ~99% |
| Ph. 3 | 10,000 verified users | 0.82x | 1,230,000,000 | ~99% |
| Ph. 4 | 50,000 verified users | 0.72x | 1,080,000,000 | ~97% |
| Ph. 5 | 100,000 verified users | 0.64x | 960,000,000 | ~90% |
| Ph. 6 | 250,000 verified users | 0.56x | 840,000,000 | ~74% |
| Ph. 7 | 500,000 verified users | 0.50x | 750,000,000 | ~48% |
A verified user is a player who has completed at least 10 seasons, whether single or Cup, and has a positive RRX transaction history consisting of at least one earn event and at least one spend event. This definition is intended to reduce sybil inflation of the user count and to ensure that governance phase transitions are triggered by genuine ecosystem growth.
Before the protocol reaches 500,000 verified users, the founder’s governance weight is not reduced below the level required to maintain ordinary-governance majority. The founder first ceases to hold ordinary majority only after the protocol has reached meaningful scale.
7.5 Community RRGV Earning Mechanics
RRGV is earned through gameplay and participation in the ecosystem. It is not sold and is not issued according to a discretionary DAO emissions schedule. Instead, it is earned at fixed rates tied to racing activity, seasonal performance, and governance participation. In this way, governance power is intended to arise from sustained involvement in the protocol rather than from transfer or purchase.
| Source | RRGV Earned | Notes |
|---|---|---|
| Race participation (per race) | R4: 1.0, R3: 1.5, R2: 2.0, R1: 3.0 | Base reward for race completion, increasing by rank |
| Race placement | R4: 2.0 / race_placement R3: 3.0 / race_placement R2: 4.0 / race_placement R1: 5.0 / race_placement | Additional RRGV based on finishing position |
| Cup Season standing | R4: 30 / season_standing R3: 60 / season_standing R2: 90 / season_standing R1: 120 / season_standing | Additional RRGV based on final season position |
| Governance participation | 30 RRGV per valid vote cast | Rewards active governance engagement |
Under the race-placement rule, a player receives additional RRGV equal to the applicable rank value divided by finishing position. Thus, an R3 driver finishing P2 receives 3.0 / 2 = 1.5 RRGV. Under the Cup Season standing rule, an R2 driver finishing a Cup season in P4 receives 90 / 4 = 22.5 RRGV.7.6 Voting Weight Formula
Voting weight in DAO governance is determined by three components: a user’s total earned RRGV, the multiplier associated with the user’s staking tier, and an additive wealth bonus. The purpose of the formula is to make earned participation the principal source of governance power, while giving limited additional weight to sustained staking and recognized in-game wealth.
The Voting Weight formula = (Earned RRGV x Staking Multiplier) + Wealth Bonus| Component | Mechanism | Range |
|---|---|---|
| Earned RRGV | Accumulated through racing and ecosystem participation | Uncapped (primary driver of voting weight) |
| Staking Multiplier | Based on RRX staking tier: SL0 = 1.00x, SL1 = 1.02x, SL2 = 1.04x, SL3 = 1.07x, SL4 = 1.10x | 1.00x – 1.10x |
| Wealth Bonus | 10 voting weight per 100 RRX of recognized wealth capped at 10,000 RRX | 0 – 1000 (additive) |
Recognized wealth includes the measured value of eligible wallet assets and the user’s cars, as defined by the protocol rules. The wealth bonus is capped and remains secondary to earned RRGV.
7.7 Founder Protection Multisig
For the first 7 years following TGE, certain limited constitutional and emergency powers are exercised through the Founder Protection Multisig. The purpose of this mechanism is to protect the protocol during the early growth period while preventing unilateral founder control.
| Property | Value |
|---|---|
| Composition | 1 founder + 8 trusted long-term signers (9 total) |
| Approval threshold | Founder + any 2 trusted signers (3-of-9, founder required) |
| Duration | 7 years from TGE — automatically expires |
| Scope | Veto on Protected Proposals + emergency actions only |
The founder alone cannot act. The founder plus one signer cannot act. The trusted signers cannot act without the founder. The mechanism is therefore collaborative in form, while preserving the founder’s limited constitutional role during the protection period.
7.8 Scope of Founder Protection Rights
The Founder Protection Multisig may veto Protected Proposals. These include token-contract amendments, emissions-framework changes, treasury-policy rewrites, governance-rule rewrites, changes to vesting architecture, changes to founder protection rights, liquidation, transfer, or repurposing of strategic reserves, transfer of core intellectual property, protocol ownership, or treasury control, and high-risk integrations materially affecting security. Ordinary proposals are not subject to founder veto.
The Founder Protection Multisig may also take emergency action where reasonably necessary to protect users, treasury assets, protocol integrity, service continuity, legal position, or smart-contract security. Such action may include pausing vulnerable functionality, temporarily suspending withdrawals, disabling integrations, halting emission flows, or activating emergency migration procedures. Any emergency action must be limited in scope, documented, publicly disclosed, and subject to later governance review.
7.9 Proposal Classes
Proposal types are divided into Ordinary and Protected classes. Ordinary proposals govern routine matters. Protected proposals govern constitutional, economic, treasury, and security-sensitive matters. Thresholds are measured against the participating voting weight, meaning only the voting weight actually cast in a proposal is counted. Non-voting participants are excluded.
| Type | Threshold | Founder Veto | Examples |
|---|---|---|---|
| Ordinary | Majority + 1 of participating voting weight | No | Events, race format, seasonal balancing, routine budget use |
| Protected | 66% supermajority of participating voting weight | Yes (during 7-year protection period) | Token contracts, emissions, treasury policy, governance rules, vesting, reserves |
Routine use of the approved 4% operating allocation within already defined budget categories is treated as an Ordinary Proposal. Material reallocations between categories, however, are treated as Protected Proposals. This includes reallocations above 10% of a category or any single release above 0.25% of total supply.
7.10 Trusted Signer Alignment
To align the long-term interests of the 8 trusted signers with the protocol, each signer receives a vested alignment allocation of 2,000,000 RRX, for a total of 16,000,000 RRX, sourced from the 4% operating allocation. This allocation is intended to support continuity, long-term responsibility, and active stewardship during the Founder Protection Period.
The vesting schedule is 0% immediate unlock; 5% unlock after 12 months; and the remaining 95% vesting in quarterly releases from month 13 through month 84. There is no extension beyond year 7. Any unvested allocation is forfeited upon resignation, removal for cause, or prolonged inactivity. Tokens distributed under this alignment allocation are credited as VESTED balances and do not enter immediate circulation as liquid supply.
7.11 Signer Management
A trusted signer may be removed by the founder together with at least 2 additional trusted signers in the event of resignation, incapacity, legal disqualification, prolonged inactivity, conflict of interest, security negligence, or misconduct. For this purpose, prolonged inactivity means non-responsiveness for 60 days or more. Replacement signers are selected on the basis of trustworthiness, strategic alignment, availability, independence, and security competence. Any replacement must be publicly disclosed.
7.12 Continuity & Emergency Depletion
If the number of active trusted signers temporarily falls below 8, the Founder Protection Multisig continues to operate, provided that at least 2 active trusted signers remain. If fewer than 2 remain, ordinary veto power is suspended until the signer group is restored. During such period, the founder may take only temporary emergency actions strictly necessary to preserve protocol security and continuity. Any such action must be narrowly tailored, publicly disclosed, and must expire automatically unless ratified after restoration of the signer group.
7.13 Founder Succession
If the founder dies, becomes incapacitated, or is otherwise legally unable to serve, the founder’s role within the Founder Protection Multisig passes to a pre-designated Founder Successor or Founder Successor Vehicle. Activation of such succession requires confirmation by at least 3 active trusted signers. The purpose of this mechanism is to prevent constitutional paralysis during the Founder Protection Period.
7.14 End of Founder Protection Period
At the end of the 7-year Founder Protection Period, the founder’s veto rights terminate automatically, emergency override powers terminate automatically, the Founder Protection Multisig dissolves, trusted signer mandates end, and signer vesting concludes without extension. Thereafter, the founder participates in governance only through the remaining effective governance weight, consisting of FBGW at 0.50x = 750,000,000 units, together with any separately earned RRGV. At that stage, the founder remains a significant governance participant, estimated at approximately 27–29% at full maturity, but no longer acts as a constitutional gatekeeper.7.15 Governance-Linked Utility Benefits
| Tier | Valid Votes in 12 Months | Entry Fee Reduction | Performance Bonus |
|---|---|---|---|
| Active Voter | 3+ | 2% | +0.2% |
| Engaged Voter | 6+ | 4% | +0.4% |
| Steward | 9+ | 7% | +0.7% |
| Core Steward | 12+ | 10% | +1.0% |
Governance-linked performance benefits are capped at +1.0% in aggregate. Entry-fee reductions are capped at 10%. The thresholds above are measured by the number of valid votes cast by a user during the preceding 12 months. These benefits lapse automatically if the user no longer meets the applicable valid-vote threshold during the preceding 12-month period.
7.16 Treasury Management
The DAO treasury receives the principal token inflows generated by the protocol, including car upgrade payments, Cup championship rake, and entry-fee related inflows. The treasury is the sole source from which gameplay reward emissions are made.
7.17 Anti-Abuse Measures
To preserve governance integrity, RRGV is non-transferable and governance eligibility is subject to minimum gameplay activity. The protocol is intended to apply anti-sybil measures to reduce multi-account manipulation. Spam voting, duplicate voting, and similar abusive conduct do not count toward governance-participation thresholds or related multipliers. The protocol may refine these safeguards over time as the ecosystem develops.
8. Technical Implementation
Reaction Racing is designed as a single-root contract system. The canonical smart-contract and settlement layer is intended to be Avalanche C-Chain. The core contracts for RRX, RRGV, vehicle assets, vesting, staking, treasury accounting, rewards, incentives, governance, and official contract registration are intended to be deployed on Avalanche C-Chain. Base and BNB Chain may be used as player-acquisition, wallet-onboarding, campaign, referral, and community-growth channels, but are not intended to maintain independent canonical economic state. The authoritative record of protocol state is therefore intended to reside on Avalanche C-Chain.
8.1 Canonical State
The protocol is intended to maintain a single canonical state for token supply, vesting, staking, treasury balances, vehicle state, reward eligibility, and governance weight. That state is intended to be defined exclusively by the Avalanche C-Chain contract set during the initial on-chain phase. Base and BNB Chain are not intended to maintain an independent native source of truth for RRX, RRGV, governance authority, vehicle state, or other settlement-relevant protocol state. If a dedicated ReactionRacing L1 is later launched, its role is intended to be introduced through approved migration and registry procedures, rather than through an uncoordinated parallel economy.
8.2 Contract Scope
The intended Avalanche C-Chain contract set consists of: the RRX utility-token contract; the RRGV governance-token contract; the car asset or car registry contract; the vesting controller; the staking controller; the treasury contract; the reward distributor; the incentives controller; the campaign claim registry; the official contract registry; the migration controller; the governance executor; and such other protocol modules as may be required by the final deployment architecture. No general administrative function is intended to permit unilateral modification, confiscation, freezing, reversal, or reassignment of player-held balances or player-held vehicle tokens.
The car asset contract or car registry is intended to represent each player-held car as a unique wallet-held asset or registry entry on Avalanche C-Chain. The contract is intended to record, or authoritatively resolve, rank class, component levels, accumulated performance points, derived performance bonus, eligibility status, and such delegation permissions as may be required by the Race Team system. Upgrade expenditures, crash-related performance-point adjustments, and other settlement-relevant changes affecting vehicle state are intended to occur through authorized protocol interactions involving the applicable RRX expenditure or other authorized sponsored-settlement path under the applicable rules.
The reward or incentives controller is intended to administer onboarding, referral, promotional, retention, and other approved incentive allocations under the applicable protocol rules. Such allocations may include sponsored upgrades, sponsored entry fees, and other sponsored gameplay expenditures or benefits approved by the protocol. Base and BNB campaign activity may be used as eligibility evidence, but final reward eligibility, claim status, and accounting are intended to be written to Avalanche C-Chain under the applicable implementation.
The treasury contract is intended to receive protocol-owned token inflows, including upgrade payments, Cup rake, and other entry-fee related inflows, and to serve as the controlled source of governance-authorized reward emissions, treasury transfers, sponsored incentive budgets, liquidity-support budgets, migration-related budgets, and other disbursements under the applicable protocol rules.
These contracts are intended to be implemented and deployed using standard EVM development workflows. The official contract registry is intended to record the active Avalanche C-Chain contract addresses, active acquisition-channel adapters, deprecated contracts, and any future RR L1 migration status under the applicable governance and security procedures.
8.3 Separation of Gameplay and Settlement
Real-time gameplay is not intended to be executed onchain on a per-input basis. Reaction-time measurement, matchmaking, race-state progression, anti-abuse checks, and session management are intended to operate in the application layer. The contract layer is reserved for settlement-relevant actions, including reward settlement, entry-fee accounting, upgrade expenditures, staking changes, vesting updates, treasury flows, vehicle-state updates, and governance actions. This separation is intended to avoid placing real-time gameplay requirements on transaction confirmation and block production.
8.4 Player Access and Wallet Layer
In addition to Avalanche-native wallet access, the protocol may support player access through Base and BNB Chain wallet environments. In this architecture, Base and BNB Chain are intended to function as player-acquisition, campaign, referral, and wallet-onboarding layers only. They are not intended to function as independent sources of issuance, governance, treasury state, vehicle state, staking state, or canonical protocol accounting. The authoritative record of RRX, RRGV, vesting, staking, treasury balances, vehicle state, and governance weight remains on Avalanche C-Chain during the initial on-chain phase.
8.5 Wallet Control and Account Resolution
Under the intended implementation, the player’s settlement address is a player-controlled EVM wallet address. Because Avalanche C-Chain, Base, and BNB Chain are EVM-compatible networks, a player may use the same externally owned account address across those networks where the same wallet or private key is used. A player may sign a login, campaign, or account-resolution message from Base, BNB Chain, or Avalanche C-Chain. Such signature is intended to establish wallet control and account linkage; it is not intended to transfer funds or create settlement outside the canonical Avalanche C-Chain contract system.
Gameplay settlement resolves against the player’s Avalanche C-Chain balances, vehicle tokens or vehicle registry entries, and Avalanche C-Chain contract state. The use of a Base or BNB Chain wallet environment therefore changes the access or acquisition layer only. It does not change the location of canonical token balances, vesting state, staking state, treasury accounting, vehicle state, or governance authority.
For application-layer purposes, the protocol may resolve one or more player-controlled wallet addresses to a single player account under the applicable account rules. Wallet control determines transaction authorization, but reward eligibility, referral eligibility, promotional eligibility, and similar application-layer rights may be determined at the player-account level rather than at the individual wallet-address level.
8.6 External Representations
All settlement-relevant gameplay actions are intended to occur on Avalanche C-Chain during the initial on-chain phase. This includes, without limitation, Cup entry-fee payments, car upgrade expenditures, staking changes, reward settlement, vesting updates, governance actions, and other tokenized gameplay actions recorded by the contract system. A player entering through Base or BNB Chain therefore continues to interact with the Avalanche-settled protocol, rather than with a separate Base-native or BNB-native settlement system.
For supported gameplay actions, the player is intended to bear the underlying RRX cost of the action, but not necessarily the associated Avalanche C-Chain network fee. The Reaction Racing DAO may fund and operate the gas-sponsorship layer required for approved protocol interactions so that ordinary gameplay use does not require the player to maintain a separate AVAX balance. Such sponsorship may be provided through a protocol-managed relayer, paymaster, smart-account architecture, or equivalent supported architecture. Base and BNB Chain gas sponsorship may be used separately for approved campaign interactions on those acquisition channels.
Gas sponsorship is intended to apply only to approved protocol interactions. It is not intended to extend to arbitrary wallet transfers, unsupported contract calls, or third-party transactions outside the Reaction Racing protocol flow. The DAO is intended to maintain the Avalanche C-Chain infrastructure and gas reserves required for such sponsored execution, subject to the final technical, security, and budgetary design adopted at deployment.
8.7 Governance Locality
Governance authority is intended to remain on Avalanche C-Chain during the initial on-chain phase. The authoritative RRGV record, voting-weight calculation, proposal execution, treasury controls, and founder-protection logic are intended to remain Avalanche C-Chain-native. Base and BNB Chain may provide acquisition-channel proofs or interface convenience, but are not intended to host canonical governance state. Any future relocation or partial execution of gameplay or governance-related functions on RR L1 would be subject to security review, migration controls, and the applicable governance approval process.
8.8 Design Objective
The objective of this architecture is to maintain a single canonical contract system on Avalanche C-Chain while permitting player acquisition through Base and BNB Chain and preserving a later migration path toward a dedicated ReactionRacing L1. Avalanche C-Chain functions as the authoritative economic execution and settlement layer and as the intended liquidity and exchange-integration layer for RRX. Base and BNB Chain function only as acquisition, campaign, referral, and wallet-onboarding layers. RR L1, if launched after product traction, security readiness, and governance approval, is intended to become the dedicated gameplay execution layer while canonical RRX liquidity and treasury accounting remain anchored on Avalanche C-Chain unless modified under an approved migration framework.
9. Future Ecosystem Concepts
Reaction Racing may, in the future, explore third-party ecosystem integrations, including liquidity tooling, lending interfaces, collateralized gameplay utilities, settlement tools, and similar infrastructure. Any such feature would be subject to separate technical, legal, commercial, and jurisdictional review. These concepts do not form part of the core Reaction Racing product described in this white paper and may be implemented, if at all, only by independent third parties or separate entities.
10. Risk Factors and Live-Balancing Statement
Game economies are dynamic. Actual outcomes depend on player behavior, retention, reward cadence, balancing decisions, and broader market conditions. Reward parameters, staking parameters, event structures, and governance-linked utility may be modified over time where necessary to protect gameplay quality and economic stability. The protocol may restrict, delay, modify, or discontinue features in response to legal, technical, security, or operational concerns. Nothing in this document is to be interpreted as a promise of token value, future liquidity, profit, or economic return.
11. Conclusion
Reaction Racing is designed as a skill-based game economy with recurring utility sinks, managed liquid float, community-weighted token allocation, an Avalanche C-Chain canonical settlement architecture, and a phased path toward broader community governance and, if justified by traction, dedicated RR L1 gameplay execution. The RRX and RRGV systems are intended to support competition, progression, retention, and long-term stewardship. The protocol is designed to remain game-first in structure and to avoid embedding unnecessary financial-product features into the core system.