Rando

Rando White Paper

Version: 1.0
Published: August 1, 2026
Website: runrando.com
Token: $RANDO
Network: Solana
Mint: EZthQ6SUL51jJihQiFMDiZVmZiRMNjMQoTb7rNvTBAGS

1. Executive Summary

Rando is a programmable intelligence and execution platform for token projects.

Its two live primary systems are:

Rando is designed to connect information with action. Rando OS helps a creator understand what is happening and decide what to do. Rando Rewards and future execution products carry out configurable actions and record relevant blockchain activity.

$RANDO is the single token associated with the Rando ecosystem. No separate token is planned for the products described in this paper.

2. The Problem

Token creators often use disconnected tools for:

Analytics can identify a problem without providing a way to act. Fee distributions may be static or manually managed. Community reward programs may provide limited public information about selection and payout.

Rando's goal is to place project intelligence and programmable execution in one system.

3. The Rando Model

Rando is organized around a continuous operating loop:

  1. Monitor token, holder, fee, market, and social activity.
  2. Identify relevant changes, risks, and opportunities.
  3. Present analysis and possible actions.
  4. Execute selected actions through programmable fee routing and reward systems.
  5. Record applicable results and blockchain activity.

Individual components may operate independently or together.

4. Rando OS - Live Command and Control

Rando OS is the live command and control center for a token project.

Current capabilities include:

Rando OS is non-custodial. Wallet authentication uses message signing and does not give Rando access to private keys or transaction authority.

Access may be offered through different service tiers.

5. Rando Rewards - Live Execution

Rando Rewards is live and is Rando's primary execution product.

It uses token fees to fund configurable reward systems. Depending on the active mode, rewards may be:

Reward settings may differ by project, campaign, token, and mode.

6. Holder Rewards

Holder rewards select a wallet from an initial qualifying holder set and apply final validation before a candidate can receive the reward.

For current $RANDO holder rewards:

Ineligible wallet categories include:

The current system automatically enforces certain exclusions, including configured addresses and non-system-owned accounts. It may not automatically identify every exchange, custodian, or other ineligible category. Rando may make additional eligibility and disqualification decisions when necessary.

Continuous-hold validation is applied to selected candidates. Aggregate eligible-wallet counts may include wallets that would fail final validation if selected.

7. Social Rewards

Social campaigns select participants through supported platform identities.

X is used in the live reward path. Integrations for TikTok, GitHub, Kick, and Instagram have been implemented or developed to varying degrees, and availability depends on the applicable mode and third-party support.

A social identity may be resolved to an existing wallet or to a wallet provisioned through Bags. This allows a winner to participate without creating a wallet in advance.

Winner displays may show a social username. Underlying proof data, public APIs, and blockchain links may also expose or allow association with a wallet address.

8. Reward Delivery

Direct payouts may be made from an on-chain prize wallet. The Rando system signs those transactions and generally pays the network fee and related account-creation costs where required.

Campaign rewards may also be delivered through Bags fee-sharing configuration. In those cases, Rando configures the applicable fee route and Bags handles the associated wallet infrastructure.

Rando does not currently enforce a general claim deadline in code. Rewards assigned to a winner are not ordinarily reclaimed solely because they remain unclaimed. Continued access depends on Bags and the relevant wallet infrastructure.

Minor technical adjustments may occur because of token decimals, rounding, or transaction mechanics.

9. Randomization

Randomization methods vary by reward mode.

Current implementations include:

Not every mode currently stores or publishes the method, seed, algorithm, or enough information for an independent observer to reproduce the selection.

Rando therefore does not claim that every draw is independently verifiable in its current form. Public transparency and verification capability vary by mode and record version.

10. Public Records

Depending on the reward mode and record version, public records may include:

For current holder history, the public API provides the winner wallet and the rendered interface may display it in truncated form. Full addresses remain available through the API and linked blockchain records.

Some draw values are returned during execution but are not stored as part of permanent history. Current holder records do not necessarily retain:

The current excluded-wallet count reflects the configured exclusion list and may not include every wallet removed by every filtering rule.

Rando does not publish a complete eligible-wallet list and does not currently persist a complete holder snapshot for every draw.

11. Programmable Fee Routing

Programmable fee routing is a core Rando feature.

A project's available fee allocation may be divided among configurable destinations, including:

Allocations may vary by project, campaign, reward mode, and objective.

Rando does not define one permanent fee split in this white paper. Current allocations are displayed through the applicable interface or campaign.

Configuration changes apply prospectively. Completed blockchain transactions cannot be retroactively changed.

12. Reward Modes

12.1 Implemented Modes

Holder Mode

Qualifying wallets enter a fee-funded randomized reward cycle.

Campaign and Social Mode

Eligible social participants may receive fee-based rewards through supported identity platforms.

Survivor Mode

Participating wallets are eliminated over successive rounds until one remains. Survivor includes blockchain-derived seeded audit information.

Cipher Mode

Participants complete clues and submit a valid solution. A winner is selected from verified solvers.

Afterlife Mode

Eliminated participants may predict the final Survivor winner and share a separate reward pool when correct.

12.2 In Development

Cipher Partner Mode

Multiple projects contribute tasks and clues to a combined campaign with daily or final rewards. Partner-facing access remains in development.

12.3 Planned Modes

Battle Mode

Two token communities compete under published performance rules, with rewards or fee routing determined by the result.

Jackpot Mode

Fees accumulate for a defined period before one qualifying participant receives the resulting pool.

Bounty Mode

Participants complete a defined action or mission and enter a randomized reward selection.

Rando Vault

Reward allocations accumulate in a visible on-chain wallet until deployed into a selected reward mode.

Planned modes remain subject to development, testing, technical limitations, third-party support, and legal review.

13. Composable Campaigns

Reward modes are designed to operate separately or in sequence.

Examples include:

The objective is to give projects multiple ways to continue engagement beyond a single result.

14. The $RANDO Token

14.1 Token Information

The mint address should always be verified before interacting with the token.

14.2 Role

$RANDO is the single token associated with the Rando ecosystem.

No separate token is planned for Rando OS, Rando Rewards, Rando Fees, Rando Launch, Rando Studio, or Rando Hub.

The utility of $RANDO may expand as additional products are released. Current utility and planned utility should be distinguished through official Rando materials.

14.3 No Promise of Value

$RANDO does not provide a guaranteed return, profit, price increase, liquidity level, or reward.

Its market value may be volatile and may fall to zero.

15. System Architecture

Rando currently relies on a combination of:

Some actions occur on-chain. Other actions, including scheduling, eligibility computation, selection, configuration, and record management, may occur through Rando-operated software.

Rando should not be described as fully autonomous, fully decentralized, or entirely trustless.

16. Data and Privacy

Rando may process:

Rando does not currently use advertising cookies or analytics trackers.

The Cipher experience may store a username and limited participation state in browser local storage.

Campaign data may be retained after a campaign ends. Rando does not currently guarantee deletion within a specific period.

Public winner results may be retained permanently. Winner displays may use a social username or truncated wallet address, while underlying APIs and blockchain records may expose additional information.

17. Roadmap

Phase 1 - Rando Fees

Rando Fees expands programmable creator-fee routing.

Planned capabilities include:

Rando Rewards becomes the first execution component inside Rando Fees.

Phase 2 - Multi-Chain Expansion

Rando plans to expand beyond Solana, beginning with Robinhood Chain.

Potential later networks include:

Multi-chain plans depend on infrastructure, technical feasibility, platform support, and development priorities.

Phase 3 - Rando Launch and Rando Studio

Rando Launch

Rando Launch is planned as a programmable token-launch platform supporting:

Rando Studio

Rando Studio is planned as a creative and launch-support layer providing:

Phase 4 - Rando Hub

Rando Hub is planned as a cross-platform social and token intelligence system connecting:

Potential capabilities include multi-platform publishing, social-to-chain correlation, promoter performance analysis, community-health scoring, and unified AI analysis.

Roadmap items are planned directions, not guaranteed commitments.

18. Administration and Change

Reward parameters are programmable and may differ by project and campaign.

The Rando team may configure future:

Rando may pause, modify, discontinue, cancel, invalidate, or rerun features or selections where necessary because of technical errors, fraud, manipulation, invalid data, security concerns, or third-party failures.

Completed blockchain transactions generally cannot be reversed.

19. Risks and Limitations

Use of Rando and digital assets involves risks, including:

Rando does not guarantee uninterrupted operation, successful participation, receipt of rewards, token value, liquidity, or regulatory treatment.

20. Legal Notice

This white paper is provided for informational purposes.

It is not:

Participation is available only to users who have reached the age of legal majority in their jurisdiction and where participation is lawful.

The Terms and Conditions and applicable settings displayed through the Services govern use of Rando.

21. Official Information

Rando will never ask for a private key or seed phrase.