Transaction Modes & MEV

QZAR currently exposes two transaction modes: sample and mev (current only jito for Solana). They change how a signed transaction is prioritized and submitted.

sample

• Standard transaction submission
• Uses priority-fee settings
• QZAR can apply dynamic compute limits and recommended/turbo priority levels
• The transaction may be visible through the ordinary submission path before confirmation

mev

• Uses the submission path with a tip
• Designed for block-engine delivery and reduced public exposure compared with ordinary broadcasting
• Transaction not visible through the ordinary submission path
• Still depends on route validity, balance, slippage, network state, and block-engine acceptance

What MEV risk means

MEV risk means the danger of losing money when bots or miners reorder, add, or skip your trades on a blockchain. This manipulation hurts your execution price.

Example MEV risks:

• Sandwich: an attacker buys before a visible trade and sells after it, worsening the victim's price
• Front-running: A bot spots your pending buy order and pays a higher fee to buy the asset first

Why it matters?

It causes slippage and gives you a worse final price than expected. It transfers value from regular traders to searchers and validators.

Choose a mode

Use sample when ordinary execution and dynamic priority are appropriate. Consider mev when private block-engine delivery is important enough to justify the tip and you understand the trade-offs.

Always verify the final signature and actual balance changes.