1.4 Definitions (Glossary)

Key terms used throughout this whitepaper

This section defines core terms used in the RH whitepaper. Unless otherwise stated, these definitions apply across all sections.

Core Terms

RH (Red Horse) The native token used for membership locking and participation in RH ecosystem programs.

On-chain Membership A membership system where eligibility, tier status, and related parameters are derived from on-chain state (e.g., locked balances and lock records) rather than off-chain credentials.

Locking (Lock / Stake) The act of committing RH to a membership contract under specified rules. Locking is used to establish membership tiers and may affect reward weighting. In this whitepaper, “locking” refers to protocol-defined commitment and does not imply gambling or wagering.

Unlocking The act of withdrawing previously locked RH, subject to the locking rules. Unlocking may change a user’s membership tier and reward eligibility.

Membership Tier A level assigned to a user based on their locked RH and lock configuration. Tiers may provide access, priority, or reward weighting within ecosystem programs.

Reward / Rewards Program A rules-based program that distributes incentives over time (e.g., by epochs). Rewards are not guaranteed and follow predefined parameters and eligibility rules.

Reward Weight (Weighting) A multiplier or scoring mechanism used to determine a user’s share of rewards. Weight can be influenced by membership tier, lock duration, or other program-defined factors.

Epoch A fixed accounting period used for reward calculation and distribution (e.g., weekly or monthly). Reward eligibility and amounts are determined per epoch according to the rewards program rules.

Snapshot A recorded view of on-chain state at a specific time or block number used for determining eligibility, tier status, or reward amounts.

Emission The planned release of RH from designated allocations (e.g., rewards budgets) into circulation according to a defined schedule and rules.

Initial Circulating Supply The amount of RH intended to be liquid and transferable at a given reference point, excluding tokens that are locked, vested, or otherwise restricted.

Treasury Wallets and allocations reserved for ecosystem development, operations, partnerships, and program funding, governed by policies described in this whitepaper.

Rewards Pool A designated wallet or contract-funded allocation used specifically for rewards distribution under the rewards program.

Governance The process and scope by which the community and/or designated stakeholders can propose, discuss, and adopt changes to protocol parameters and policies.

Parameters Configurable variables within the RH system (e.g., epoch length, tier thresholds, reward budgets). Parameters may be updated only through the defined governance and operational controls.

Technical Terms

Solana Chain The blockchain network on which RH smart contracts are deployed. - SPL Token The standard token format on Solana. RH is issued as an SPL token. - Mint Address The on-chain address that defines an SPL token (its supply, decimals, and authority settings). - Program (Smart Contract) An on-chain program on Solana that executes protocol logic (e.g., locking and rewards).

Smart Contract A program deployed on a blockchain that executes deterministically according to its code. RH uses smart contracts to manage locking, membership tiers, and reward distributions.

Multisig (Multi-signature Wallet) A wallet that requires multiple approvals (signatures) to execute transactions. Multisig is used to reduce single-point-of-failure risk for administrative and treasury operations.

Admin Controls Limited administrative functions that may exist to support safe operations (e.g., parameter updates within defined bounds or emergency safeguards). Admin controls are documented and intended to be minimized.

Pause / Emergency Pause A safety mechanism that temporarily restricts certain actions (e.g., locking or claiming rewards) in response to unexpected risks. The presence and scope of pause functionality, if any, are described in the security section.

Upgradeable Contract A contract design pattern that allows logic to be upgraded after deployment (typically via proxy patterns). Whether RH contracts are upgradeable is explicitly stated in the technology and security sections.