Launch venue: Meteora DBC
Tokens launch through Meteora's Dynamic Bonding Curve (DBC), reached behind a venue-agnostic interface so the venue can be swapped without touching the rest of the system.
Why DBC, not LaunchLab
The launch venue is Meteora DBC, not Raydium LaunchLab. The reason is the quote asset. DBC config keys are permissionless and support arbitrary quote mints; LaunchLab does not. Botify pairs every launch against a tokenized stock, so it needs a venue that lets an arbitrary Token-2022 mint be the quote side. DBC does; that requirement decided the venue.
The venue interface
The product launches through a LaunchVenue interface with five operations: createConfig, createLaunch, buy, sell, and getState. A factory returns the implementation. Meteora DBC is built; Raydium LaunchLab is reserved as a swappable fallback and not implemented.
One config per stock
A DBC config is created once per quote (stock) mint and reused by every launch against that stock. The config is cached on the stock, so the first launch against a stock pays to create it and every launch after reuses it.
The bonding-curve fee (100 bps by default) is split three ways: protocol, partner and creator. The partner, the fee claimer, is the $BOTIFY treasury. That is the on-chain end of the fee flow.
Token-2022 badge gate
Every xStock is a Token-2022 mint with extensions, and Meteora requires an admin token badge as a remaining account to use one as a quote. We cannot create that badge, so its presence is a hard gate on whether a mint is launchable at all. All 17 watchlisted stocks are badged on mainnet, which is why the watchlist is exactly that set.
Migration is automatic
A bonding curve that fills up migrates to a full liquidity pool (DAMM v2). Botify does not run migration infrastructure. Meteora runs keepers that migrate a completed curve automatically once its migration threshold is reached (a minimum of roughly 750 USD equivalent). A manual migrator exists as a fallback for devnet, but on mainnet the keepers do it.
Migrated pools must permanently lock at least 10 percent of liquidity on day one. The config locks the partner side in full to satisfy that rule.
Proven, with one caveat
The full path (config, launch, buy, state) is proven end to end on devnet against a plain SPL stand-in for the quote asset. The real xStocks are mainnet-only and need the token badge, so a real xStock quote, and its Scaled UI multiplier behavior, cannot be exercised on devnet. That interaction stays unverified until a first live launch on mainnet.