Munch trades.
Feed the holders.
MemeMunch is a memecoin-focused swap ecosystem with two revenue engines. Token-tax revenue is split between holder dividends and the Site Operational Fund. Net protocol revenue is split between a $MUNCH buyback-and-burn route and the same Site Operational Fund.
Built around actual activity.
The MemeMunch model connects trading activity to holder dividends, repurchases, and site-operation funding. Every flow starts with revenue that has actually been collected.
Two engines, three destinations
$MUNCH token tax splits between holder dividends and the Site Operational Fund. Swap-platform revenue splits between buyback & burn and the same Site Operational Fund. Each flow is tracked separately.
Verifiable on-chain
Dividend payouts, buyback spending, token purchases, burn activity and operational-fund transfers are all linked to on-chain evidence.
Rule-based execution
Smart contracts and a keeper trigger dividend distributions, buybacks and operational-fund transfers when the defined conditions are met.
Two engines. Three destinations.
Each engine has its own revenue source and its own split. Funds are collected first, then routed to dividends, buybacks or operations.
Token tax
$MUNCH buys and sells carry a 1% tax.
Swap protocol
Aggregator swaps generate an integrator fee.
The $MUNCH token.
These are the final tokenomics of MemeMunch.
MUNCH · deflationary through buyback & burn.
98% to holder dividends · 2% to site operations.
98% to holder dividends · 2% to site operations.
| Property | Configuration |
|---|---|
| Name / Symbol | MemeMunch / MUNCH |
| Chain | BNB Chain |
| Total supply | 1,000,000,000 MUNCH |
| Buy / Sell tax | 1% / 1% |
| Token-tax split | 98% to Dividend Vault (holders, pro-rata) · 2% to Site Operational Fund |
| Quote / Trading pair asset | QQQB — Invesco QQQ Trust Tokenized bStocks |
| Dividend asset | QQQB 0x205812CdBed920aFf76C6580abD681a46D11efc7 |
| Net protocol revenue split | 90% buyback & burn · 10% to Site Operational Fund |
| Repurchased tokens (protocol-revenue share) | 100% burned |
| Team / marketing allocation from tax | None |
Burns are executed as genuine ERC-20 burns that reduce totalSupply(), so circulating supply falls as protocol revenue accumulates. Because $MUNCH is a Flap tax token, its dividend asset is always the same as its trading-pair (quote) asset — here, QQQB.
Tax in. Dividends and site funding out.
All $MUNCH trading-tax revenue is split between holder dividends (98%) and the Site Operational Fund (2%). No marketing, team, or buyback allocation is funded from this engine.
| Event | Tax | Destination |
|---|---|---|
| $MUNCH buy | 1% | Flap tax-processing route → 98% Dividend Vault / 2% Site Operational Fund |
| $MUNCH sell | 1% | Flap tax-processing route → 98% Dividend Vault / 2% Site Operational Fund |
| Wallet-to-wallet transfer | 0% | No tax, no routing |
| Liquidity / exempt addresses | Excluded | Excluded from taxation and from dividend eligibility |
How the dividend is paid
Tax is collected in $MUNCH. The 98% dividend share is swapped to QQQB (0x205812CdBed920aFf76C6580abD681a46D11efc7) — the same asset $MUNCH is quoted against — before distribution, following the standard Flap tax-token rule that the dividend asset always equals the quote asset. Paying in QQQB rather than $MUNCH avoids creating sell pressure on $MUNCH from the payout itself, and gives holders real-world exposure to the Invesco QQQ Trust alongside their $MUNCH position. The remaining 2% is routed to the Site Operational Fund.
Each holder's dividend share is proportional to their $MUNCH balance at the distribution trigger. LP, CEX and contract addresses are excluded from eligibility.
Buyback & burn — funded by protocol revenue.
Buyback & burn is funded exclusively by 90% of net protocol revenue (Engine B), not by token tax. 100% of the $MUNCH bought with that 90% share is burned. “100%” refers to repurchased tokens from that share — not to all tokens in circulation.
revenue
MUNCH
burned
Operational Fund
Execution amounts depend on real revenue, market price, liquidity, gas costs and permitted slippage, so no fixed periodic buyback amount is promised. Token-tax revenue is not part of this route — see Token tax for the holder-dividend engine.
MemeMunch Swap.
The swap interface routes token trades through external decentralized liquidity aggregators, including OKX, KyberSwap and OpenOcean, and picks the best available quote for each pair.
How a swap works
- Connect a compatible wallet.
- Choose input and output tokens.
- Review quote, slippage and applicable fees.
- Approve token spending if required.
- Sign and confirm the transaction.
Fees are visible
When a route includes a MemeMunch integrator fee, the interface shows the applicable rate and identifies MemeMunch as the receiving party before confirmation. Network gas, pool fees and token taxes are separate charges.
Routes without a supported integrator fee do not generate protocol revenue.
90% of net revenue funds buybacks. 10% funds site operations.
This is a net-revenue allocation. It does not imply that MemeMunch receives 100% of the gross integrator fee charged to traders.
90% → $MUNCH buyback & burn
“Net protocol revenue” means the fee revenue actually received by the protocol after aggregator revenue-sharing obligations and direct collection or conversion costs. 90% of this net amount buys $MUNCH, which is then burned.
10% → Site Operational Fund
10% of net protocol revenue goes to the same Site Operational Fund that receives 2% of token tax — covering infrastructure, RPC/keeper services, aggregator integration, security review and ongoing development. This portion is not spent on $MUNCH purchases and is not distributed as dividends.
| Stage | What it means |
|---|---|
| Gross integrator fees | Amounts charged on supported routes. |
| Third-party share / eligible costs | Deductions required by integration or collection. |
| Net protocol revenue | Split 90% buyback & burn / 10% Site Operational Fund. |
| Actual buyback | Funds spent in a successful on-chain purchase (from the 90% share). |
| Operational-fund transfer | Funds moved to the Site Operational Fund address (the 10% share). |
Unreceived fees, quotes and pending swaps are not reported as realized buyback or operational funding. Fee tokens and settlement timing differ between aggregators.
Smart contract + keeper, for three flows.
Execution is automated across all three destinations — holder dividends, protocol-revenue buybacks, and Site Operational Fund transfers from both engines — with contract-enforced constraints and an external keeper that monitors balances and submits eligible transactions.
Enforce the rules
Holds designated funds separately per engine, restricts spending destinations, defines approved swap routes, maximum slippage, spending limits, dividend distribution logic, the 98/2 tax split, the 90/10 protocol-revenue split, and burn handling, and exposes events and read functions.
Trigger execution
Watches balances and conditions, submits permitted transactions (dividend distribution, buyback, operational-fund transfer), awaits confirmation, backs off after failures, and reports state — without unrestricted withdrawal authority.
Execution parameters
- Minimum accumulated tax revenue before a dividend round, and minimum accumulated protocol revenue before a buyback.
- Minimum-balance threshold for dividend eligibility; exclusion list for LP, CEX and contract addresses.
- Maximum price impact and slippage on both the tax→QQQB swap and the buyback route.
- Contract-level enforcement of the 98% / 2% tax split and the 90% / 10% protocol-revenue split.
- Gas cost thresholds, trigger frequency and approved call permissions.
- Fallback behavior if RPC, keeper, liquidity or aggregator services fail.
Track the entire flow.
The public dashboard distinguishes collected revenue, funds awaiting deployment, completed dividends, completed buybacks, completed burns, and Site Operational Fund transfers. Every metric is derived from contract events, explorer records or identified settlement statements.
| Metric | Source of truth |
|---|---|
| Tax revenue received | Flap collection / Tax Vault transfers |
| Tax split into 98% / 2% | On-chain split transactions from the Tax Vault |
| Tax → QQQB swap for dividends | On-chain swap transactions from the Dividend Vault |
| Dividends distributed to holders | Distribution transactions, per round |
| Gross and net protocol revenue | Integrator settlement records + treasury receipt |
| Protocol-funded buybacks (90% share) | Transactions funded by protocol revenue |
| Site Operational Fund transfers (2% tax + 10% protocol revenue) | Transactions to the operational-fund address, tagged by source engine |
| MUNCH bought and burned | Token transfers, burn events, supply accounting |
| Unspent balances / unpaid dividends | Balances of the designated contracts |
Security & risks.
The token and its vaults disclose administrative roles and any ability to change tax rates, the 98/2 or 90/10 splits, dividend logic, fee recipients, treasury destinations, keepers, execution thresholds or implementation contracts.
Published for review
- Contract source and addresses.
- Tax treatment of buys, sells and transfers.
- Dividend logic and exclusion list.
- Vault custody and withdrawal permissions, including the Site Operational Fund address.
- Keeper authority and failure recovery.
- Slippage limits and approvals.
- Burn implementation and recorded supply.
Material risks
- Token price volatility and possible loss of value.
- Liquidity, slippage and MEV — including on the tax-to-QQQB swap that funds dividends, and QQQB's own market conditions as a tokenized real-world asset.
- Smart-contract bugs or compromised permissions in the dividend, buyback or fund-split logic.
- Aggregator, RPC and keeper outages.
- Low trading volume resulting in low or no dividends and low or no buybacks.
- Concentration: dividends are proportional to holdings, so large holders receive a proportionally large share.
- Regulatory treatment of pro-rata distributions differs by jurisdiction; this is not legal advice.
Neither dividends nor buybacks guarantee market-price appreciation. Trade only with funds you can afford to lose.
Frequently asked questions.
What is MemeMunch?
A memecoin swap ecosystem with two revenue engines. $MUNCH token tax splits 98% to holder dividends and 2% to the Site Operational Fund. Net swap-protocol revenue splits 90% to $MUNCH buyback-and-burn and 10% to the same Site Operational Fund.
What is the tax on MUNCH?
1% on buys and 1% on sells. Wallet-to-wallet transfers are untaxed.
Does the token tax fund buybacks?
No. Token-tax revenue funds holder dividends (98%) and the Site Operational Fund (2%). Buybacks are funded separately, from 90% of net protocol revenue.
How is the dividend calculated and paid?
Each holder's share is proportional to their $MUNCH balance (pro-rata by % holding). Dividends are paid in QQQB (Invesco QQQ Trust Tokenized bStocks, 0x205812CdBed920aFf76C6580abD681a46D11efc7) rather than $MUNCH, so the 98% dividend share is swapped to QQQB before distribution — QQQB is also $MUNCH's trading-pair (quote) asset. LP, CEX and contract addresses are excluded from eligibility.
Is 100% of the swap fee used for buybacks?
No. The allocation is 90% of net protocol revenue to buybacks and 10% to the Site Operational Fund. Net protocol revenue is lower than the gross fee charged to users after third-party shares and direct costs.
What is the Site Operational Fund for?
It is funded by 2% of token tax and 10% of net protocol revenue, and covers the site's running costs: infrastructure, keeper/automation services, integrations, security review and development. It is not distributed to holders and is not spent on $MUNCH purchases.
What happens to tokens bought back?
All $MUNCH repurchased with the 90% protocol-revenue share is burned, reducing total supply.
Can the same trade pay tax and a protocol fee?
Yes, if both apply to that route. The interface shows all applicable user-facing charges before approval or transaction confirmation.
Do dividends or buybacks guarantee higher token prices or fixed income?
No. Dividend amounts depend on trading volume and tax collected; buyback amounts depend on protocol revenue, market conditions, liquidity and demand. Neither is a fixed or guaranteed return.