Updated September 17, 2026. About a four-minute read.
NASDAFUQ brings memecoin culture and the stock market into the same room. Anime, rave music, cursed trading terminals and a community with something to rally around. The name carries the basket. The basket is the mechanism behind it.
The reward design is simple: a share of trading fees buys a fixed basket of assets, and eligible holders receive their share directly in their wallets. No staking ritual. No claim button. The intended reward assets are Stock Tokens & Tokenized ETFs.
The name was the basket the whole time
| Letter | Asset | The theme | Share of the purchase budget |
|---|---|---|---|
| D | DELL | Dell, AI servers | 20% |
| A | AMD | AI chips and GPUs | 20% |
| F | FLY | Firefly Aerospace, rockets | 20% |
| U | USAR | USA Rare Earth, the materials behind the machines | 20% |
| Q | QQQ | Invesco QQQ, the Nasdaq-100 | 20% |
Five fixed slots. No weekly stock picker, no AI changing the portfolio, no surprise sixth asset. The basket and weights are fixed in the deployed policy; changing them requires a new deployment. Equal spending shares don't mean equal token quantities or equal values afterward.
From trading fees to your wallet
- Fees enter the vault. A published share of trading fees goes into a contract that holds the purchase budget.
- A cycle closes. One cycle is called an epoch. The system sets aside the keeper/gas reserve, adds funds carried from earlier cycles, and splits the remaining budget five ways.
- Holder balances are recorded. A snapshot records eligible balances at the closing block. Your balance relative to the total eligible balance determines your share.
- The vault buys the basket. Each purchase checks a reference price, liquidity, minimum acceptable output and a deadline. FLY can be bought in smaller pieces.
- The assets arrive. A distributor calculates each holder's amount and sends the assets in batches. The sender pays the transaction gas. Receiving a drop doesn't require connecting to the site, signing a claim or paying gas yourself.
For each asset:
your share = your eligible snapshot balance ÷ all eligible snapshot balances
your amount = available asset inventory × your share, rounded downAvailable inventory includes assets bought this cycle and any inventory carried from earlier cycles. Your balance at the snapshot matters, rather than how long you've held or how many wallets you use. Fees collected, purchase prices, execution and carryover determine what there is to distribute. A scheduled cycle doesn't create a fixed amount.
What “100% fees to holders” means
The accounting uses net distributable fees: what remains after the published keeper/gas reserve and execution costs. The reserve pays for operating the system, is fixed at deployment, and can't exceed 20% of gross fees.
purchase budget = gross fees + carried-in funds − keeper/gas reserve
each basket slot = purchase budget × 20%, rounded downHolders split the resulting assets. The slogan describes where the net distributable amount goes; the reserve isn't part of that amount. The exact reserve and trading-fee share are deployment settings, not something the website decides.
Why FLY gets sips, not gulps
FLY is designed as the basket's thin-liquidity slot. Instead of one large buy moving its own price, the system makes smaller, spaced purchases called clips or sips.
Early sips stay within FLY's share of net fees already received. They don't spend tomorrow's expected fees. After the cycle closes, further clips can finish the allocation if the purchase checks pass.
When a step needs another try
If a purchase can't execute within its checks, the unspent budget stays in the vault for a later cycle. The system keeps the same basket rather than substituting another asset. Any earlier successful purchases remain inventory.
If a delivery fails, it can be retried without paying a completed transfer twice. After the retry cap, an admin can roll the unpaid inventory forward. Amounts below the minimum transfer size also roll forward. That inventory belongs to the later cycle's snapshot, rather than staying as a personal credit for the original wallet.
A keeper is the operator that advances the cycle and publishes its holder snapshot. Contracts enforce the basket, permitted routes, proof requirements and amount calculation. Anyone can independently rebuild the snapshot from transfer history and compare it with the published record. The operator still needs to run the process; a countdown is the cycle schedule, not a delivery promise.
Current deployment
The verified deployment described by these sources is on Robinhood Chain Testnet, chain ID 46630. Its fees and reward assets are simulated: mDELL, mAMD, mFLY, mUSAR and mQQQ are mock tokens with no monetary value. The published receipts record that rehearsal, not distributions of real Stock Tokens & Tokenized ETFs. Its keeper reserve is 10%. An official mainnet network, token address, launch date and final launch terms aren't established in the project records.
Real-asset distribution still depends on issuer access and the distribution structure. NASDAFUQ isn't affiliated with Robinhood, Nasdaq, Invesco or the basket companies.
Follow the mechanism
The receipt page shows each cycle's fees, purchases, deliveries and carryovers. OBSERVED ONCHAIN marks recorded events; ESTIMATED marks calculated values; PENDING, FAILED and ROLLED OVER explain the other paths. A failed attempt can remain in the history after a successful retry. The file's timestamp tells you when the record was generated.
- Agent brief: the community, basket and full mechanism in one document.
- Published receipts and deployment settings.
- Handbook and architecture: the underlying rules.
This guide follows the current site brief, with deployment details kept separate from the product explanation.