> For the complete documentation index, see [llms.txt](https://graphdex-1.gitbook.io/graphdex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://graphdex-1.gitbook.io/graphdex-docs/trading/validator-bribe.md).

# Validator Bribe

**An extra execution incentive — separate from Priority, layered on top.**

<div align="center"><figure><img src="/files/aVYqE79eKRLE9y13C7Y5" alt="Trade Strategy panel — Priority / Bribe / Slippage"><figcaption><p>Bribe sits between Priority and Slippage in the Trade Strategy row.</p></figcaption></figure></div>

Bribe is a second execution lever in the **Trade Strategy** row, separate from Priority. Where Priority is the standard validator tip, Bribe is an additional incentive — designed for users who want more control over execution in competitive or fast-moving conditions.

During review the value shown was `0.0002 SOL`. The terminal exposes Bribe for advanced execution tuning; default users rarely need to touch it.

{% hint style="success" %}
**Reach for Bribe deliberately**

Use Bribe when Priority alone isn't winning inclusion — not as a routine setting. Stacked execution costs add up fast.
{% endhint %}

## What Bribe Is For

* Extra incentive on top of the standard Priority Fee.
* Separate cost, not a substitute for Priority.
* Aimed at high-contention scenarios — token launches, news-driven moves, sniper environments.
* Inherited from Speed Presets (Slow / Fast / Turbo) when you switch a preset.

## What Bribe Does NOT Do

Using a Bribe does not guarantee:

* Successful execution.
* First-block inclusion.
* A better fill price.
* Protection from volatility.
* Protection from failed transactions.

Treat Bribe as a probabilistic edge, not insurance.

## When to Use It

* You've already raised Priority and still see inclusion delays.
* You're competing for a tight launch window.
* You're running a sniper-style setup where seconds matter.
* You've accepted the cost premium and reviewed the rest of your trade strategy.

For routine trades on liquid pairs, **leave Bribe at the default**.

## Practical Guidance

* Keep Bribe conservative unless you understand the execution tradeoff.
* Review it together with Priority and Slippage — they're three pieces of the same profile.
* Be especially careful when using Bribe with **Quick Buy** — instant submission with stacked incentives can produce surprising costs.
* Clear or reduce the value when you no longer need aggressive execution settings.

## Bribe Risk

Combined Priority + Bribe on a failed transaction is double cost for zero outcome. The "I forgot to clear Turbo" failure mode is real:

* Failed transactions consume both Priority and Bribe.
* Aggressive Bribe on small positions can exceed the position's profit potential.
* MEV bots compete on bribes too — being slightly above them costs more than you think.

See [Risk of Fast Execution Settings](/graphdex-docs/trading/risk-of-fast-execution-settings.md) and [Execution Risks](/graphdex-docs/trading/execution-risks.md) for full coverage.

## More to Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/cvGJYoD9UstDDnIsicyY"><strong>Priority Fee</strong></a></td><td>The standard validator tip — pair with Bribe.</td><td><a href="/files/aVYqE79eKRLE9y13C7Y5">/files/aVYqE79eKRLE9y13C7Y5</a></td></tr><tr><td><a href="/pages/uJCvy09y2FG1Kk27Bpz7"><strong>Slippage</strong></a></td><td>Price tolerance — the third lever in the row.</td><td><a href="/files/aVYqE79eKRLE9y13C7Y5">/files/aVYqE79eKRLE9y13C7Y5</a></td></tr><tr><td><a href="/pages/OMivUziEbyoA9jTgesYW"><strong>Risk of Fast Execution</strong></a></td><td>What goes wrong when Priority + Bribe stack on aggressive presets.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr></tbody></table>

{% hint style="info" %}
Bribe is the most context-dependent of the three speed levers. When in doubt, lower it. See [Trading Settings Overview](/graphdex-docs/trading/trading-settings-overview.md) for how the three settings work together.
{% endhint %}

## FAQs

<details>

<summary>What's the difference between Priority and Bribe?</summary>

Priority is the standard validator tip Solana exposes. Bribe is a separate execution incentive on top. Both raise cost; both can improve inclusion odds in different ways.

</details>

<details>

<summary>Does Bribe guarantee my transaction lands first?</summary>

No. Like Priority, it's probabilistic. Other bidders can outbid you.

</details>

<details>

<summary>Will I pay Bribe on a failed trade?</summary>

Yes — the cost is consumed regardless of outcome.

</details>

<details>

<summary>What's a reasonable default Bribe value?</summary>

The terminal defaults to a small value (e.g. \`0.0002 SOL\`). For routine liquid-pair trades, default or zero is usually fine. Raise it only when you've identified competitive inclusion as the bottleneck.

</details>

<details>

<summary>Can I disable Bribe entirely?</summary>

Set the field to \`0\` to skip the bribe component. Priority alone may be enough for normal market conditions.

</details>


---

# 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://graphdex-1.gitbook.io/graphdex-docs/trading/validator-bribe.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.
