RED COMRADE Whitepaper
Version 1.1 — Proposed distribution policy — 10 September 2026
RED COMRADE (RCOM) is a founder-managed Solana meme token built around political, economic, and crypto satire. This paper explains the token, its existing controls, and a proposed transition toward wider distribution. The founder’s intended personal allocation is 50 million RCOM, or 5% of launch supply. This is a target allocation, not a claim that the founder currently controls only 5%.
At the snapshot described below, the founder controls five major wallets holding approximately 499.48 million RCOM and the withdrawable Raydium liquidity position. Community and sale allocations remain founder-controlled until transferred. No new distributions, token sales, or vesting contracts are established by publishing this paper.
00 Project identity
| Field | Value |
|---|---|
| Name | RED COMRADE |
| Symbol | RCOM |
| Network | Solana mainnet |
| Token program | Token-2022 |
| Decimals | 9 |
| Launch supply | 1,000,000,000 RCOM |
| Supply at the verification snapshot | 999,964,390.679388630 RCOM |
Canonical mint address
29bFhrwpthoJadSyP6YV28gnxNY48jV1YaMgDcKMAHdH
Always verify the mint address. A name, symbol, image, or social profile can be copied by another token. RCOM is an independent project with no affiliation claimed with any government, political party, public figure, or outside organization.
01 Executive summary
RCOM’s theme is a token for Earthlings: one billion tokens at launch in a world of more than eight billion people. The mismatch is a satirical premise about scarcity and ownership. RCOM has nine decimal places, so a person does not need a whole token to participate.
The token’s mint, freeze, metadata update, and metadata pointer authorities are disabled. Additional RCOM cannot be created through the mint authority. Token holders can still burn tokens, reducing supply. Metadata is fixed on-chain and references IPFS content; website and social content remain editable.
The proposed distribution policy retains 50 million RCOM as the founder’s personal allocation, earmarks 200 million RCOM for community rewards and giveaways, and earmarks approximately 249.48 million RCOM for staged sales. The existing liquidity position remains separate and withdrawable. There is no commitment to sell or distribute every earmarked token by a particular date.
RCOM does not promise appreciation, guaranteed income, a fixed redemption value, or support for its market price. Wider distribution is an objective, not an accomplished result.
02 Purpose and philosophy
RCOM explores meme culture, community identity, scarcity, and ownership through satire. The language of solidarity and collective participation is part of the project’s theme; it does not mean that token holders currently govern the project or own its treasury.
The project is founder-managed. Community participation can inform its direction, but no binding token-holder governance arrangement is represented as active. Important claims about supply, wallet control, distribution, liquidity, and restrictions should be supported by public records.
Solana provides the infrastructure for the token, transfers, and its existing decentralized pool. Transaction costs and service availability vary. Using public blockchain infrastructure does not eliminate operational, custody, or market risk.
03 Token architecture and controls
RCOM launched with one billion tokens. At finalized Solana slot 445796391, the recorded supply was 999,964,390.679388630 RCOM, a reduction of 35,609.320611370 RCOM from launch supply. This is a dated snapshot, not a live supply counter.
| Control | Verified state | Practical effect |
|---|---|---|
| Mint authority | Disabled | No further issuance through this authority |
| Freeze authority | Disabled | No freeze authority can freeze RCOM token accounts |
| Metadata update authority | Disabled | On-chain name, symbol, URI, and metadata fields cannot be updated through this authority |
| Metadata pointer authority | Disabled | The metadata account pointer cannot be changed through this authority |
| Project wallets | Founder-controlled | Tokens held in these wallets remain under founder control |
| Raydium LP position | Founder-controlled and unlocked | The founder retains withdrawal access |
The mint data contains the metadata pointer and token metadata extensions. The verified snapshot does not show a transfer-fee or permanent-delegate extension. This description of observed settings is not a smart-contract audit or a guarantee that every service will support RCOM.
The metadata JSON and its image reference use content-addressed IPFS identifiers. Their content cannot be substituted under the same CID, but files must remain available through pinning and retrieval services. The website uses a cleaned version of the logo; the immutable metadata still references the original image. Explorer and wallet display updates may depend on their own indexing.
04 Proposed allocation and distribution
Version 1.1 proposes replacing v1’s separate treasury, community, reserve, development, and founder budget categories with the following distribution policy. These labels describe intended uses. They do not create separate ownership, escrow, vesting, or a transfer restriction.
Allocation targets
| Intended use | RCOM | Basis and status |
|---|---|---|
| Founder personal allocation | 50,000,000 | 5% of launch supply; no enforced vesting |
| Community rewards and giveaways | 200,000,000 | 20% of launch supply; planned distributions |
| Staged sales | 249,481,739.906972149 | Remaining balance in the five disclosed wallets after the two allocations above; sales terms not yet set |
| RCOM in the existing pool | 499,971,494.537710010 | Snapshot of the pool’s RCOM reserve; not a community distribution |
| Remaining balances outside those wallets and pool | 511,156.234706471 | Residual supply; beneficial ownership not established by this paper |
| Total outstanding supply at snapshot | 999,964,390.679388630 | Excludes burned tokens |
The sale budget is approximately 249.48 million, rather than the earlier illustrative 250 million. The policy uses current balances and avoids allocating more tokens than are available. Pool balances, burns, and transfers can change these figures; reconcile balances before each release.
The 50 million founder allocation equals exactly 5% of launch supply and slightly more than 5% of the reduced outstanding supply. It is separate from any continuing control over undistributed tokens or liquidity.
Current wallet control
The founder has confirmed control of the following owner addresses. Balances were checked at the same finalized slot. The individual addresses have not yet been assigned to the new distribution categories in this paper.
| Owner address | RCOM held directly |
|---|---|
7AspQ289McdVQ2qnzhNDixQoAfme7rAVrhYJHm1YmmWj | 200,000,000 |
5wQNK2L5obkYwYCrtZQZ8Awo88wGMactVCx3adjP2pBK | 100,000,000 |
GeWi26jwxLdcUC6jhNmsMn6mjDvinK1c91fz3Mh1nksD | 90,000,000 |
9Zv2QtxnRKEB56Xb1vQMqBt5EGN7QfDfApTWMVbCgsz3 | 59,481,739.906972149 |
5cyqCtPfqE6Q5wLUZewJrdRdPGezDjfmgM15kFapxzY6 | 50,000,000 |
| Total | 499,481,739.906972149 |
Moving RCOM among these or other founder-controlled wallets does not increase independent ownership. Adding RCOM to the founder’s withdrawable LP position also does not constitute a giveaway. The project should report distributed amounts separately from earmarked, offered-for-sale, and undistributed balances.
05 Liquidity and founder access
RCOM trades through the identified Raydium WSOL–RCOM CPMM pool. At the snapshot, the founder’s wallet 9Zv2QtxnRKEB56Xb1vQMqBt5EGN7QfDfApTWMVbCgsz3 held 50,382.049067430 LP tokens, equal to the current issued LP token supply checked for that pool.
The project retains withdrawal control. The position is not represented as permanently locked or burned. Withdrawing liquidity returns a proportional share of the underlying assets under the pool’s rules; it does not guarantee recovery of the original SOL amount. Trading changes reserve composition. Removing substantial liquidity can impair trading and increase price impact.
The founder’s planned 5% personal allocation is therefore not a 5% cap on total effective control. While the founder retains the LP position and undistributed allocations, those must be disclosed separately. The pool’s roughly 50% token reserve must not be advertised as tokens already distributed to independent holders.
The earlier proposal for 24-month founder vesting has not been implemented and is not a commitment in this version. The founder’s personal allocation is unvested and can be transferred. Any future vesting arrangement would require separately defined terms, funding, and a verifiable contract before being described as active.
06 Community distribution and staged sales
Community allocation
The proposed 200 million RCOM community budget can support giveaways, rewards, grants, and contributions to the project. It is a budget ceiling, not an announced giveaway or a promise of individual entitlement.
Before each program, publish the amount, eligibility rules, selection method, per-recipient limits, relevant dates, and distribution method. Start with a bounded release and review participation before committing to additional rounds. Design limits to discourage duplicate claims without representing wallet counts as counts of unique people.
Publish distribution transaction references and remaining budget totals. Disclose any recipients controlled by or affiliated with the founder. Do not manufacture volume, holder counts, endorsements, or engagement to suggest demand that does not exist.
Sale allocation
Approximately 249.48 million RCOM is earmarked for possible staged sales. No price, sale date, venue, batch size, or fundraising target is established by this paper. The balance remains founder-controlled until sold or otherwise allocated through a disclosed policy change.
Before offering a tranche, publish its token amount, price or pricing method, eligibility, timing, fees, custody or settlement method, and intended use of proceeds. Identify who receives and controls the proceeds and distinguish personal compensation from project spending. Review applicable requirements for the actual sale structure and participants before launch.
Selling a large tranche directly into the existing small pool could substantially reduce its SOL reserves and depress the price. A sale budget does not imply that the pool can absorb it. Sale terms should account for market depth rather than treating the full allocation as immediately saleable at a displayed price.
Potential utility and participation
RCOM begins as a meme token. Tipping, creative rewards, community grants, polls, and optional experiences may be explored where there is actual demand. These are possible uses, not delivered features or guaranteed benefits. Token ownership does not itself confer binding project governance, a claim on sale proceeds, or a right to withdraw project liquidity.
07 Roadmap and current status
| Area | Status at this revision |
|---|---|
| Token launch and mint authority revocation | Completed |
| Freeze and metadata authority settings | Verified disabled |
| IPFS metadata | On-chain URI updated; content remains dependent on availability |
| Website and public contact | Published |
| Raydium liquidity | Existing position; founder retains withdrawal access |
| Mixed community and sales plan | Proposed in this revision; no new transfers executed by drafting it |
| Founder vesting | Not implemented; no vesting commitment in this version |
| Program rules and sale terms | To be defined before each release |
| Independent governance and additional utility | Not represented as active |
The next operational steps are to designate the founder and distribution wallets, reconcile balances, publish the adopted policy, and define the first bounded community program. Sale preparation is separate from a community giveaway and requires its own terms. Future releases should be documented with amounts, transaction references, remaining balances, and any material changes in control.
The roadmap is directional. It does not promise returns, exchange acceptance, completion dates, or the implementation of every potential feature.
08 Risks and disclosures
Market and liquidity risk. RCOM may lose some or all value. A small pool can experience substantial slippage and price changes. The founder can withdraw the current liquidity position. Access to withdrawal does not protect the founder or holders from trading losses or changes in reserve composition.
Concentration and governance risk. The founder currently controls the major disclosed wallets and the LP position. The proposed distribution plan does not remove this concentration until actual ownership or control changes. Founder-controlled tokens can be transferred or sold, including the unvested personal allocation.
Contract and network risk. Solana, Token-2022, Raydium, wallets, and other infrastructure can fail, be exploited, or become unavailable. The authority checks in this paper do not constitute a security audit.
Operational and metadata risk. Key loss, compromised accounts, incorrect transfers, and poor custody practices can cause loss. The immutable on-chain metadata cannot be corrected later. IPFS availability requires ongoing pinning, while website hosting, email, and social services have separate availability and account risks.
Distribution and regulatory risk. Giveaways and sales can face eligibility, tax, consumer-protection, promotion, and other requirements that depend on their structure and jurisdiction. Duplicate claims, unfair selection, or unclear sale terms can harm participants and the project.
Narrative and impersonation risk. Interest in a meme token can disappear. Anyone can copy branding or the ticker. Verify the canonical mint and official links, and never disclose a seed phrase or private key to claim tokens or receive support.
This paper describes the project and a proposed distribution policy. It does not establish a sale, fixed redemption obligation, guaranteed yield, or promised investment return. Participants should assess the relevant facts and risks before transacting.
09 Transparency and references
Allocation intentions, actual transfers, wallet balances, and control restrictions should be reported as separate facts. Public updates should disclose material founder or project sales, withdrawals, changes in spending policy, and revisions to release plans. Do not describe an unimplemented restriction as vesting or a planned distribution as completed circulation.
| Reference | Location |
|---|---|
| Project website | RED COMRADE website |
| Project updates | COMRADE COIN on X |
| Contact | redcomrade.contact@gmail.com |
| Token and supply | RCOM on Solscan |
| Holder information | RCOM holders |
| Raydium pool | WSOL RCOM pool |
| LP token | RCOM pool LP token |
| Metadata JSON | IPFS metadata through gateway |
| Original metadata image | IPFS image through gateway |
| Authority mechanics | Solana token authority documentation |
| Metadata mechanics | Solana metadata extensions |
| Pool mechanics | Raydium CPMM documentation |
Metadata URI
ipfs://bafkreicxg2up3spwti53buithsn52ypgvwcqiyrdpvaqtvnprd72nyvfky
Image URI stored in the metadata
ipfs://bafybeihwomsielim2p4srb6m6m55ncv77exx6g77vqqjzk3qv5ycavldvm
Technical balances and controls in this revision refer to finalized Solana slot 445796391, checked on 10 September 2026. Wallet-control attribution is based on the founder’s disclosure; blockchain balances alone do not establish beneficial ownership. Consult current chain records for later changes.
Changes from version 1
This revision introduces the proposed personal, community, and staged-sale allocation policy; distinguishes launch supply from outstanding supply; documents immutable metadata and updated public references; explicitly discloses founder control and unlocked liquidity; and removes the unimplemented 24-month founder vesting commitment. It also distinguishes planned releases from actual circulation and explains fractional token ownership.