agiprolabs/claude-trading-skills/jito-bundles
Claude Code and agent skill by agiprolabs/claude-trading-skills
- community
Checking that the SKILL.md file is still in the repository.
Jito bundle submission for MEV protection on Solana — bundle building, tip strategies, block engine endpoints, and landing rate optimization
Install
npx vskill@latest install agiprolabs/claude-trading-skills/jito-bundlesSKILL.md
Jito Bundle Submission for Solana
Jito bundles allow you to submit up to 5 Solana transactions that execute atomically — either all land in the same slot or none do. This is the primary mechanism for MEV protection and competitive transaction execution on Solana. Approximately 85%+ of Solana validators run the Jito-modified client, making bundles the standard for reliable, front-run-resistant execution.
EXECUTION SKILL — SAFETY WARNING: Submitting bundles spends real SOL on tips. Always test with--demomode first. Never submit bundles with real funds without explicit confirmation. Default to simulation/dry-run in all scripts and examples.
When to Use Bundles
| Scenario | Use Bundle? | Why | |
|---|---|---|---|
| Swap on illiquid token | Yes | Prevents sandwich attacks | |
| Multi-step arbitrage | Yes | Atomic execution prevents partial fills | |
| Liquidation | Yes | Competitive — tip determines priority | |
| Simple SOL transfer | No | Priority fees are cheaper and sufficient | |
| Time-insensitive swap | Maybe | Bundles cost tips; priority fees may suffice | |
| NFT mint / competitive action | Yes | Guarantees ordering within the slot |
Core Concepts
Bundle Anatomy
A Jito bundle is a JSON-RPC request containing 1-5 base58-encoded signed transactions. The transactions execute sequentially and atomically within a single slot.
Tip Mechanism
Tips are SOL transfers to one of Jito's 8 tip accounts. The tip incentivizes validators to include your bundle.
Tip accounts are fetched dynamically via getTipAccounts. Rotate through them to distribute load.
Block Engine Endpoints
Jito operates geographically distributed block engines. Choose the one closest to your infrastructure:
| Region | Endpoint | |
|---|---|---|
| New York | https://mainnet.block-engine.jito.wtf | |
| Amsterdam | https://amsterdam.block-engine.jito.wtf | |
| Frankfurt | https://frankfurt.block-engine.jito.wtf | |
| Tokyo | https://tokyo.block-engine.jito.wtf |
All endpoints accept JSON-RPC over HTTPS on port 443. The /api/v1/bundles path handles bundle operations.
API Methods
sendBundle
Submit a bundle of up to 5 transactions.
getBundleStatuses
Check the landing status of submitted bundles (up to 5 bundle IDs per request).
getTipAccounts
Fetch the current list of Jito tip accounts.
getInflightBundleStatuses
Check status of bundles that haven't landed yet (in-flight).
Bundle Construction Pattern
A typical bundle for a protected swap:
Tip Sizing Guide
| Scenario | Tip Range (lamports) | Tip Range (SOL) | |
|---|---|---|---|
| Normal swap (low urgency) | 1,000 - 10,000 | 0.000001 - 0.00001 | |
| Normal swap (standard) | 10,000 - 50,000 | 0.00001 - 0.00005 | |
| Competitive action (arb, liquidation) | 50,000 - 500,000 | 0.00005 - 0.0005 | |
| Highly competitive (NFT mint, MEV) | 500,000 - 5,000,000 | 0.0005 - 0.005 | |
| Emergency (must land this slot) | 5,000,000+ | 0.005+ |
Dynamic tip calculation based on recent tip levels:
Common Errors and Fixes
| Error | Cause | Fix | |
|---|---|---|---|
Bundle dropped (slot expired) | Bundle didn't land within 2 slots | Retry with fresh blockhash; consider higher tip | |
Transaction simulation failed | A tx in the bundle would fail on-chain | Simulate each tx individually to find the failing one | |
Bundle already processed | Duplicate bundle ID | Expected on retry; check status instead | |
Rate limited | Too many requests to block engine | Back off; rotate between block engine endpoints | |
Invalid transaction | Malformed or unsigned transaction | Verify all txs are signed and base58-encoded | |
Blockhash not found | Stale blockhash | Use getLatestBlockhash with finalized commitment |
Landing Rate Optimization
Strategies to maximize bundle landing probability:
- Multi-region submission: Send the same bundle to multiple block engines simultaneously. The first to reach the current leader wins.
- Fresh blockhash: Use
getLatestBlockhashwithconfirmedcommitment immediately before building. Stale blockhashes are the #1 cause of dropped bundles.
- Retry with backoff: If a bundle doesn't land within 2-3 seconds, rebuild with a fresh blockhash and resubmit. Do NOT resubmit with the same blockhash.
- Adequate tipping: Under-tipped bundles are deprioritized. Monitor the network's tip distribution and tip at or above the 50th percentile for your urgency level.
- Minimal bundle size: Fewer transactions = less simulation time = higher landing rate. Use single-transaction bundles when possible.
Safety Checklist (Execution)
Before submitting any bundle with real funds:
- [ ] Simulated all transactions individually via
simulateTransaction - [ ] Verified tip amount is reasonable (not accidentally SOL instead of lamports)
- [ ] Confirmed blockhash is fresh (< 60 seconds old)
- [ ] Verified all transactions are properly signed
- [ ] Checked wallet balance covers all transaction costs + tip
- [ ] Tested with devnet or --demo mode first
- [ ] Set maximum tip cap to prevent accidental overpayment
Files
References
references/bundle_api.md— Complete JSON-RPC API reference with request/response schemas and error codesreferences/tip_strategies.md— Tip calculation strategies, dynamic tipping, cost optimizationreferences/best_practices.md— Bundle construction patterns, landing rate optimization, common pitfalls
Scripts
scripts/build_bundle.py— Bundle construction with tip instruction;--demomode builds but does not submitscripts/check_bundle_status.py— Bundle status checking and tip account fetching;--demomode uses mock responses
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/jito-bundles/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/agiprolabs/claude-trading-skills/jito-bundles)