$FUND  memefund
Whitepaper · v0.1 · Draft

A memecoin fund that scales itself from the tax line.

Every transfer of $FUND pays a protocol tax. The tax buys a basket of blue-chips and memecoins that backs the token 1:1 against supply, marked to NAV on-chain and voted by holders. $FUND is convertible into its share of that basket at any time (with a burn), and a staked slice compounds and is airdropped back to holders every cycle.

Transfer tax
5.0%
Governance-set, capped
→ Growth sleeve
90%
Blue-chips + memecoins
→ Yield sleeve
10%
Staked in Avantis
Target APY
~10%
Airdropped each cycle, variable
Backing
1 : 1
Convertible, 50% burned
Governance
Token-wtd
DAO over the basket
01

Overview

A hedge fund where the management fee is the transaction tax, the LPs are the holders, and the books are a block explorer.

Most memecoins return value to nobody. They trade on attention, the attention fades, and the only thing left on-chain is a flat liquidity pool. memefund inverts that. The token is a wrapper around a real, growing treasury of assets, and the act of trading the token is what funds the treasury.

Three things hold the design together:

  • The tax funds the fund. A tax on every transfer is swept into a treasury and deployed into a basket of blue-chip and memecoin assets.
  • The fund backs the token. Treasury holdings are tracked 1:1 against circulating supply and marked to a live net-asset-value (NAV) that anyone can verify on-chain. $FUND is convertible into its share of the basket at any time, with a portion burned on conversion.
  • The holders run the fund. Token-weighted governance decides what the basket holds, and a staked slice of the treasury earns yield that is airdropped back to holders every cycle.
In one line

Buy the token, and you own a transparent, voted, yield-paying claim on an on-chain basket that the token's own trading volume keeps filling, convertible back to the underlying whenever you want.

02

How it works

Follow a single dollar of tax from a trade to a dividend.

The protocol is a loop. Trading creates tax, tax becomes treasury, treasury splits into a growth sleeve and an income sleeve, and the income sleeve pays holders. Below is the flow of funds for one taxed transaction.

Transfer buy / sell / send tax 5% Treasury swept → USDC via Jupiter 90% 10% Asset basket bluechips + memes Staked yield Avantis · Base backs NAV supply 1:1 yield Rewards airdrop / cycle
tax → treasury → 90% basket (NAV) + 10% staked yield → rewards airdrop

Stepping through it:

  1. A transfer happens. Any buy, sell, or transfer of $FUND triggers a fixed-percentage transfer tax, withheld natively at the token level.
  2. The treasury sweeps. Withheld tax is periodically harvested and swapped into USDC through a DEX aggregator, building a stable base of dry powder.
  3. The treasury splits. By policy, roughly 90% of net treasury value is the growth sleeve (a basket of blue-chips and memecoins) and roughly 10% is the yield sleeve (staked tax revenue).
  4. The basket backs the token. Every basket position is on-chain and counted toward NAV, so the protocol can show a verifiable backing value per token at all times, and $FUND can be converted into its share of the basket at any time (with a burn).
  5. The yield sleeve pays out. Returns on the staked 10% compound at a target ~10% APY and are airdropped automatically to eligible holders every cycle.
03

Tokenomics & the tax

The tax is the entire business model, so its design matters more than the supply curve.

The transfer tax

$FUND is issued as a Solana Token-2022 mint using the native transfer-fee extension. A percentage of every transfer is withheld by the token program itself. There is no honeypot router contract, no off-chain trust required, and the fee is enforced at the protocol level on Solana. Fees accrue on each token account and are periodically harvested to the treasury.

ParameterIllustrative valueSet by
Transfer fee5.0% per transferGovernance, hard-capped in mint config
Max fee capPer-transfer ceiling (anti-whale)Mint configuration
Harvest cadenceThreshold or scheduledTreasury keeper
Growth / yield split90 / 10Governance
Design note

A flat transfer fee taxes velocity, not just buys. High-churn speculation funds the fund the most, which is exactly the behavior a memecoin generates anyway. The cap keeps a single large transfer from over-taxing real treasury rotations.

Supply

Total supply is fixed at mint; there is no inflation. The treasury grows in value from tax revenue, not by minting new tokens, so backing-per-token is not diluted by emissions. Recommended allocation buckets:

BucketPurpose
Public floatTradable supply; the tax base
Protocol treasurySeed liquidity & bootstrap basket
Governance reserveFounder/steward position (see Governance)
EcosystemMarket-making, listings, partnerships
Tax-split calculator
$
5.0%
Tax withheld
$500
→ Basket (90%)
$450
→ Yield (10%)
$50
Illustrative only. Edit the trade size and drag the rate to see how a single transaction feeds the treasury. The income slice is what compounds into the dividend.
04

Treasury & 1:1 backing

The website is the fund's NAV statement, and the chain is its auditor.

The treasury holds two things: a basket of blue-chips and memecoins (the growth sleeve) and a staked yield position (the yield sleeve). Both are on-chain at known addresses, so net asset value is computable by anyone, not asserted by the team.

What "1:1 matched" means here

Backing-per-token is defined as treasury NAV divided by circulating supply:

backing_per_token = treasury_NAV / circulating_supply

The protocol does not promise that the market price equals backing. Markets do what they want. It promises that the backing figure is real, fully collateralized by assets actually in the treasury, and updated live. The site renders the basket holding-by-holding (asset, units held, USD value, % of NAV) alongside the income sleeve, so a holder can reconcile the displayed NAV against the chain at any moment.

Why this is the credible part

"Fully backed" is a claim every project makes and few can prove. Reading positions from public addresses and showing the math turns a marketing line into something a skeptic can independently verify in a block explorer.

The basket

The growth sleeve is a governance-curated set of blue-chip crypto and memecoins with target weights. Tax revenue buys the blue-chip core first for a durable floor, with a curated memecoin sleeve for upside. Accumulation and rebalancing execute through Jupiter DCA / TWAP rather than market orders, so large treasury moves don't move the assets against the fund. The basket can be rebalanced on a cadence or when weights drift past a band; both are governance parameters.

Growth engine: leverage

Beyond spot accumulation, a bounded, governance-gated leveraged trading strategy can be run on a ring-fenced share of the treasury to grow the vault faster than spot alone. Leverage is capped, isolated from the backing basket, and sized as part of the risk budget, not layered over the whole treasury.

05

Convert & burn

Backing you can actually take delivery of, not just read about.

$FUND is convertible 1:1 into the underlying tokens the fund holds: redeem your $FUND and receive your pro-rata share of the basket (by NAV) in the actual assets, on-chain. This turns "fully backed" from a claim into a right, and anchors the token's value to its backing rather than to sentiment alone.

The 50 / 50 split

The $FUND you return on conversion is split in half: 50% is burned and 50% is retained by the treasury. Both halves leave the circulating float, so backing-per-token rises for everyone who stays: the burn permanently shrinks supply, and the retained half grows the treasury. Conversion is therefore accretive to remaining holders and makes supply deflationary over time.

on convert: basket_share → wallet  ·  returned $FUND = 50% burned + 50% to treasury

Worked example · illustrative

Convert1,000,000 $FUND
Basket share returnedyour pro-rata share of treasury NAV, in underlying tokens
Burned (50%)500,000 $FUND destroyed
To treasury (50%)500,000 $FUND retained
Effect on remaining holdersbacking-per-token ticks up
06

Governance

Holders vote the basket.

Token-weighted governance controls the parts of the protocol that involve discretion: what the basket holds, the target weights, rebalance rules, the tax rate (within its cap), and the growth/income split. Proposals follow a standard lifecycle.

  1. Proposal. A holder above a proposal threshold submits a change (add/remove asset, reweight, adjust a parameter).
  2. Discussion. A fixed window for debate before voting opens.
  3. Vote. Token-weighted voting over a snapshot of balances, subject to a quorum.
  4. Execution. Passing proposals queue through a timelock, then execute against the treasury via the keeper.
07

Rewards (APY)

Earn automatically. No staking. Just holding.

A fund that only appreciates asks holders to sell to realize anything. Rewards give them a reason to hold. We take 10% of all taxes from $FUND swaps and stake them in Avantis for a target ~10% compounding return. Each cycle the protocol withdraws the excess above the staked principal and airdrops it to holders, leaving the principal in place to keep compounding. No action is required from holders, rewards land straight in the wallet.

Payout, cadence & eligibility

  • Source. The staked 10% earns yield in the Avantis avUSDC vault; only the excess yield is withdrawn and distributed.
  • Asset. Rewards are paid in $FUND, airdropped automatically. A roadmap item moves payouts to $USDC deposited straight to your wallet.
  • Cadence. Distributed on a fixed weekly cycle.
  • Eligibility. Holders with 0.25% or more of $FUND supply qualify.
  • Weighting. Pro-rata by holding across eligible wallets.

Worked example · illustrative

Treasury NAV$1,000,000
Staked in Avantis (10%)$100,000
Excess yield (~10% APY)~$10,000 / year
Withdrawn & airdroppedpro-rata to eligible holders, weekly
Why Avantis fee-yield, not farm emissions

Rewards are funded by real tax revenue staked in Avantis, which pays from organic trading-fee yield rather than minted supply, so payouts don't dilute backing-per-token. The headline ~10% APY is a target, variable with treasury size and yield conditions, and is not guaranteed.

08

Architecture

A Solana token and governance layer, with a bridged yield sleeve on Base.

The one genuine complication: the tax mechanism lives best on Solana (Token-2022 transfer fees + Jupiter), but the chosen yield source may live on Base. The treasury is therefore multichain, and the bridge between them is a first-class component, not an afterthought.

ComponentWhereRole
$FUND mintSolanaToken-2022, transfer-fee extension; native tax + harvest
Treasury multisigSolanaSquads-style multisig holding the basket & dry powder
ExecutionSolanaJupiter DCA/TWAP for basket accumulation & rebalance
Convert / burnSolana1:1 redemption into basket tokens; burns a % of converted $FUND
Leverage engineTBDBounded, governance-gated leveraged strategy on a ring-fenced share
GovernanceSolanaProposals, snapshot voting, timelock
BridgeSolana ⇄ BaseNative USDC transfer (CCTP) for the yield sleeve
Yield sleeveBaseStaked tax revenue in the Avantis avUSDC vault
NAV / accountingOff-chain readerReads all positions, computes NAV & backing-per-token for the site
DistributorSolanaSnapshot + pro-rata reward airdrop to eligible holders
09

Decentralization path

The credible answer to "your vote always wins": say when it stops.

Stewardship is a launch condition, not the destination. A published path turns a centralization weakness into a roadmap commitment.

PhaseGovernance realityTrigger to advance
StewardFounder reserve decisive; votes are directional/ratifyingFloat & treasury below thresholds
SharedSteward retains veto/guardrail only; community sets the basketTreasury NAV & holder count milestones
OpenSteward reserve reduced below majority; quorum carries votesSustained participation; security maturity

Each transition should be on-chain and visible: reserve size, quorum, and timelock parameters published, so "we'll decentralize" is measurable rather than promised.

10

Ecosystem

The fund is the product; the community is the distribution.

A handful of social and product surfaces turn holding into a game and give the protocol an on-chain identity.

SurfaceWhat it is
LeaderboardPublic ranking of holders (by holding size and/or realized P/L) to gamify accumulation and reward conviction
ENSA protocol-owned ENS name for the treasury / brand identity onchain
fomo.familyThe protocol's fomo.family account is the treasury, so treasury activity (buys, conversions, rewards) is surfaced there directly
11

Risk factors & disclaimers

An on-chain fund of blue-chips and memecoins that trades with leverage and pays rewards is roughly as risky as that sentence sounds. Read before deploying capital.

Protocol & market risk

  • Basket volatility. Memecoins are highly volatile and can go to zero; even the blue-chip core can fall sharply, and illiquid positions may be hard to exit at marked value.
  • Leverage risk. The leveraged growth strategy can be liquidated and lose its ring-fenced capital outright; in adverse conditions it can shrink the treasury rather than grow it. Caps and isolation reduce but do not remove this.
  • Smart-contract risk. Bugs in the token, treasury, convert/burn, governance, leverage, or distributor contracts could cause loss. Audit everything; nothing here is audited yet.
  • Bridge risk. Moving the yield sleeve between Solana and Base exposes treasury value to bridge security.
  • Reward / yield risk. The staked-yield source is variable and can underperform; the ~10% APY is a target, not a guarantee, and rewards (and the roadmap to USDC payouts) are not guaranteed. Holders below the eligibility threshold earn nothing.
  • Price vs backing. Conversion ties $FUND to its backing, but market price can still trade below NAV, and the conversion burn means you receive slightly less than your gross share. Backing is collateralization, not a price floor.
  • Governance concentration. During the steward phase, the founding entity can determine outcomes. Holders are trusting that stewardship.
  • Tax friction & venue support. Transfer-fee tokens can be unsupported or mishandled by some venues, wallets, and routers; integrations need testing.