1. Index objective
The MEME500 Index (“the Index”) is designed to represent the performance of the memecoin segment of Robinhood Chain. The Index is rules-based, capped-weight, and reconstituted monthly. It seeks broad exposure to the segment rather than selection of individual outperformers.
The Index does not seek to hold five hundred constituents. The name reflects an aspiration, a benchmark it is parodying, and the committee’s confidence in the segment’s capacity to produce assets.
2. Universe definition
The eligible universe consists of all fungible tokens that satisfy all of the following:
- Native to Robinhood Chain. The token’s canonical contract is deployed on Robinhood Chain (Chain ID 4663). Bridged or wrapped representations of tokens native to other chains are excluded.
- Memecoin classification. The token has no utility that the committee is prepared to take seriously. Tokens with a functioning product, protocol revenue, or a governance role in a live system are excluded. Borderline cases are resolved by the committee and published.
- Liquid on-chain market. The token has at least one on-chain pool against ETH or a major stablecoin.
3. Eligibility criteria
At each Rebalance Day, a universe token is eligible for inclusion if it meets every criterion below. Thresholds are illustrative and are replaced by launch parameters.
| Criterion | Illustrative threshold | Rationale |
|---|---|---|
| Minimum pool liquidity | ≥ 5 ETH equivalent | Treasury must be able to buy without moving the market unreasonably |
| Minimum token age | ≥ 14 days since pool creation | Filters same-day launches and most immediate rugs |
| Contract status | Ownership renounced, or verified with no mint/pause/blacklist functions | No privileged party can alter supply or freeze holders |
| Transfer taxes | None | Tax-on-transfer tokens distort execution and NAV accounting |
| Holder concentration | Top 10 non-pool holders < 40% of supply | Reduces single-actor exit risk |
| Trading continuity | Traded on at least 10 of the prior 14 days | Excludes dormant tokens |
A constituent that ceases to meet any criterion between Rebalance Days remains in the Index until the next Rebalance Day, unless a removal event under Section 6 applies.
4. Weighting approach
The Index uses a capped liquidity-adjusted weighting scheme.
- Each eligible token is assigned a raw weight proportional to its on-chain pool liquidity, averaged over the 14 days preceding Rebalance Day.
- Raw weights are normalised to sum to 100%.
- Any constituent whose weight exceeds 30% is capped at 30%. The excess is redistributed pro-rata among uncapped constituents. The procedure repeats until no constituent exceeds the cap.
- A minimum weight of 2% applies. Tokens whose normalised weight falls below 2% are excluded from that reconstitution, and weights are re-normalised.
Liquidity, rather than market capitalisation, is used because market capitalisation in this segment is a function of supply decisions made by anonymous people at 3 a.m., whereas liquidity is a function of capital someone actually deposited.
4a. Core and sleeve
The Index Treasury holds two distinct books, and this methodology governs them differently.
| Core basket | Momentum Sleeve | |
|---|---|---|
| Nature | Rules-based, passive | Tactical, discretionary within published triggers |
| Cadence | Epoch purchases at target weights | Immediate on trigger, outside epochs |
| Universe | Eligible constituents only (Section 3) | Exempt from eligibility pending review |
| Sizing | Target weights, 30% cap | Hard cap of 10% of deployments (illustrative), per-position limit |
| Outcome | Held; drift corrected by new purchases | Gains recycled to core; losses borne by sleeve reserve |
The Index, as a benchmark, is the core basket. The sleeve is a treasury capability, not an index rule; it is documented here so that the distinction is unambiguous. Sleeve positions do not affect constituent weights. See Index Treasury & Epochs.
5. Rebalancing
- Frequency. The Index is reconstituted monthly on Rebalance Day, a fixed calendar day published at launch.
- Announcement. Proposed additions, removals and weight changes are published as an Index Announcement no fewer than five days before Rebalance Day, in the manner of a conventional index provider.
- Governance. From Phase II, the announcement is put to a token-gated community vote. Eligibility to vote requires a wallet holding at least a minimum balance of $MROCK, published at launch (illustrative: a fixed $MROCK amount). One wallet above the threshold is eligible; votes are weighted by staked balance. A simple majority of participating staked $MROCK, with a quorum published at launch, ratifies the reconstitution. The committee proposes; eligible holders dispose. Until Phase II, the committee ratifies and publishes its reasoning.
- Execution. From Rebalance Day the treasury directs subsequent epoch purchases at the new target weights. The treasury does not sell existing holdings to rebalance, except in the case of a removal event; drift is corrected by directing new purchases, not by trading the basket.
- Between Rebalance Days. Weights float with market movement and are not corrected.
6. Removal events
A constituent is removed from the Index immediately, outside the monthly cycle, on the occurrence of any of the following:
- Liquidity collapse. Pool liquidity falls below 20% of its 14-day average at inclusion.
- Rug behaviour. Removal of pool liquidity by a privileged party, or a contract action that alters supply, freezes transfers or blacklists holders.
- Contract compromise. A verified exploit affecting the token contract or its principal pool.
On an emergency removal, the treasury ceases purchases of the constituent. It does not attempt to sell existing holdings into a collapsed pool; those holdings are written down to zero in NAV and retained as a matter of record. The removed constituent’s weight is redistributed pro-rata at the next epoch.
7. Index committee
The committee is the group of people responsible for applying this methodology, resolving borderline cases and publishing announcements. Its decisions and reasoning are public. Its membership is published at launch. It has no discretion to override a rule in this document; it may only propose an amendment, which follows the same announcement and vote process as a reconstitution.
8. Methodology changes
Amendments to this document are published as a numbered methodology version with a changelog and a five-day notice period. From Phase II, amendments require the same token-gated vote as a reconstitution.
9. Disclaimer
This methodology describes a pre-launch product. The illustrative thresholds above are replaced by launch parameters. Nothing in this document constitutes an offer, a guarantee of performance, or investment advice. See Risk Disclosures.