Creator fees that follow rules you signed.

You choose a fee mode before launch. Your wallet signs the fee configuration. From then on, fees route according to that configuration: straight to wallets through native Bags fee sharing, or into a strategy vault on our program for automated modes like buyback and burn.

Launches happen on Bags on Solana mainnet. Explore shows only confirmed tokens launched through BagSplit, with their recorded fee modes. Drafts and external launches do not appear in this feed.

1. 1
   Connect and sign in
   Connect a Solana wallet and sign a plain-text message. It is not a transaction and costs no gas.
2. 2
   Describe the coin
   Upload an image (PNG, JPEG or WEBP, up to 5 MB). Name up to 32 characters, ticker up to 10 characters using A-Z and 0-9. Description, socials and an initial buy are optional.
3. 3
   Pick a fee mode
   Choose one of seven modes on Launch. The mode guide explains each.
4. 4
   Sign and launch
   Approve the fee config, the strategy vault setup if your mode needs it, and the launch transaction.

1. 1
   Draft
   BagSplit saves a launch record so you can resume after a reload. Unfinished launches show a Resume action on the Dashboard.
2. 2
   Wallet-signed fee config
   The server builds and simulates the transaction before your wallet is asked to sign. After signing it is submitted and polled.
3. 3
   Strategy vault setup (automated modes)
   Buyback, Holder Rewards and Custom initialize a vault on the BagSplit program, signed by you as owner.
4. 4
   Wallet-signed launch
   The launch is reported as successful only once its status is confirmed. A confirmation popup shows the image, name, ticker and a copyable mint address.

Dismissing a wallet prompt or a failed transaction is recoverable. BagSplit never creates a duplicate launch automatically. Simulation checks that a transaction should execute; it is not a guarantee of outcome or profit.

• Platform pool. BagSplit partner revenue is currently 25% (2500 bps) of the eligible platform fee pool, set by on-chain partner config. It is not a percentage of trading volume and is not deducted from your recipients.
• Creator entitlement. A separate deployer share held by the creator wallet that paid for the fee config.
• Recipient pool. What your mode allocates. Native wallet percentages apply to this pool and sum to 10000 bps.

Network fees, rent and an optional initial buy are separate costs. BagSplit makes no universal trading fee or payout promise.

In BagsPay mode the recipient pool is a single entry: the official payout wallet at 10000 bps. It cannot be combined with other recipients or vault strategies.

Supported methods

• X Money. 1-15 letters, digits or underscore. Optional @.
• Cash App. 1-20 letters, digits, underscore or hyphen, with at least one letter. Optional $.
• Venmo. 5-30 letters, digits, underscore or hyphen. Optional @.

Terms, accepted at launch and on every destination change

• Only the normal remaining claimer pool goes to the payout provider.
• A separate 25% gross claimer-pool deployer share goes to the wallet that pays the fee config, in SOL. It is not converted.
• Claims start at a 0.25 SOL threshold. The normal payout minimum is 5 USDC.
• Conversion costs about 0.5-0.7% plus a few cents per payout.
• Cash orders are discounted 10%, increasing to 20% if unfilled after 24 hours.
• Your account must accept payments through the chosen method.
• Provider and Peer buyer settlement is not guaranteed.
• There are no guarantees on payout timing.

Settlement and timing are not guaranteed. Use the token's payout page to manage destinations.

Who can do what

How vaults are built

• Vaults are PDAs derived from program, creator and mint, so each coin is separated. No vault has a private key.
• Fees enter through a fixed-purpose native Bags claim bridge.
• Each cycle enforces interval, min and max limits, and an expected nonce for replay protection.
• Initialization, pause and allowed recovery require the owner signature.

Liquidity in the deployed program

Deployed Add-and-lock into an existing supported pool and position.

Deployed Owner-authorized first-position bootstrap after graduation, with automatic launch setup and keeper execution.

1. 1
   Creator approvals
   You sign the fee config, vault initialization and launch.
2. 2
   Fees accumulate
   Allocated creator fees reach the vault through the claim bridge.
3. 3
   Due cycle executes
   When interval and thresholds are met, the service gas signer submits the cycle: buyback and burn, holder reward funding, or both for Custom.
4. 4
   Reconciliation
   Transaction records, confirmation checks and on-chain nonces are used to reconcile cycles before retrying them.

Unspent funds may be recovered under pause and policy rules. BagSplit exposes no withdrawal path for principal locked through Meteora's native permanent lock. A lock does not remove smart-contract or external-protocol risk.

• No private keys are generated or stored in the browser. Your wallet signs sign-in, fee config, vault setup and launch.
• Sign-in is a one-time plain-text challenge, not a transaction.
• Transactions are simulated on the server before you sign. Simulation is not a profit guarantee.
• Server-side operational keys sign due automation cycles and snapshots through a dedicated gas wallet with no upgrade authority.
• The program is upgradeable and the deployment wallet holds that authority.
• The snapshot oracle is trusted within the reward allocation. It is not trustless.

The app calls a same-origin API under /api with a session cookie set after wallet sign-in. Readiness, feeds, launches, transaction preparation, simulation, submission, payouts and claims all go through it. Bags and RPC credentials stay on the server; the app never asks for keys in a form, and shows data as unavailable rather than substituting samples.

Check live readiness on Launch before you start.