BAN is a capped meme token riding Solana’s security budget

Comedian (BAN) is not trying to be a new base layer with its own validator set. It is a Solana SPL meme asset launched via Pump.fun, with the narrative anchored to Maurizio Cattelan’s “Comedian” (banana + duct tape) and the surrounding commentary on value and spectacle.

That has a direct tokenomics consequence that people often underweight. BAN does not pay for network security. It inherits Solana’s security budget. If Solana’s validator economics degrade, BAN does not have a compensating “fee-to-stakers” or issuance-to-validators lever to pull. BAN’s design is closer to “scarce social asset” than “security-backed productive asset.”

On the project’s site, the framing leans into an “art meme ecosystem,” mentioning an app, store, mini-games, and “incentives from Comedian DAO,” but without publishing a detailed on-chain specification for how BAN is used inside those products (payments, gating, rewards, burns, or revenue share). For a checklist of what teams typically need to specify, see token economy components.

Supply, issuance, and what “fixed” means here

Circulating supply data lists 999,961,859 BAN as circulating supply and total supply, with a 1,000,000,000 BAN max supply parameter.

Pump.fun’s own help center describes its standard meme coin template as 1 billion tokens minted and that no further coins can be minted. BAN’s listing also points back to a Pump.fun origin page for the same mint address, which is consistent with that template lineage.

From a supply integrity perspective, the two things that matter are (1) whether additional minting is possible and (2) whether freezing / transfer controls exist. Public pool analytics for BAN/SOL indicate minting and freezing authority is disabled for the trading pair, which supports the “hard-capped, no-admin” supply story at the token level.

Pump.fun also documents that “the contract is renounced upon creation” and that the coin’s metadata is immutable after creation, which reduces the surface area for post-launch control over the asset’s identity layer (name, socials embedded at mint time).

Distribution and structure, using only verifiable snapshots (this is not a formal “allocation chart” from a whitepaper):

Utility and fiscal flows: where value can (and can’t) accrue

Start with the hard constraint. There is no published mechanism that routes protocol revenue to BAN holders. No staking yield. No scheduled emissions. No documented buyback and burn. BAN’s “token economy” is therefore dominated by secondary market positioning and liquidity access, not by endogenous cashflows.

During Pump.fun’s bonding-curve phase, Pump.fun charges trading fees and splits them between the Pump.fun protocol and the token creator. The bonding-curve fees are specified as 1.25% total fee before graduation, composed of 0.95% protocol and 0.30% creator. This matters historically if BAN traded meaningfully on Pump.fun early on. It does not automatically create a long-term BAN holder yield stream today.

Post-graduation, BAN trades like a normal Solana token across DEX routing and CEX order books. AMM swap fees accrue to liquidity providers (and to the DEX protocol, depending on venue), not to BAN holders by default. That is the core trade-off of “zero inflation” meme assets. You avoid dilution. You also avoid having a native budget to pay for development, security reviews, listings, or sustained liquidity incentives.

From a security-budget-maximalist lens, this is the structural weakness. The system has no native spending policy. If the ecosystem wants security work done, it needs either (1) voluntary contributions, (2) off-chain monetization, or (3) ad hoc treasury formation. Each option increases governance ambiguity and reduces modelability.

Liquidity, market structure, and holder concentration

BAN’s main on-chain liquidity venue is a BAN/SOL pool on Raydium. A pool liquidity snapshot reports around $2.99M liquidity for that pool and indicates that 99.98% of liquidity is locked. Liquidity lock is a meaningful mitigation against the classic “pull the LP” rug pattern. It is not a guarantee against price collapse.

Two concentration vectors still matter.

First is custodial concentration. Pool analytics identify a single CEX-associated address (Gate.io) as holding 480.46M BAN in a snapshot. Even if those tokens represent aggregated customer balances, it creates an obvious “one entity can move size” risk at the market microstructure layer.

Second is launch-path dependency. Pool analytics flag that 3.6% of tokens were purchased via bundled buys for this pool, which is a common proxy traders use to reason about early sniping and wallet clustering risk. That does not prove maliciousness. It does imply that some early supply likely sits in coordinated hands, which increases tail risk around exits.

DEXScreener shows the BAN/SOL pair as created “1y 4mo 6d ago” relative to its page rendering, and it reports pooled inventory in the same ballpark (BAN and SOL amounts) as the pool analytics view, which is consistent with a mature pool rather than a newly bootstrapped one.

Governance and parameter control: mostly off-chain

There is no evidence in the public materials surfaced via listings, the project’s site, or the trading venues that BAN has an on-chain governance system controlling monetary parameters. That is coherent with the “mint authority disabled” state and Pump.fun’s “renounced contract” framing.

The official site speaks about a “Comedian DAO” as a potential source of incentives for ecosystem builders, but it does not publish the actual control plane. No treasury address. No multisig policy. No proposal process. No spend rules. That absence is not a moral critique. It is a governance surface area problem. Without explicit controls, “DAO” becomes an off-chain social label.

Profile ownership claims are also shown for the token’s profile on October 27, 2024, November 6, 2025, and February 18, 2026. That is not on-chain governance. It is a signal that the social layer around BAN’s “official presence” has been contested or at least repeatedly re-administered across common discovery surfaces.

Risk analysis (Security Budget Maximalist)

The cleanest part of BAN’s design is its lack of monetary complexity. There is no visible inflation schedule and no evidence of a mutable mint. That reduces one major class of long-term holder risk: unexpected dilution.

The cost is equally clear. With no issuance and no specified fee capture to a BAN treasury, there is no native security budget for anything above the base chain. No funding loop for audits, ongoing development, incident response, or even basic operational continuity. In practice, meme assets survive on attention, exchange access, and community coordination. That works until it does not.

For a contrasting meme-asset case study, compare this with Melania Meme.

Dominant risk: no durable security budget, no enforceable fiscal policy

Trigger: sustained decline in speculative volume and attention, or a prolonged risk-off regime where marginal buyers do not show up.

Mechanism: BAN has no documented endogenous revenue stream that scales with usage and can be committed to maintenance. Pump.fun fees historically reward the creator and Pump.fun during the early lifecycle, but that is not a perpetual, on-chain policy that BAN holders can rely on. Post-graduation, most economic value leaks outward to LPs, DEX venues, and CEX venues via standard trading fees. The token itself does not compound security.

Who bears it: long-horizon holders and any builders who attempt to create real utility on top of BAN without a dedicated budget. They end up subsidizing the ecosystem through unpaid labor or external fundraising. Late-cycle buyers become the de facto “security budget” via price support, which is not a budget. It is reflexivity.

Measurable indicators: multi-month declines in on-chain liquidity and volume (pool liquidity, 24h volume), shrinking holder growth, and repeated churn of “official” discovery surfaces like token profile ownership claims or social channels, which suggests coordination costs are rising. We collect related market-structure work in our crypto research page.

If the project actually wants to become an “ecosystem,” it eventually needs a credible commitment device. That can be a transparent multisig treasury funded by voluntary donations, a product that charges fees in SOL and uses them for public goods, or a contract-level mechanism that routes some flow to a treasury. Each choice comes with trade-offs. The key point is that “no inflation” does not mean “free security.” It often means “no budget.”

Top 3 risks

  1. Security budget failure (dominant): Trigger: prolonged drop in trading activity and social reach. Mechanism: no emissions and no documented fee-to-treasury loop means no sustained funding for audits, development, and incident response; BAN becomes purely sentiment-priced. Who bears it: holders and unpaid ecosystem contributors. Measurable indicators: declining liquidity and volume on the primary pool, stalled holder growth, and increasing off-chain governance churn across discovery surfaces.
  2. Custodial concentration shock: Trigger: a major exchange custody event, delisting, or large net outflows from a dominant CEX holder cluster. Mechanism: concentrated balances can turn into a sudden liquidity vacuum or forced selling, amplifying drawdowns in a relatively finite liquidity pool. Who bears it: spot holders and LPs. Measurable indicators: top-holder share changes, large CEX-associated wallet balance moves, and widening slippage versus trade size.
  3. Coordinated supply and market-structure manipulation: Trigger: whale exits into thin liquidity, especially after periods of renewed attention. Mechanism: early clustered supply plus limited pool depth can translate into steep price impact; “LP locked” prevents a pull but does not prevent a dump. Who bears it: late buyers and LPs (impermanent loss). Measurable indicators: bundled-buy flags, top holder concentration, rising sell/buy imbalance, and volume spikes not matched by sustained liquidity growth.

If BAN stakeholders ever want a more infrastructure-grade posture, the work is straightforward but not easy: publish the treasury and control model (if it exists), define what BAN is used for inside products, and specify sustainable funding for maintenance. If you need tokenomics consulting on how to do that without quietly reintroducing admin risk or unsustainable emissions, treat it like a security budget design exercise first, and a narrative exercise second-our tokenomics design services are built for that.



This article is part of our Tokenomics Deep Dive series.