> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bags.fm/llms.txt
> Use this file to discover all available pages before exploring further.

# Priority Fees and Tips

> How to optionally add tips to supported endpoints

### 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-launch-transaction`
* `POST /fee-share/config` (fee share configuration creation)

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:

```json theme={null}
{
  "ipfs": "ipfs://...",
  "tokenMint": "...",
  "wallet": "...",
  "initialBuyLamports": 25000000,
  "configKey": "...",
  "tipWallet": "JitoOrAstralWalletBase58...",
  "tipLamports": 100000
}
```

Add a tip when creating a fee-share config:

```json theme={null}
{
  "payer": "...",
  "baseMint": "...",
  "feeClaimers": [
    {
      "user": "...",
      "userBps": 5000
    },
    {
      "user": "...",
      "userBps": 5000
    }
  ],
  "tipWallet": "TipRecipientBase58...",
  "tipLamports": 100000
}
```

### Recommended providers

You can use any valid Base58 Solana address for `tipWallet`. For compact transactions, we recommend using a recipient that is already included in our public Address Lookup Table (LUT): `Eq1EVs15EAWww1YtPTtWPzJRLPJoS6VYP9oW9SbNr3yp`. See [Address Lookup Tables](/principles/lookup-tables) for details.

Current provider recipients included in the LUT:

* Jito:
  * `96gYZGLnJYVFmbjzopPSU6QiEV5fGqZNyN9nmNhvrZU5`
  * `HFqU5x63VTqvQss8hp11i4wVV8bD44PvwucfZ2bU7gRe`
  * `Cw8CFyM9FkoMi7K7Crf6HNQqf4uEMzpKw6QNghXLvLkY`
  * `ADaUMid9yfUytqMBgopwjb2DTLSokTSzL1zt6iGPaS49`
  * `DfXygSm4jCyNCybVYYK6DwvWqjKee8pbDmJGcLWNDXjh`
  * `ADuUkR4vqLUMWXxW9gh6D6L8pMSawimctcNZ5pGwDcEt`
  * `DttWaMuVvTiduZRnguLF7jNxTgiMBZ1hyAumKUiL2KRL`
  * `3AVi9Tg9Uo68tJfuvoKvqKNWKkC5wPdSSdeBnizKZ6jT`

* bloXroute:
  * `HWEoBxYs7ssKuudEjzjmpfJVX7Dvi7wescFsVx2L5yoY`
  * `95cfoy472fcQHaw4tPGBTKpn6ZQnfEPfBgDQx6gcRmRg`
  * `3UQUKjhMKaY2S6bjcQD6yHB7utcZt5bfarRCmctpRtUd`
  * `FogxVNs6Mm2w9rnGL1vkARSwJxvLE8mujTv3LK8RnUhF`

* Astral:
  * `astrazznxsGUhWShqgNtAdfrzP2G83DzcWVJDxwV9bF`
  * `astra4uejePWneqNaJKuFFA8oonqCE1sqF6b45kDMZm`
  * `astra9xWY93QyfG6yM8zwsKsRodscjQ2uU2HKNL5prk`
  * `astraRVUuTHjpwEVvNBeQEgwYx9w9CFyfxjYoobCZhL`
  * `astraEJ2fEj8Xmy6KLG7B3VfbKfsHXhHrNdCQx7iGJK`
  * `astraubkDw81n4LuutzSQ8uzHCv4BhPVhfvTcYv8SKC`
  * `astraZW5GLFefxNPAatceHhYjfA1ciq9gvfEg2S47xk`
  * `astrawVNP4xDBKT7rAdxrLYiTSTdqtUr63fSMduivXK`

If you have additional providers to recommend for inclusion in the LUT, reach out to us.

### 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.