Retail does not want
a portfolio.
It wants to stop being wrong.

The dominant retail failure in this market is not lack of conviction. It is concentration plus regret. A retail buyer picks one asset, watches four others run, sells into the rotation, and repeats. Every measurable behaviour in the category follows from that loop: the churn, the chasing, the short holding periods.

Diversification is the textbook answer and retail refuses it, for a reason that is rational rather than stupid. Ten positions means ten sourcing decisions, ten swaps, ten fee events, ten tax lots, and ten things to watch. The cost is not financial. It is attention.

REBASE collapses that to one buy. You hold one token, and what you accumulate is a basket. The mechanism does the sourcing, the swapping, and the delivery. The user does none of it and cannot forget to.

The part we did not expect to matter as much as it does: picking is free, reversible, and unlimited. It costs nothing and moves no tokens. That turns a passive holding into a thing you come back and touch, which is the scarcest property a token can have.

Every REBASE trade is also a distribution. The tax conversion and the pro-rata push to holders execute inside the buyer's own transaction, so the buyer pays the gas for everyone's payout. In the 24 hours before this was written (6 September 2026), the median trade cost $0.056 in gas and delivered 24 separate holder payouts across the basket, about $0.0017 each. The same 2.6 million gas transaction on Ethereum mainnet costs $0.35 at today's unusually quiet gas price and roughly $32 at an ordinary 5 gwei, which is more than the entire reward on a $50 trade. On Base the buyer funds two dozen people's rewards without noticing. On L1 nobody trades. That is the whole design constraint, and the numbers are on Basescan.

More than one L2 clears that bar, and Robinhood Chain is the credible alternative: it pairs a retail on-ramp with a native tokenized equity and ETF layer, and for a basket that only held equities it would be the better venue. We would rather name that than have you name it for us. Three things keep this on Base:

The menu. The basket is only as interesting as what holders can put in it. Base has the memecoin surface, the Clanker, Virtuals and Bankr ecosystems, and a growing tokenized equity and RWA layer, all routable from one place. Robinhood Chain has the equity layer and not the rest, and a basket that cannot hold community tokens cannot run the acquisition loop in the next section.

The flow goes into Base. 3% of every trade is automated buying of ten Base-native assets, chosen by their own communities. REBASE converts memecoin churn into distributed buy pressure across the Base long tail. If your portfolio is Base assets, this is infrastructure pointed at it.

The rails are on-chain and controller-held. REBASE launched through BaseStonk's launcher. The token, the rewards distributor and the fee hook are plain, immutable contracts: no proxies, no upgrade path, no admin key over the pool. Distribution executes inside every transfer, the basket seat is held by our controller key, and none of it needs BaseStonk's site or API to keep running. Two bounded platform powers remain in the verified source and belong in your diligence: the platform admin can re-cut the fee payee wedges (not the tax rate, burn or liquidity), and can mark addresses exempt from rewards. It cannot stop distributions, change the 5% tax, or touch the basket seat. A second chain is a fresh launch, not a redeploy.

Coinbase as the terminating on-ramp and smart wallet removing the seed phrase from the funnel both matter, and both have equivalents on Robinhood Chain. We list them as table stakes, not as the reason.

The thing worth underwriting is not the token. It is the acquisition loop.

Any token community can coordinate to get their asset into the REBASE basket. Weight is a function of aggregate picks, and picks are weighted by balance, so a community that wants reward flow directed at their token has one path: acquire $REBASE and pick.

That inverts the usual customer acquisition cost. Instead of REBASE marketing to communities, communities market REBASE to themselves, because their incentive to do it is mechanical and their reward for succeeding is visible on-chain within 30 minutes. Every basket cycle produces a public leaderboard of who is winning, which is the content.

The site already surfaces this: a live panel showing which ecosystem assets are ranked just outside the top ten, and by how much. That is a coordination target rendered as a number. It is the highest-intent screen on the site.

The honest version of this: the loop is reflexive in both directions and it concentrates influence in whoever holds the most. We treat that as a property to disclose and design around, not one to hide. See the diligence section.

1% of every trade is a platform fee. It is contract-level, volume-linked, and does not depend on anyone claiming, staking, or opting into anything. It accrues from the first trade and it does not require a subsequent product to monetize.

We want to be precise about stage. $REBASE has been live and trading on Base since 31 August 2026. The homepage live section shows price, volume, holders and cumulative payouts, all read from chain and market data. We are not going to restate those numbers here because they would be stale by the time you read this, and we are not going to draw a curve through a few days of data and call it a trend.

What we would ask you to underwrite instead is whether the mechanism produces the trading volume it needs, because volume is the only input. Rewards, revenue, and the acquisition loop are all downstream of it.

REBASE is one token. The interesting object is the pattern underneath it: a tax-funded, holder-directed reward basket that any community can instantiate.

The primitive is a rewards contract plus a routed quote gate plus an epoch-based aggregation of balance-weighted preferences. None of that is specific to our token, our basket, or our community. If the mechanism works once, the same machinery issues it as a service.

We are not raising against that. We are telling you it is there because it is the reason the ceiling is not one memecoin.

REBASE has no commercial, advisory, or corporate relationship with ALT5 Sigma Corporation or World Liberty Financial. Any relationship that arises will be disclosed on this page at signature and not before. We reference both here as public-record precedent about the market, and for no other purpose.

What the precedent establishes: the structural question of whether US-regulated, publicly reporting entities can hold and operate around digital assets in the open, with disclosed governance and audited financials, has moved from open to settled in the space of roughly two years. A Nasdaq-listed operating company can build a token treasury, disclose it in its filings, and continue trading. Regulated digital asset trading and payments entities operate under FinCEN money services business registration and state money transmitter licensing, and that perimeter is now well-mapped rather than theoretical.

What the precedent does not establish, and we want to be direct about this because the opposite claim is common in this category and it is not true: none of it is a safe harbour for REBASE. A regulated entity holding a token says nothing about whether a reward-bearing, tax-funded token is itself a regulated instrument. Those are different questions with different answers, and the second one is ours to answer.

The reason it matters to an investor is narrower and more useful. It means the counterparties REBASE will eventually need - regulated execution venues, tokenized asset issuers, custody, banking - now exist as licensed businesses with public compliance postures, rather than as offshore entities. The infrastructure risk in this category has genuinely fallen. The securities-classification risk has not.

Everything in this section is drawn from public filings and public reporting and should be re-verified against current sources before you rely on it.

This is the section most tokens do not write. We would rather you read our version of it than assemble it yourself and assume the worst. The retail-facing versions of these disclosures are in the docs, under Regulatory posture and Risks.

The central question: is $REBASE a security? We do not claim it is not. The honest answer is that a reward-bearing token sits in contested territory in every major jurisdiction, and any project telling you otherwise is telling you about their marketing rather than their law.

The facts that cut toward no: the protocol is non-custodial and never holds user assets. There is no pooling, no account, and no obligation owed by any person. Distribution is mechanical, triggered by trade events, with no human discretion over who is paid or how much. There is no promised rate, no accrual, and no floor. The basket is selected by holders, not by the team.

Status caveat. Holder-directed rebuilds are live but gated by a participation floor of eight voting wallets, which has not been met. The one rebuild so far (1 September 2026) was computed from a single voter's picks, the team's, before the floor existed. Until the floor is met, the holder-directed facts above describe the design more than the record.

The facts that cut toward yes, and these are real: the controller seat can rebuild the basket outside the epoch, which is managerial capability held by an identifiable party. The marketing allocation funds promotion of the token from trade proceeds. The reward flow is presented as a reason to hold, which is an expectation of profit however carefully it is worded. A team built the mechanism and continues to operate the front end.

The mitigation path is the controller seat. Renouncement is on-chain, permanent, and publicly verifiable, and it is the single strongest available move toward the sufficient-decentralization argument. It also permanently removes the ability to repair a broken basket. That tradeoff is the most consequential open decision in the project and we would expect you to have a view on the timing.

Tokenized equity and ETF exposure. This is the sharpest specific risk, sharper than the base classification question, and it deserves separate attention.

When a basket slot holds a tokenized equity or ETF instrument, the reward mechanism delivers that instrument to every holder automatically, pro-rata, without KYC, to a pseudonymous and global holder base. Depending on the instrument and the recipient's jurisdiction, that pattern implicates registration, distribution, broker-dealer, and transfer restrictions that attach to the underlying instrument and are not cured by the delivery being automatic. REBASE does not issue these instruments and cannot fix a defect in them. The controls available are at the eligibility layer: the routed quote gate determines what can enter a basket at all, and it is the correct place to apply jurisdictional and instrument-level restrictions. We regard the current gate as necessary and not yet sufficient for this specific category, and we would treat tightening it as a launch-blocking item rather than a roadmap item.

Money transmission. The protocol does not take custody, does not hold fiat, and does not sit between a payer and a payee. Users transact against a contract from their own wallet. This is the cleanest area of the analysis and we do not think it is close.

Sanctions and screening. Rewards are pushed to holder addresses automatically. Once the controller is renounced, no party can prevent a distribution to a screened address, because no party retains that power. Front-end screening is available and meaningful, and it does not reach the contract. This is an unresolved tension between the decentralization argument and the sanctions posture, and it is inherent to push-distribution designs rather than specific to ours.

Market conduct. Balance-weighted basket steering means a large holder can direct reward purchases toward an asset they already hold, and profit from the resulting flow. We disclose this on the public site in those words. It is a foreseeable use of the mechanism rather than an exploit, and it is disclosed as such, but a regulator assessing it under a manipulation framework rather than a governance framework would reach a different conclusion than we do.

Consumer protection and disclosure. Every risk in this section appears on the public site in retail-readable language, not only here. The footer disclaimer, the docs risk section, and the reward substitution notice on individual payout rows all exist so that a user learns the failure modes from us rather than from a loss.

Offering posture. Nothing on this site is an offer, a solicitation, or advice.

What we have not solved. Counsel opinion on the classification question is jurisdiction-by-jurisdiction and none of it is a clean yes. Sanctions screening cannot survive controller renouncement. The tokenized instrument category needs a tighter gate than we have today. And the market conduct exposure from balance-weighted steering is disclosed rather than mitigated, because mitigating it would mean abandoning the mechanism.

We would rather show you this list than have you find it.

Live on Base since 31 August 2026. The token trades on Uniswap, the rewards contract pays holders on-chain, and every figure in the homepage live section is read from chain and market data. The app holds the controller key and broadcasts holder-driven rebuilds at a daily check or after 30 saves, once at least eight wallets have voted. Seven have so far, and the one rebuild to date (1 September 2026) was computed from a single voter's picks before the floor existed. Picks are weighted by real REBASE balances.

If you want the contracts or the aggregation code behind the steering loop, ask.