​
Overview

Some endpoints support adding an optional tip to a wallet of your choice. This lets you direct a portion of lamports to any provider (e.g., Jito, Astral) or a wallet you control when constructing transactions. By default, all transactions generated by these endpoints already include appropriate Compute Budget instructions:
  • setComputeUnitLimit and setComputeUnitPrice are set to optimize for reliable inclusion and cost-efficiency.
  • No tip is included by default. Tips are only added when you provide tipWallet and tipLamports.

​
Supported endpoints

  • POST /token-launch/create-config
  • POST /token-launch/create-launch-transaction
  • POST /token-launch/fee-share/create-config
These endpoints accept two optional fields in the request body:
  • tipWallet (string): Base58 encoded Solana public key of the tip recipient wallet.
  • tipLamports (number): Tip amount in lamports.
If omitted, no tip is included.

​
How it works

When you include tipWallet and tipLamports, the API appends a tip transfer as the final instruction in the generated transaction(s). Priority fee settings (setComputeUnitLimit and setComputeUnitPrice) are always included regardless of tipping. You are responsible for:
  • Submitting and confirming the returned transaction(s)
  • Ensuring the provided tipWallet is valid and owned by the intended provider
  • Choosing an appropriate tipLamports value
Notes:
  • Tipping is purely optional and does not affect endpoint functionality when omitted.
  • There is no provider/key allowlist. You can use any valid Base58 encoded Solana public key for tipWallet.
  • The transaction fee payer funds both the network fees and the tipLamports transfer. Ensure the payer has sufficient SOL for all costs.

​
Example payloads

Add a tip when creating a token launch transaction: 
{
  "ipfs": "ipfs://...",
  "tokenMint": "...",
  "wallet": "...",
  "initialBuyLamports": 25000000,
  "configKey": "...",
  "tipWallet": "JitoOrAstralWalletBase58...",
  "tipLamports": 100000
}
Add a tip when creating a fee-share config: 
{
  "walletA": "...",
  "walletB": "...",
  "walletABps": 5000,
  "walletBBps": 5000,
  "payer": "...",
  "baseMint": "...",
  "quoteMint": "...",
  "tipWallet": "TipRecipientBase58...",
  "tipLamports": 100000
}

​
Validation and limits

  • tipWallet must be a valid Base58 encoded Solana public key (any key is allowed; no allowlist)
  • tipLamports must be a positive integer within your balance constraints
  • The API does not currently enforce provider allowlists; use caution and verify recipients

​
Troubleshooting

  • If a transaction fails to simulate or send, verify your tipWallet, tipLamports, and that your payer has sufficient SOL.
  • If you do not see the tip reflected on-chain, confirm the final submitted transaction includes the tip instruction and was confirmed.