The RUGRIOT thesis
An informed community is a stronger community.
Crypto makes it possible for communities to form around shared ideas at extraordinary speed. That openness also exposes people to opaque token launches, misleading promises, concentrated holdings and complicated on-chain activity. New participants often discover critical warning signs only after money has changed hands.
RUGRIOT was created in response to that frustration. It combines an expressive community identity with a practical goal: make blockchain research easier to understand, easier to verify and harder to confuse with unsupported opinion.
The RUGRIOT token exists on Solana. The planned RUGRIOT Scan service is a separate research application that will analyze public blockchain data. Token holdings are intended to determine access to progressively advanced scanner capabilities; time-limited paid access is also being considered. These proposed services are not yet guaranteed or fully deployed.
What RUGRIOT is
- A Solana-based community token with a planned connection to research-tool access.
- An education and on-chain risk-awareness initiative.
- A developing read-only scanner and a framework for evidence-backed community research.
What RUGRIOT is not
- A new blockchain, mining protocol, validator network or replacement for Solana.
- A promise that any token, wallet or project can be definitively labeled safe or fraudulent.
- A guarantee of financial returns, liquidity, product delivery or privileged token-holder profits.
Core facts
| Network | Solana |
| Token | RUGRIOT (RUGRIOT) |
| Mint address | EWuKfiF8mQFo4YWtKbALzyFtYMhxePjs1HJ4eCG9pump |
| Project website | rugriot.com.co |
| Launch platform | Pump.fun, October 2026 |
01The problem RUGRIOT addresses
Public blockchain data is open, but openness is not the same as clarity. A wallet address, mint authority, token holder list or liquidity transaction means little without context. Existing explorers often require a reader to connect information across separate pages, understand technical details and avoid jumping to conclusions from isolated signals.
Four recurring challenges
| Challenge | Why it matters |
|---|---|
| Information asymmetry | Experienced participants can act on signals that newcomers struggle to interpret. |
| Fragmented evidence | Supply, holders, liquidity, locks and connected wallets are often inspected in separate tools. |
| Unverified claims | Labels such as “locked,” “burned” or “safe” are easily repeated without proof or a timestamp. |
| Reactive education | Warnings frequently arrive only after a dramatic price or liquidity event. |
02Principles and product boundaries
- Verify what can be verified. Source facts should link to public transactions, accounts or reproducible provider data.
- Separate facts from hypotheses. A signal or wallet relationship is not proof of intent.
- Show uncertainty. Missing, stale or conflicting information must be visible.
- Read-only first. A token scan never needs a user’s seed phrase or permission to move funds.
- Correct the record. Community research must support review, appeals and corrections.
These principles form both the scanner’s design requirements and the standard RUGRIOT wants its own disclosures to meet. The goal is better-informed judgment, not automated certainty.
03Network and token design
RUGRIOT is a token issued on the Solana network, not a standalone cryptocurrency protocol. Its transfers, token-account state and settlement use Solana infrastructure. Unlike Litecoin, RUGRIOT does not operate independent proof-of-work mining, coin issuance through block rewards or its own consensus rules.
| Attribute | RUGRIOT design |
|---|---|
| Underlying network | Solana |
| Token identity | Mint: EWuKfiF8mQFo4YWtKbALzyFtYMhxePjs1HJ4eCG9pump |
| Origin | Pump.fun launch |
| Primary present role | Community and meme token |
| Intended application role | Eligibility credential for RUGRIOT Scan access tiers |
| Transfer and custody | Managed by users and supported wallets under Solana token rules |
Token rights and service access
A RUGRIOT holding does not by itself confer ownership of the scanner, equity in a business, voting control, a share of service fees or a claim on project revenue. The planned access model is a product policy, not a transfer of governance or financial rights. Any live terms must specify the current tier thresholds, qualifying balances, usage limits and service availability.
Chain state versus project policy
The blockchain records token balances and transactions. It does not automatically determine which off-chain research features a holder can use. Access checks, paid-pass issuance, rate limits, customer support and software updates would be implemented by the scanner service. This distinction matters: an on-chain balance may be independently visible, but a product-access decision depends on the published service rules.
A second coin: $RiotDegen
On November 11, 2026 the RUGRIOT team launched a second token, RUGRIOT Degen ($RiotDegen), on pump.fun from the published Project Treasury wallet. It runs alongside RUGRIOT rather than replacing it. It uses pump.fun's own fee system: part of each trade's fee goes to $RiotDegen holders, paid in RUGRIOT through pump.fun's holder rewards program, and the creator's share is swapped for RUGRIOT and added to the RUGRIOT staking pool.
| Attribute | $RiotDegen design |
|---|---|
| Underlying network | Solana (Token-2022 program) |
| Token identity | Mint: 32tfZ7z9fwLEv2ReyjpmMqH4MuFTpjACBCEaP8VLpump |
| Origin | Pump.fun launch, November 11, 2026, from the Project Treasury wallet |
| Mint and freeze authority | Both off: no new tokens can be created and no holder can be frozen |
| Fees | Pump.fun's fee system; holder rewards paid in RUGRIOT by pump.fun; the creator share is swapped for RUGRIOT for the staking pool |
| Membership role | Counts toward member tiers by dollar value, added to RUGRIOT holdings |
Like RUGRIOT, a $RiotDegen holding confers no ownership, equity, voting control or claim on project revenue. Holder rewards are paid by pump.fun under its own rules, which RUGRIOT does not control and which can change. RUGRIOT staking and the holder leaderboard count RUGRIOT only.
04Membership and scanner-access economy
RUGRIOT has four membership tiers, based on the dollar value of the RUGRIOT and $RiotDegen held in a member’s linked wallets, added together. Higher tiers unlock progressively deeper RUGRIOT Scan tools, and a paid option is planned for users who cannot or do not wish to hold the token.
Four practical utility pillars
- Tiered research access: token holdings determine eligibility for progressively richer RUGRIOT Scan tools.
- Information advantages, not trading promises: higher tiers are intended to provide deeper reports, research resources and alerts.
- Community participation: the membership program describes educational resources, forums, early features and selected giveaway eligibility.
- Flexible use: a planned subscription could offer scanner access without holding the token.
| Tier | RUGRIOT held (USD value) | What it includes today |
|---|---|---|
| Bronze | $0.01 – $100 | The RUGRIOT app and full scanner for any token; live charts, smart money and wallet alerts; community forums, profile and badge |
| Silver | $100.01 – $500 | Everything in Bronze, plus a watchlist with in-app alerts, scan history with PDF reports, and the Silver forum and badge |
| Gold | $500.01 – $1,000 | Everything in Silver, plus new lock alerts on your phone, funding traces and the Wallet Graph, and the Gold forum and badge |
| Diamond | $1,000+ | Everything in Gold, plus the private Diamond forum, the animated Diamond badge and a place at the top of the holder leaderboard |
| Subscription (planned) | No holding needed | Possible paid scanner access for people who don’t hold RUGRIOT; not launched |
Tiers are worked out automatically from the dollar value of the RUGRIOT and $RiotDegen in a member’s linked public wallets, at the current market price, and kept up to date; the dollar thresholds may be adjusted over time. The perks listed are the ones working today; more are planned. Subscription prices and what a subscription includes have not been set.
How eligibility could be checked
- A user supplies a public wallet address or voluntarily proves control through a narrowly scoped message signature.
- The service checks a relevant RUGRIOT balance and applies its published eligibility rule.
- A time-limited session is granted with feature permissions and reasonable usage limits.
- Access may be rechecked; no seed phrase, private key or token transfer is required for a read-only scan.
Why keep a non-holder route?
Research should remain approachable. An occasional user may need a single investigation and may not want market exposure merely to run it. Timed passes could serve that need, while holder tiers provide a separate path for regular users. Neither model should be represented as supporting token price or creating investment returns.
05RUGRIOT Scan: research workflow
RUGRIOT Scan is envisioned as a read-only Solana research terminal. It will translate selected blockchain observations into a report that lets a reader inspect the evidence behind an assessment. The scanner is still in testing and development; the descriptions below specify its intended methodology, not a claim that each feature is production-ready.
| Stage | Intended operation |
|---|---|
| 1. Identify | Validate the token mint or account under review and collect a dated chain snapshot. |
| 2. Observe | Retrieve token authorities, supply data, holder distribution, lock records and relevant liquidity or wallet activity. |
| 3. Correlate | Compare signals across transactions, accounts, addresses and known documented patterns. |
| 4. Explain | Separate raw observations from tentative interpretations and known data gaps. |
| 5. Report | Provide time-stamped findings, direct sources and confidence or completeness labels. |
Evidence levels
| Label | Meaning |
|---|---|
| Verified observation | A specific fact supported by an accessible primary record or independently checked result. |
| Possible risk | A pattern worthy of further investigation, not proof of wrongdoing. |
| Unknown / incomplete | Insufficient, stale or contradictory information; the tool should abstain from a definitive claim. |
A risk summary is not a safety certificate. A token can change after scanning, providers can fail and wallet ownership may be impossible to determine with certainty. Reports should preserve timestamps, data provenance and limitations so readers know exactly what was examined.
06Community learning and Rug Hunters
Education is part of the product, not an afterthought. The wider vision includes practical explainers, an accessible knowledge base, community discussion and evidence-backed investigations. The community-facing Rug Hunters concept encourages contributors to document suspicious patterns responsibly, with review processes that protect against unsupported accusations.
A responsible case record
- Token mint, relevant public accounts, transaction signatures and source links.
- A concise claim, the observations that support it and reasonable alternative explanations.
- Research date, reviewer outcome, confidence, unresolved questions and corrections.
- No personal addresses, real-world identity speculation, harassment or coordinated targeting.
Community contributions should not automatically become scanner verdicts. Human review and an accountable correction process are necessary when a case is sensitive, contested or incomplete.
07Token locks and long-term commitments
Long-term locking is a visible part of RUGRIOT’s approach to founder accountability. As displayed on the project’s token-lock page on October 28, 2026, the launch supply baseline is 1 billion tokens and the project reports 568,201,789 RUGRIOT in active locks across eight contracts, with ten total receipts including two completed unlocks. These are project-reported figures with linked Streamflow receipts, not an independent audit of current escrow state or circulating supply.
| Project-reported active lock | Condition or timing |
|---|---|
| 270M founder-controlled | October 8, 2027; two time-based receipts (200M + 70M) |
| 20M founder-controlled | January 17, 2027 time-based unlock |
| 30M founder-controlled | $157K FDV price trigger ($0.000157) or December 1, 2026, whichever comes first; relocked from Receipt 09 |
| 40M founder-controlled | $200K FDV price trigger |
| 10M founder-controlled | $313K FDV price trigger |
| 168,201,789 founder-controlled | $200M FDV price trigger |
| 30M community-reported | April 12, 2027; community ownership not independently confirmed |
The website reports 538,201,789 founder-controlled tokens and 30M in a community-reported lock. Two completed receipts are not included above: 17M tied to $100K FDV (unlocked and claimed October 14, 2026) and 40M tied to $104K FDV (unlocked and claimed October 25, 2026). Live status, receipt details and any later changes should be checked at rugriot.com.co/holders.
A lock restricts access under its specific contract terms. It does not guarantee market liquidity, prevent all sales by unrelated holders, or prove that any future relock has occurred.
08Milestone goals and relocking strategy
RUGRIOT’s published milestone plan links token allocations to measurable events and intended community outcomes. These plans explain proposed use of unlocked tokens; they are not automatic on-chain executions or guarantees that funds will be sufficient for every objective.
| Milestone | Published intention |
|---|---|
| $100K FDV — reached Oct 14, 2026 | 17M tokens released: 10M intended for community giveaways/contests and 7M for development. |
| $200K FDV — 40M locked allocation | 10M gradual founder investment recovery; 20M relocked for 12 months; 5M development; 5M community rewards. |
| $313K FDV — 10M recovery milestone | Give all 10M tokens to one verified scam or rug-pull victim, with evidence review and privacy safeguards. |
| Oct 8, 2027 — 270M unlock | Begin a proposed three-year founder, development and recovery allocation plan. |
Proposed use of the October 2027 allocation
| Amount | Three-year intention |
|---|---|
| 120M | Long-term founder reserve; relock for a further 24 months. |
| 60M | Founder compensation made available gradually over 36 months, with sales disclosed. |
| 60M | RUGRIOT Scan, website, infrastructure and operating costs. |
| 30M | Recovery support: target 2.5M tokens per quarter for one verified victim, aiming to assist 12 recipients over three years. |
Recovery awards should protect recipients’ privacy and use informed consent for any public presentation. Tokens are speculative and their cash value is not fixed. Planned allocations, relocks, gradual releases and assistance programs remain subject to implementation and public evidence when executed.
What success should look like beyond price milestones
- A scanner that returns accurate, sourced and understandable risk observations.
- A publicly documented lock history and transparent use of released allocations.
- Accessible education and a carefully reviewed Rug Hunters case library.
- Sustainable operations, responsible member access and meaningful support for scam victims.
09Security, privacy and responsible operation
Read-only interaction
Researching a token should not require connecting a wallet. If wallet verification is later introduced for tier access, it should be limited to proving control of an address without requesting private keys or approvals to transfer assets. Any optional signature flow must have a clear message and security review.
Infrastructure and data quality
API credentials should remain server-side; inputs should be validated; requests should be rate-limited; and service errors should not be misrepresented as clean results. A reliable report should distinguish direct chain observations from provider-derived estimates, show source freshness and explain when a lookup cannot be completed.
Research safeguards
Wallet clustering, developer history and alleged suspicious patterns require special care. A shared funding source does not prove common beneficial ownership. A cluster hypothesis is not a legal finding. Published case material should include reproducible links, uncertainty and an accessible correction channel.
10Development path
| Workstream | Release objective | Current position |
|---|---|---|
| Technical foundation | Stable read-only server, protected provider access and meaningful error states | Prototype/testing |
| Core research | Accurate token, holder, authority, supply and lock observations | Validation in progress |
| Investigations | Wallet relationships, historical context and curated cases | Planned |
| User experience | Accessible terminal, mobile layouts and exportable sourced reports | Development/design |
| Public deployment | Independent technical/security review, policies and supported access tiers | Not launched |
Roadmap phases are directional and depend on validation, security review, providers and resources. They are not delivery promises.
11Stewardship and sustainability
RUGRIOT is currently founder-led, with community members able to contribute ideas, education and research. It is not presented as a decentralized autonomous organization or as a token-voting governance system. Decisions about software releases, case review, moderation and project-controlled resources rest with the project operators unless a different framework is publicly established.
Potential service fees would support an application model, but no fee amount, allocation of proceeds or token-holder revenue entitlement is established here. Any community bounty or other incentive should have separate published terms, eligibility and fulfillment conditions.
Potential future mechanisms — TBD
Token buybacks, token burns and staking have been discussed as possibilities but are not adopted programs. No buyback source, burn formula, staking contract, reward rate, yield, launch date or funding commitment is established. Any later proposal would require published economics, technical and security review, legal assessment and clear community disclosure before implementation. This paper does not imply that such mechanisms will launch or increase token demand or value.
How the project should earn trust
- Publish precise product status: live, beta, experimental or planned.
- Disclose material token and treasury information with dated evidence.
- Provide clear feature access and payment terms before charging users.
- Correct wrong claims and document meaningful changes.
- Invite independent review without representing a community opinion as an audit.
12Risks and limitations
- Market: RUGRIOT can experience extreme volatility, low liquidity or a total loss of value.
- Execution: scanner tools, access tiers and paid passes may be changed, delayed or never launched.
- Technical: bugs, exploits, data-provider failures and inaccurate interpretation can affect outputs.
- Attribution: public addresses and transactions rarely establish a person’s motives or identity on their own.
- Regulatory: laws, platform requirements and token treatment may evolve across jurisdictions.
13References and verification
- RUGRIOT project: https://rugriot.com.co
- RUGRIOT milestone roadmap: https://rugriot.com.co/roadmap
- Live lock records and relocking plans: https://rugriot.com.co/holders
- RUGRIOT token: https://pump.fun/coin/EWuKfiF8mQFo4YWtKbALzyFtYMhxePjs1HJ4eCG9pump
- Solana token model: https://solana.com/docs/tokens
- Litecoin project and source: https://litecoin.org/ and https://github.com/litecoin-project/litecoin
- Dogecoin community principles: https://dogecoin.com/ and https://foundation.dogecoin.com/manifesto/
Litecoin and Dogecoin are referenced as established examples of clear technical identity and community purpose. RUGRIOT is independent of both projects and does not claim their network properties, governance, reputation or endorsement.
Important risk and information notice
This paper is an informational description of RUGRIOT, its reported lock arrangements and its development intentions. It is not financial, investment, legal or tax advice, and it is not a promise of token value, profit, liquidity, listing or future services. Digital tokens are speculative and can lose all value.
RUGRIOT Scan remains under development. Membership categories do not establish that particular scanner tools are operational. Time-limited paid passes and future feature allocations are proposals. Buybacks, burns and staking are only possibilities under consideration, with no defined implementation or return. Research outputs may be wrong, incomplete or outdated and must not be treated as proof of fraud or safety.
Lock totals and milestone figures are based on dated public project disclosures and may have changed; review each Streamflow receipt and current on-chain data. Future relocks, sales, development budgets and recovery awards are intentions, not completed transactions or fixed-value promises. Nothing in this paper confers ownership, profit-sharing, redemption or revenue rights.