4.2 Smart Contracts
A minimal contract suite for membership locking and rules-based rewards
RH is implemented through a focused set of on-chain programs on Solana. The design emphasizes clarity, auditability, and minimized trust assumptions: membership is derived from locking state, rewards follow published rules and budget constraints, and operational powers are tightly scoped.
Deployment fields to be updated: RH Token Decimals and Contract Addresses (listed in Section 4.4).
Contract Set
1) RH Token Contract (SPL)
RH is issued as an SPL token on Solana with a fixed total supply of 10,000,000,000 RH. The token follows standard SPL behavior for transfers and holdings.
Supply Policy
Fixed supply at issuance (no inflation by default).
Any burn mechanics (if used) are transparent and voluntary and do not guarantee outcomes.
Deployment Reference
RH Mint Address: A3rk5gtQ2S24Fhz8Ctfhjj2bDgK1SZF7fXvbH1Jty5Bp
Decimals: 9
2) Membership (Locking) Program
The locking program establishes verifiable membership state by recording lock positions and enforcing lock terms. Tier eligibility is derived from locking state and evaluated at snapshot checkpoints to maintain consistent accounting across epochs and campaigns.
Lock positions are recorded in program-derived accounts (PDAs), enabling verifiable snapshots and deterministic tier evaluation.
Deployment Reference
Locking Program ID: [Update after deployment]
Operational Scope
Administrative scope is intentionally limited to parameter updates within governance, and sensitive authorities are managed under conservative controls.
3) Rewards Program
The rewards program distributes incentives under published rules and explicit budget constraints. Rewards may be issued through recurring epoch cycles and/or time-bounded campaigns, depending on the active configuration.
Eligibility is evaluated from locking state at snapshot checkpoints. Reward accounting and distribution state are recorded in program-derived accounts (PDAs) to support verifiable, consistent settlement.
In addition to ecosystem campaigns and community initiatives, RH may run lightweight P2E-style participation campaigns as optional programs. These campaigns are designed to reward eligible members for transparent, rules-based participation (e.g., completing defined activities), while maintaining clear budgets, caps, and disclosures.
Update after deployment
Rewards Program ID: [Update after deployment]
Rewards Vault (Token Account): [Update after deployment]
4) Operational Wallets (Treasury / Rewards Pool)
RH is designed with conservative operational practices to reduce discretionary risk and improve transparency. Sensitive authorities and operational actions are intentionally limited in scope and executed under controlled procedures.
Operational accounts (where applicable)
Treasury Account: used for long-term operations and ecosystem sustainability.
Rewards Vault (Token Account): used for program reward distributions under published budgets and rules.
Liquidity Operations Account: used for market support activities, where applicable.
Authority management
Sensitive authorities (including relevant token and program authorities) are managed under multisig-based controls or equivalent conservative governance processes.
Separation of duties is applied across treasury, rewards, and liquidity operations to reduce single-point risk.
Operational scope
Operational actions focus on bounded parameter updates, budget configuration, and disclosures.
RH does not guarantee rewards, yields, or returns; distributions (if any) follow published rules and budget caps.
Transparency
Official references and addresses are published via verified channels, and any changes are disclosed with versioned updates.
Last updated