MEV Protection
MEV (Maximal Extractable Value) attacks like front-running and sandwich attacks can cause significant losses for DeFi transactions. Trading Boost provides free MEV protection through Jito's private transaction channels.
Why Choose ZAN's Anti-MEV Protection?
Among numerous Solana transaction acceleration services, ZAN stands out with its superior technical architecture and innovative protection mechanisms, significantly reducing the risk of sandwich attacks. We don't just provide efficient transaction acceleration — we build a robust security defense for you.
- Industry-Leading Security Guarantees ZAN's anti-MEV protection solution offers industry-leading transaction security through a dual-layer protection mechanism:
- First Layer: Jito Integration Defense Mechanism
By integrating Jito's latest sandwich attack mitigation features into our transaction processing pipeline, we can effectively defend against attacks based on Jito bundles. This technological innovation ensures your transactions are prioritized within the block engine, fundamentally preventing them from being sandwiched by malicious transactions. - Second Layer: Intelligent Validator Detection System
ZAN's unique intelligent validator detection system continuously monitors validator behavior across the Solana network. Through big data analysis, we can accurately identify and avoid malicious validator nodes, ensuring your transactions execute only within secure and trusted network environments.
How It Works
Trading Boost's MEV protection leverages Jito Block Engine's specific address transfer mechanism:
- When MEV protection is enabled, transactions are routed through Jito's private mempool rather than the public mempool.
- Searchers cannot see or exploit your transaction before it reaches the chain.
- Transactions are submitted directly to validators via Jito's private channels.
Comparison with Public Submission
| Dimension | Public Submission (No MEV Protection) | MEV Protection Enabled |
|---|---|---|
| Transaction Visibility | Enters public mempool, visible to all | Only through Jito private channels, invisible to searchers |
| Front-running Risk | High (especially dangerous for large swaps) | Very low |
| Sandwich Attack Risk | High | Very low |
| Latency | Baseline latency | May add minimal additional latency |
| Cost | No additional fees | No additional fees |
How to Enable
Append ?anti-mev=true to any Trading Boost endpoint URL:
http://booster-sg.zan.top/node/v1/solana/mainnet/<YOUR_API_KEY>/tips?anti-mev=true
Step 1: Configure Jito Protection
In your Solana transaction instructions, simply add a valid public key address starting with jitodontfront to activate Jito's native protection mechanism. This simple configuration tells the blockchain network that your transaction requires special protection. Any transaction bundles containing this account will be intelligently filtered, ensuring your transaction is positioned safely.
Technical Tip:Using Jito's protection features won't impact your transaction confirmation speed, achieving a perfect balance between security and efficiency. See official documentation.
Step 2: Enable Anti-MEV Parameter
When submitting transactions through ZAN, simply add the anti-mev=true parameter to your API request URL to activate our proprietary validator protection system. ZAN maintains a blacklist of known malicious leaders. This parameter tells the ZAN system to perform security checks on the current block leader. If potential risks are detected, we automatically forward transactions to the next safe available validator node, avoiding potential attacks.
Usage Scenario Recommendations
| Scenario | Recommendation | Reason |
|---|---|---|
| DeFi swaps (especially large) | Highly recommended | Sandwich attack slippage losses typically far exceed latency costs |
| Large token purchases | Recommended | Prevents price being pushed up by front-running |
| NFT minting | Optional | Depends on whether mint mechanism involves price-sensitive operations |
| Small transfers | Not needed | Unprofitable for attackers |
| Ultra-low latency arbitrage | Consider disabling | Additional latency from private routing may affect arbitrage windows |
Technical Deep Dive
How Sandwich Attacks Operate
To understand our protection solution, first understand how sandwich attacks work. Essentially, this is a market manipulation strategy where attackers profit by inserting their own transactions before and after user transactions:
Attack process involves three steps:
- Forward Transaction: Attacker buys target assets before user transaction executes
- User Transaction: User's normal transaction executes
- Backward Transaction: Attacker immediately sells assets after user transaction completes
Through this "sandwiching" strategy, attackers profit from price movements caused by user transactions, while users are forced to transact at unfavorable prices, incurring financial losses.
ZAN's Dual Protection System
Our protection solution addresses two main sandwich attack methods with corresponding countermeasures:
- Defending Against Jito Bundle Attacks:
For attacks leveraging Jito's bundle mechanism, we integrate Jito's official protection features. When transactions containingjitodontfrontaccounts are detected, the block engine enforces special ordering rules, ensuring these transactions cannot be used as attack tools. - Defending Against Regular Transaction Ordering Attacks:
For attacks using regular transaction ordering, ZAN's intelligent validator detection system plays a crucial role. With rich network data and advanced monitoring capabilities, we can identify and avoid validator nodes exhibiting malicious behavior in real-time.
Code Examples
Enabling MEV protection only requires modifying the endpoint URL:
// Without MEV protection
const endpoint = 'http://booster-sg.zan.top/node/v1/solana/mainnet/<AK>/tips';
// With MEV protection — simply append ?anti-mev=true
const endpointWithMev = 'http://booster-sg.zan.top/node/v1/solana/mainnet/<AK>/tips?anti-mev=true';
// Remaining code stays exactly the same
const connection = new Connection(endpointWithMev, 'confirmed');
For complete code examples, see Tips Mode Integration Guide .
Updated about 2 hours ago
