A MEV protection toggle tells you little until you know where it sends the order. Check the submission route, fallback behaviour and minimum received before changing your trade preset. Paying more for inclusion does not, by itself, keep a swap private.
In this article
What MEV protection actually changes
A sandwich attack uses your pending swap as the middle trade: an attacker buys ahead of it, your order moves the price further, and the attacker sells afterwards. The result is worse execution for your order. Solana has no shared public mempool, but that does not prevent infrastructure operators from observing transaction flow.
MEV protection can limit who receives the transaction or restrict how a supported service orders it. The scope depends on the provider and submission method. It does not change the pool's liquidity, remove your order's price impact or assess whether the token is legitimate.
Start with the preset you actually trade through. A manual buy, quick-buy button and automated order may have separate settings. A protection setting visible in one screen is not enough to establish how another order type is submitted.
Separate protection from priority fees and tips
| Setting | What it controls | What to check |
|---|---|---|
| Priority fee | An additional network charge that improves scheduling priority | The total fee for this order, including any automatic fee cap |
| Relay or block-engine tip | Payment associated with a submission service or bundle auction | The recipient, amount and route the app says it uses |
| Protected submission | Restrictions on transaction propagation or ordering | Covered order types, supported paths and fallback behaviour |
| Minimum received | The output floor accepted by an exact-input swap | The token amount you will accept for the money spent |
These controls solve different problems. Increasing a priority fee changes the incentive to include your transaction; it does not select a private route. A transfer to a tip address shows a payment, not the full path your signed order took before landing.
Check the fast mode and fallback path
A submission service can send the same transaction through several paths. That helps explain why a faster preset and a protected preset may behave differently. For example, bloXroute documents a fastest configuration with front-running protection disabled, and protected configurations that can wait when flagged leaders are ahead.
Before saving a preset, find out whether a timeout causes the app to keep waiting, expire the order or broadcast through another endpoint. If another path does not enforce the same protection, the original setting cannot cover that path. The same question applies when an app broadcasts through multiple providers at once.
Jito's jitodontfront mechanism restricts the position of marked transactions in bundles accepted by its block engine. Its scope is the block engine, not all transaction ordering across Solana. Treat that as a specific mechanism, rather than a network-wide guarantee.
Record the answers for your trading setup: which route is protected, which order types use it, and what happens when it cannot land promptly. If the app exposes none of that, a green toggle alone cannot verify the behaviour.
Keep the price limit when you enable protection
Inspect minimum received again after switching modes or refreshing a quote. For an exact-input swap, expected output and minimum acceptable output serve different purposes: one is the quoted result; the other is the floor the order may accept.
A protected route does not make an unusually wide tolerance harmless. You still permit execution down to the order's limit. Ordinary market movement can also worsen the result while the transaction is being delivered.
Compare the final token quantity with your original trade plan before signing. If you need the mechanics behind that difference, use the separate guide to slippage versus price impact. Raising the tolerance until an order lands changes the trade you agreed to make.
Check the fill without mistaking it for proof of protection
Save the quote, minimum received, protection mode and fee settings before submission. Afterwards, keep the transaction signature and reconcile the actual tokens received and SOL spent. The Solana explorer guide explains how to separate transfers, network fees and account deposits.
A successful transaction proves that it landed. A good fill does not prove that no one observed it; a bad fill alone does not establish a sandwich. Investigating a suspected attack requires the surrounding trades, their order, the affected pool and evidence linking the attacker's entry and exit.
Include separately charged relay tips when budgeting execution. Talentre's trading fee calculator accepts extra costs alongside platform and network charges. It helps compare the cost assumptions of your presets; it does not measure MEV saved or predict the execution price.
Keep the same order size and quote timestamp with your record. Comparing two trades placed at different times cannot isolate the benefit of a protection mode: the market, route and available liquidity may have changed between them.
Frequently asked questions
What is MEV protection on Solana?
It is a submission or ordering mechanism intended to reduce harmful extraction around a trade, such as sandwich attacks. Coverage depends on the service, order type and actual route. It is not a guarantee against every form of adverse execution.
Does a higher priority fee stop sandwich attacks?
A priority fee affects transaction scheduling incentives. It does not make the transaction private or establish the protection rules of its submission path. Check the route separately from the fee.
Does a Jito tip prove that my swap was protected?
No. The payment alone does not establish how the app propagated your order or which protection mechanism was applied. Check the submission method and any fallback paths used for that order.
Why can a protected swap take longer to land?
Some protected modes restrict eligible paths or wait rather than send to particular leaders. That can reduce immediate delivery options. Read the mode-specific behaviour before replacing it with a faster preset.
Can I use higher slippage with MEV protection?
Protection does not replace the minimum output condition of your swap. A wider tolerance still allows a worse fill, including from ordinary price movement. Set the output limit from what you accept receiving.
Does MEV protection prevent rug pulls?
No. Transaction propagation and ordering do not remove token authorities, secure pool liquidity or prevent holders from selling. Those require separate token and market checks.
Questions or corrections? Contact the Talentre team.


