RTRD

ROBINHOOD CHAIN MAINNET · 4663

THE RULES.
THE RESERVES.
THE RECEIPTS.

Trust the receipts. Not the screenshot.

RTRD connects an ERC-20 token, room NFTs and an independently funded Vault. This page explains where tokens sit, how payments move, what can be burned, and which restrictions the deployed contracts actually enforce.

Contract mechanics reviewed 8 October 2026. Live panels refresh without a wallet connection. Static explanations describe the current deployments—not retired testnet contracts or a proposed allocation.

Three different kinds of statement

Contract rule Enforced by deployed code. Live setting Read from chain; some settings can change. Project policy An intended use of funds, not a transfer restriction. Source verification is not an independent security audit.

01 / Supply & distribution

The verified token uses the symbol RTRD and 18 decimals. The constructor minted 100,000,000,000 RTRD to the initial holder. There is no subsequent mint function, transfer tax, blacklist or project-wide sell restriction in this token contract. Holders can transfer tokens and use burn; burnFrom requires allowance.

Loading verified supply…

totalSupply() already excludes supply-reducing burns. Lifetime burned is MAX_SUPPLY − totalSupply(); never subtract it again. Maximum lifetime issuance, current total supply and circulating supply are different definitions. We do not publish a circulating figure without a documented methodology.

Where the current supply is held

The ledger below reports balanceOf at one block. It is custody—not an immutable allocation pie. Vault and Rooms balances include several internal accounting buckets; these must not be added a second time. PoolManager custody can include other positions or pools involving RTRD and is not the controller’s exact locked principal.

Loading custody ledger…

Verified founder funding was 12 billion RTRD (12% of original issuance), deposited on 7 October 2026. That is a funded allocation, not a token-enforced cap on all future founder funding. Founder funding transaction ↗

02 / What happens to the remaining tokens?

Project policy

Undistributed ecosystem reserves are intended to fund game liquidity, rewards, community distributions and operating needs—not discretionary market sales of the remaining supply. This is a project commitment, not a blanket prohibition enforced by the ERC-20.

There is no automatic rule that burns every unused token or releases all reserves on one date. Allocated rewards, expense funds, founder reserves, room balances and external liquidity have different purposes and withdrawal rules.

  • Project wallet: tokens still held here remain under wallet control; they are not automatically vested or time-locked.
  • Vault reward pool: owner-funded tokens support explicit airdrop allocations and daily claims. Rewards are finite and depend on available funding.
  • Vault expense account: the owner can send these tokens to a destination or withdraw the expense account. This is not a permanently locked reward reserve.
  • Founder treasury: properly deposited allocations are reserved for six fixed founders and released under its vesting schedule.
  • Hood internal pool and bonus reserve: separate game accounting, described below; not shares in the external Uniswap pool.
  • Distributed tokens: claimed rewards, withdrawn room tokens and vested founder tokens can be transferred or sold by recipients. Their later actions are not constrained by a project reserve policy.

No burn projection, price floor or guaranteed demand is implied by these uses. Funding and payouts can move tokens between categories without changing total supply.

03 / Founder vesting

Contract rule The FounderTreasury splits every approved owner deposit between six fixed wallets: 25%, 15%, 10%, 20%, 20%, 10% of that deposit. Those percentages are not shares of the entire token supply.

1% of each allocation vests per completed week for 100 weeks (700 days), measured from treasury deployment. Nothing vests before the first completed week. Missed claims accumulate; claims are not automatic. A registered founder may trigger another founder’s claim, but payment goes to that founder’s fixed wallet.

Loading founder allocations and dates…

Later deposits inherit the original elapsed schedule; they do not receive a fresh 100-week lock. The owner cannot recover allocated founder reserves through recoverSurplus. Accidental direct transfers above the reserved amount are recoverable, and unrelated tokens or ETH have separate recovery paths. Once claimed, founder tokens are ordinary transferable RTRD; there is no post-claim sell lock.

04 / Two pools. Different rules.

External market pool

Uniswap v4’s native ETH/RTRD pool is managed by the PoolManager and guarded by the launch hook. Native ETH is currency0 (zero address); RTRD is currency1. The fee is 0.3%, with tick spacing 60. The pool ID is not a contract address.

The controller owns a full-range native PoolManager position—not a transferable LP NFT. Its principal is locked for 730 days from initial successful funding. There is no admin override of that deadline in the reviewed controller.

Fee collection is separate from principal. After launch protection expires, the owner can collect earned fees; principal withdrawal remains blocked until the principal deadline. After that deadline the owner can remove the controller’s liquidity. This lock does not apply to every future third-party position.

Hood internal game pool

poolEth and poolRtrd are accounting reserves inside Rooms. Game rounds exchange room trading balances against these reserves using the contract’s reserve-ratio calculation. They do not execute each game trade on Uniswap.

There are no internal LP shares or a promise of LP yield. The owner can seed the pool in either asset. While Idle, the owner can withdraw 99% of both internal reserves per call, including while paused. Repeated withdrawals can reduce reserves to dust; this pool does not have the external controller’s 730-day lock.

Room-owned balances, treasury fees, jackpot tokens and fixed bonus reserves are distinct accounting categories. NFT ownership carries its room balances; those are not a share of the internal pool.

Initial external funding: the successful 6 October 2026 transaction supplied approximately 1 ETH and 20 billion RTRD (20% of original issuance) to the controller position. Exact consumed amounts differ by tiny rounding refunds. This historical funding is not a claim about today's pool balance or token price. Verify initial liquidity funding ↗

Loading launch and lock status…

Launch protection: before opensAt(), only approved game contracts can buy RTRD from this particular hooked pool; sells and liquidity removal are gated. At the configured opening, the hook gate expires based on time without an admin opening transaction. The hook owner can change approved games, but not the immutable scheduled opening. Token transfers and other markets are not covered by this gate.

The configured opening is 31 October 2026 at 23:00 UK time (1 November at 00:00 Amsterdam time). This is a hook permission change, not a promise that a particular trading interface will be available or that liquidity or price will stay constant.

Loading internal game reserves…

05 / Follow a payment

All percentages below describe the current reviewed code. Integer rounding is performed in base units. Adjustable prices are read in the apps before payment.

Implemented payment routes
ActionWhere the payment goesBurn?
Mint a room (ETH)25% buys RTRD externally; of the received RTRD, 99% goes to the room’s trading balance and 1% to Rooms treasury. Another 25% ETH funds the internal pool, 10% pays the executor, and the remaining approximately 40% goes to the owner.No immediate burn.
Equipment upgrade paid with new ETH10% treasury ETH; approximately 40% internal pool ETH; 50% buys RTRD externally and immediately burns the received tokens.External buy-and-burn.
Deposit ETH into a room99% credits the room trading balance, 0.5% pays the executor, and the remainder (approximately 0.5%) funds the internal pool. Minimum deposit: 0.001 ETH; the credit must fit the room cap.No immediate burn.
Rename / edit a room (ETH)Half pays the executor; the remainder funds internal pool ETH. The application fee is owner-configurable.No immediate burn.
Equipment upgrade from room balancesUses caged RTRD first, then room ETH at the internal reserve ratio. RTRD payment: 10% treasury, remainder jackpot. ETH payment: 10% treasury, remainder internal pool.No external swap or burn on this route.
Room cosmetic unlock (ETH)5% executor, 5% Rooms treasury, remainder internal pool ETH. Cosmetics do not improve trading scores.No immediate burn.
Vault profile edits / styles (ETH)Half buys external RTRD and burns it immediately; the other half goes to the current Vault owner (odd-wei remainder goes to the owner).External buy-and-burn.

ETH deposits follow the 99% room / 0.5% executor / remainder pool split above. RTRD deposits (minimum 10,000 RTRD) go to the room cage until uncaged. Game round buys credit 99% of gross RTRD output to the room, 0.3% to treasury and the remainder to internal pool accounting. Sells credit up to 99% of gross ETH output to the room, subject to its protected principal/cap rules, with 0.1% treasury and the remainder retained internally.

Round prizes move a configured share of internal RTRD liquidity to a winning room’s cage; a separate, fully funded bonus can be added. Jackpot contributions and payout timing are contract-controlled settings. Neither prizes nor deposits are trading P/L: the displayed matched-round result compares credited ETH sell proceeds with actual ETH spent on the matching buy, after fees. Losses are possible.

06 / The Vault’s four buckets

The Vault is not an interest-bearing loan or an unlimited emissions engine. It separates staked principal + outstanding airdrop allocations + expense account + reward pool. Their sum is reserved RTRD. Direct transfers above those reserves are excess—not automatically donations to the reward pool.

Loading reserve accounting and current reward settings…

The owner can fund rewards and expenses, assign funded airdrops, configure eligibility and daily tiers, change profile prices, and recover unallocated excess. The reserve-aware recovery path cannot withdraw users’ stakes or allocated airdrops as excess. Expense spending is explicitly permitted. The owner’s controls and the continued need for funding are part of the trust model.

Staking is not the airdrop vesting clock

Stake changes are paused during a batched staker allocation. Otherwise sendStaked closes the entire stake and sends its principal to the selected recipient; the airdrop early-exit burn does not apply to stake principal. Eligibility age and daily claim cooldowns are separate conditions, not a guaranteed fixed lock of the principal.

Daily claims require the stake’s holding age (48 hours), a 24-hour claim interval, sufficient reward funding and no allocation run in progress. A top-up restarts the whole stake’s holding age. Missed days do not accrue. Daily rewards go directly to the wallet and do not use the airdrop penalty schedule. Current thresholds and rewards can be reconfigured by the owner; no APR/APY is promised.

Airdrop payout schedule

Allocation withdrawal uses the Vault deployment clock, not the date each allocation was assigned:

Portion of an outstanding allocation paid on withdrawal
Time since deploymentPaidBurned
Before day 3010%90%
Day 30 to before day 12025%75%
Day 120 to before day 24050%50%
Day 240 to before day 36575%25%
Day 365 onward100%0%

Withdrawal clears the entire allocation. The unpaid portion is permanently burned; it is not left to claim later. Rounding remainder is also burned. An allocation left unclaimed is not automatically burned by this schedule.

07 / What actually burns?

  • Token-holder burn: burn destroys the caller’s tokens; burnFrom uses an approved allowance.
  • Vault airdrop withdrawal: destroys the unpaid portion under the deployment-age schedule.
  • Vault paid profile actions: uses half the native ETH payment to buy and immediately burn external RTRD, without spending existing user reserves.
  • Hood new-ETH equipment upgrade: uses half the ETH price for the external buy-and-burn route. Paying from room balances is a different route.
  • Hood internal-liquidity burn: the executor can burn poolRtrd × BurnRate / 10,000 at most once per rolling 23.5 hours, when running, Idle and with no pending jackpot. The owner can set 0–1,000 basis points (0–10%); zero disables it. Missed intervals do not stack and execution is not automatic.

Supply-reducing burns are irreversible for this fixed-supply token. A burn does not guarantee a higher price or a return. A cumulative burn share is not a daily or annual burn rate. Vault burn totals are a subset of all token burns; do not add them to lifetime burned again.

08 / Trust boundaries & risks

A trustworthy explanation includes what administrators can do, not just what is locked.

  • The token does not prevent owner-wallet sales, recipient sales or alternative markets. The launch hook gates only its configured pool.
  • Founder funds vest slowly, but there is no supply-wide founder-funding cap. Late deposits inherit elapsed vesting. Claimed tokens are transferable.
  • External principal is time-locked; fees can be collected after opening. Hood internal liquidity is owner-withdrawable and may shrink.
  • Vault expenses are owner-spendable. Reward tiers, eligibility and profile fees are configurable. Funded rewards are not a guaranteed yield.
  • Rooms owner controls include pricing, caps, executor, pause, metadata, burn rate, prize/bonus settings and treasury withdrawals. Room trading exits require Idle; caged withdrawals are available in any phase. Pausing does not itself block withdrawals, but settlement state still matters.
  • The executor commits game rounds and ordering. Entropy, batching and recovery rules are not a guarantee of manipulation-proof outcomes. Contract verification and local tests are not an independent audit.
  • Contracts, wallet keys, RPCs, indexing, liquidity and market pricing can fail or change. No promise of profit, price support, risk-free staking or permanent liquidity is made here.

09 / Official mainnet contracts

Chain ID 4663 · gas asset ETH · public RPC https://rpc.mainnet.chain.robinhood.com. Always compare full addresses; a matching symbol is not proof of authenticity.

RTRD contract directory
Contract / roleAddress & explorer
RTRD token — fixed issuance, transfers, burns0xb8c596cc5275166899c5e9384BEd667DFeADC5a6 ↗
Rooms — NFTs, internal pool, game balances0x54Eab543A495569ecC9bDff64EBc47187374C773 ↗
RTRD Vault — staking, funded rewards, profiles0xe57a83B578352DFfcd9E306FC328b0C363AA9D56 ↗
Founder treasury — six allocations, weekly vesting0xD00676Cfc56560A54AE7Cabf5e4E291597320778 ↗
Liquidity controller — external position and principal lock0x5cc7DCeB14FBa98c1bDA88300f402bcf60218DB1 ↗
Launch hook — protected pool permissions0x363fBEEE2015a0087Ccdf9b8902797893Be16a80 ↗
Uniswap v4 PoolManager — market pool infrastructure0x8366a39CC670B4001A1121B8F6A443A643e40951 ↗
Recorded project wallet — not a locked contract0x78B79ab513cceb930Ea6eBb439C12bc7221344B7 ↗

Native ETH/RTRD pool ID: 0x7fdeb9bf98ba9c53397d5e9bf820ffe1036ea1435ed584e1e36afb3eb17f69f0

10 / Verify it yourself

  1. Open the exact explorer address and inspect its verified source / Read Contract tab. Verify you are on Robinhood mainnet, not testnet.
  2. Token: compare MAX_SUPPLY, totalSupply, decimals and balanceOf. Inspect Transfer events for funding and burns.
  3. Vault: read getEcosystemStats, getRTRDAccounting, dataFee, payoutPercent, owner and getPlayerStats for your own account.
  4. Founder treasury: compare totalDeposited, totalClaimed, vestingStart, vestingEnd, unlockedWeeks, allocationOf, claimed and claimable.
  5. Controller/hook: compare positionLiquidity, liquidityUnlockAt, liquidityLockDuration, opensAt, protectedLaunch and approvedGames.
  6. Rooms: read getProtocolState, BurnRate, nextLiquidityBurnAt, BonusDropReserve and BonusDropPerRound. Internal reserves are not the external pool’s reserves.

This page signs nothing and never requests token approvals. Each live panel shows its block and update time. Missing reads remain unavailable; old snapshots are marked stale. Documentation can become outdated after settings, funding or ownership changes—current contract state takes precedence.