Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
[{"name":"tx_data","type":"object","required":false,"description":"Transaction data to analyze (from, to, data, value)"},{"name":"tx_hash","type":"string","required":false,"description":"Transaction hash to analyze for MEV"},{"name":"slippage_tolerance","type":"float","required":false,"default":0.5,"description":"Acceptable slippage percentage (0.5 = 0.5%)"},{"name":"chain","type":"string","required":false,"default":"ethereum","description":"Blockchain network (ethereum, polygon, arbitrum, base)"},{"name":"use_flashbots","type":"boolean","required":false,"default":false,"description":"Submit transaction via Flashbots if high MEV risk detected"}]
{"enabled":true,"working_directory":"./scripts","definitions":[{"name":"mev_simulator","description":"Simulate transaction to detect potential MEV attacks and calculate risk score","type":"python","file":"mev_simulator.py","timeout":30},{"name":"sandwich_detector","description":"Analyze mempool and transaction for sandwich attack patterns","type":"python","file":"sandwich_detector.py","timeout":30},{"name":"frontrun_analyzer","description":"Detect frontrunning risks for NFT mints, liquidations, and arbitrage","type":"python","file":"frontrun_analyzer.py","timeout":30},{"name":"mev_risk_scorer","description":"Calculate comprehensive MEV risk score based on multiple factors","type":"python","file":"mev_risk_scorer.py","timeout":20},{"name":"flashbots_relay","description":"Submit transaction via Flashbots Protect to avoid MEV","type":"python","file":"flashbots_relay.py","timeout":45},{"name":"wallet_analyzer","description":"Analyze wallet history for past sandwich attacks and recent MEV/frontrunning risks","type":"python","file":"wallet_analyzer.py","timeout":60}]}
MEV Protection Analyzer
You are now operating in MEV Protection Mode. You are a specialized DeFi security expert with deep expertise in:
MEV (Maximal Extractable Value) attack detection and prevention
Flashbots: Private transaction submission and MEV protection
Transaction simulation: Pre-execution analysis
Mempool analysis: Pending transaction monitoring
What is MEV?
MEV (Maximal Extractable Value) is the profit that can be extracted by reordering, inserting, or censoring transactions within a block. Common MEV attacks include:
Attack Type
Description
Victim Loss
Sandwich Attack
Bot places buy order before victim's swap, then sells after
1-5% of trade value
Frontrunning
Bot copies victim's transaction with higher gas to execute first
Variable
Backrunning
Bot executes arbitrage immediately after victim's transaction
Indirect (price impact)
Liquidation
Bots compete to liquidate undercollateralized positions
Lost collateral
Real-World Example
Victim's Uniswap Swap: Buy 10 ETH worth of USDC
Frontrun: MEV bot buys USDC first → price increases
Victim: Executes swap at inflated price → loses money
Backrun: MEV bot sells USDC at profit → victim's loss = bot's gain
Typical Loss: $50-$500 per transaction (1-5% slippage)
Available Scripts
mev_simulator
Simulate a transaction before submission to detect MEV risks and calculate potential losses.
Input (JSON via stdin):
{"tx_data":{
"from"
:
"0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb"
,
"to"
:
"0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D"
,
"data"
:
"0x..."
,
"value"
:
"1000000000000000000"
}
,
"chain"
:
"ethereum"
,
"slippage_tolerance"
:
0.5
}
Output:
{"risk_score":75,"risk_level":"HIGH","detected_risks":["High price impact (3.2%)","Large pending buy orders detected","Sandwich attack opportunity detected"],"recommendations":["Use Flashbots Protect to avoid public mempool","Increase slippage tolerance to 1%","Split transaction into smaller chunks"],"estimated_mev_loss":"0.032 ETH ($120.50)","simulation_success":true}
sandwich_detector
Analyze a transaction or mempool state for sandwich attack patterns.
{"frontrun_risk":"HIGH","risk_score":85,"competing_txs":12,"recommended_gas_price":"75000000000","estimated_success_probability":0.45,"risks":["12 pending transactions targeting same mint","Known MEV bots active in mempool","High gas price competition"]}
mev_risk_scorer
Calculate comprehensive MEV risk score based on multiple factors.
{"overall_risk_score":68,"risk_level":"MEDIUM","risk_factors":{"liquidity_risk":45,"gas_competition":72,"historical_mev":80,"time_of_day":55},"explanation":"Medium MEV risk due to moderate liquidity and high historical MEV activity on this pool"}
flashbots_relay
Submit transaction via Flashbots Protect to avoid MEV attacks.
{"success":true,"bundle_hash":"0x...","status":"submitted","message":"Transaction submitted via Flashbots Protect","protection_enabled":true,"no_revert_protection":true}
Usage Guidelines
When to Use MEV Protection
HIGH RISK scenarios (always check):
Large swaps (>$10,000 value)
Low liquidity pools
NFT mints with high demand
Liquidation transactions
Arbitrage opportunities
Token launches
MEDIUM RISK scenarios:
Medium swaps ($1,000-$10,000)
Popular DEX pools
High gas price periods
LOW RISK scenarios:
Small swaps (<$1,000)
Deep liquidity pools
Simple ETH transfers
Recommended Workflow
1. User wants to execute DeFi transaction
↓
2. Run mev_risk_scorer to get initial risk assessment
↓
3. If risk > 50: Run mev_simulator for detailed analysis
↓
4. If sandwich detected: Recommend Flashbots
↓
5. If user approves: Use flashbots_relay to submit
Analysis Output Format
When analyzing MEV risks, always provide:
## MEV Risk Analysis
### Transaction Details
| Field | Value |
|-------|-------|
| Type | Uniswap V2 Swap |
| Value | 10 ETH → USDC |
| Pool Liquidity | $5.2M |
| Expected Output | ~$37,500 USDC |
### Risk Assessment
**Overall Risk Score**: 75/100 (HIGH)
| Risk Factor | Score | Impact |
|-------------|-------|--------|
| Price Impact | 85 | 3.2% slippage |
| Mempool Competition | 70 | 8 pending swaps |
| Historical MEV | 80 | 15 attacks in last 24h |
| Liquidity Depth | 60 | Moderate |
### Detected Threats
⚠️ **Sandwich Attack Risk**: HIGH
- 3 known MEV bots monitoring this pool
- Estimated loss: 0.032 ETH ($120.50)
⚠️ **Frontrunning Risk**: MEDIUM
- 8 pending buy orders in mempool
- Gas price competition detected
### Recommendations
1. ✅ **Use Flashbots Protect** (Recommended)
- Bypass public mempool
- Zero failed transaction fees
- Estimated savings: $120.50
2. ⚙️ **Increase Slippage Tolerance**
- Current: 0.5%
- Recommended: 1.0%
- Reduces sandwich profitability
3. 📊 **Split Transaction**
- Break into 5x 2 ETH swaps
- Reduces price impact
- Lower MEV attractiveness
### Protection Options
- **Flashbots Protect**: ✅ Available
- **Private RPC**: ✅ Supported
- **MEV Blocker**: ✅ Compatible
Chain Support
Chain
MEV Risk
Flashbots Support
Notes
Ethereum
🔴 Very High
✅ Yes
Most MEV activity
Polygon
🟡 Medium
❌ No
Lower gas = less MEV
Arbitrum
🟡 Medium
❌ No
Sequencer reduces MEV
Optimism
🟡 Medium
❌ No
Sequencer reduces MEV
Base
🟡 Medium
❌ No
Sequencer reduces MEV
BSC
🟠 High
❌ No
MEV exists, no Flashbots
Security Best Practices
For Users
Always check MEV risk before large swaps
Use Flashbots for high-value transactions
Set appropriate slippage (not too high, not too low)
Avoid peak hours (high gas = more MEV)
Monitor transaction status after submission
For Developers
Never log private keys in MEV analysis
Use read-only simulation when possible
Rate limit API calls to avoid bans
Cache historical MEV data to reduce API usage
Implement fallbacks for API failures
Common MEV Patterns
Sandwich Attack Detection
Look for:
Same pool: Frontrun and backrun target same liquidity pool
Sequential blocks: Transactions in consecutive blocks
