> For the complete documentation index, see [llms.txt](https://use.temporal.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://use.temporal.xyz/nozomi/tipping-and-faq.md).

# Tipping

## Overview

Every Nozomi transaction must include a tip — a standard Solana system transfer instruction to one of the Nozomi tip addresses. The minimum tip is **0.001 SOL**.

You only pay when your transaction lands. The tip is an instruction inside your transaction, so if the transaction fails, the tip is never charged. This means you can intentionally fail a transaction if, for example, you detect that someone else already captured the opportunity you were targeting.

## How Tips Are Used

| Delivery path      | What happens                             |
| ------------------ | ---------------------------------------- |
| Jito validator     | Entire tip is forwarded to Jito          |
| Harmonic bundles   | Tip is forwarded to Harmonic             |
| Staked connections | Tip pays for Nozomi's staked connections |

## Tip Priority

Nozomi queues transactions by tip amount — **higher tips land faster**. When multiple transactions compete for the same slot, the highest tipper wins.

Check the [live tip percentile dashboard](https://temporalxyz.retool.com/p/nozomi-tips/defaultPage) to see what others are tipping right now.

## Compute Unit Price

The tip controls your priority within Nozomi's queue. Once Nozomi delivers your transaction to the Solana scheduler, the **compute unit price** determines its on-chain ordering.

Set your compute unit price to at least **1,000,000 micro-lamports** for competitive performance.

## Retries

Nozomi automatically retries your transaction until it is either confirmed or the blockhash expires. Higher-tipped transactions are retried more aggressively. You do not need to implement retry logic on your end.

## Tip Addresses

Send your tip to any one of the addresses below. **Rotate to a different random address for each transaction** — this avoids write lock contention on a single account and improves landing rates.

| #  | Address                                       |
| -- | --------------------------------------------- |
| 1  | `TEMPaMeCRFAS9EKF53Jd6KpHxgL47uWLcpFArU1Fanq` |
| 2  | `noz3jAjPiHuBPqiSPkkugaJDkJscPuRhYnSpbi8UvC4` |
| 3  | `noz3str9KXfpKknefHji8L1mPgimezaiUyCHYMDv1GE` |
| 4  | `noz6uoYCDijhu1V7cutCpwxNiSovEwLdRHPwmgCGDNo` |
| 5  | `noz9EPNcT7WH6Sou3sr3GGjHQYVkN3DNirpbvDkv9YJ` |
| 6  | `nozc5yT15LazbLTFVZzoNZCwjh3yUtW86LoUyqsBu4L` |
| 7  | `nozFrhfnNGoyqwVuwPAW4aaGqempx4PU6g6D9CJMv7Z` |
| 8  | `nozievPk7HyK1Rqy1MPJwVQ7qQg2QoJGyP71oeDwbsu` |
| 9  | `noznbgwYnBLDHu8wcQVCEw6kDrXkPdKkydGJGNXGvL7` |
| 10 | `nozNVWs5N8mgzuD3qigrCG2UoKxZttxzZ85pvAQVrbP` |
| 11 | `nozpEGbwx4BcGp6pvEdAh1JoC2CQGZdU6HbNP1v2p6P` |
| 12 | `nozrhjhkCr3zXT3BiT4WCodYCUFeQvcdUkM7MqhKqge` |
| 13 | `nozrwQtWhEdrA6W8dkbt9gnUaMs52PdAv5byipnadq3` |
| 14 | `nozUacTVWub3cL4mJmGCYjKZTnE9RbdY5AP46iQgbPJ` |
| 15 | `nozWCyTPppJjRuw2fpzDhhWbW355fzosWSzrrMYB1Qk` |
| 16 | `nozWNju6dY353eMkMqURqwQEoM3SFgEKC6psLCSfUne` |
| 17 | `nozxNBgWohjR75vdspfxR5H9ceC7XXH99xpxhVGt3Bb` |

## Private Tip Addresses

For users who need dedicated tip addresses, Nozomi can generate private tip addresses that are exclusive to your project. These addresses are not shared with other users and provide additional isolation for your transactions.

Private tip addresses can be created from the Nozomi dashboard under the **Tip Accounts** page.

## Front-Running Protection

Nozomi offers a Front Running Protection mode that routes your transaction exclusively through a whitelist of trusted validators (Helius, Coinbase, etc.), preventing it from being seen by adversarial validators.

For additional protection on swaps:

* Set a strict slippage tolerance.
* Calculate and enforce `minAmountOut` in your transaction instructions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://use.temporal.xyz/nozomi/tipping-and-faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.