atomic-bundle-debug

Diagnoses failed Jito bundles and maps symptoms to concrete repair actions.

15|2|Updated May 19, 2026
One-click install
npx skills add https://github.com/nirholas/atomic --skill atomic-bundle-debug-nirholas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: atomic-bundle-debug
Source: https://github.com/nirholas/atomic/tree/main/skills/bundle-debug
Command: npx skills add https://github.com/nirholas/atomic --skill atomic-bundle-debug-nirholas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jito bundles on Solana fail for a small set of well-defined reasons, but the error messages are cryptic and the failure modes (rejected, simulated-failed, silently dropped, landed-but-reverted) are hard to distinguish. This Skill turns a vague report like "the bundle didn't land" into a specific root cause and a concrete next command in under a minute. ## Core Features & Use Cases - Symptom-to-cause mapping: A decision flow and diagnosis table covering sendBundle errors (Invalid, tip-account lock failures, simulation failures), silent drops, and landed-but-reverted bundles. - Status classification workflow: Uses tools/check-bundle-status.ts with a bundle UUID to classify bundles as LANDED, PROCESSED, PENDING, or UNKNOWN, and explains what each state means operationally. - Tip economics guidance: Concrete tip sizing recommendations per scenario (fee collection, standard launch, sniper competition, leaked-key rescue) plus regional block-engine endpoint fallbacks. - Use Case: Your fire-jito.js launch script returned "Bundles must write lock at least one tip account". The Skill identifies stale hardcoded tip accounts as the cause and directs you to run tools/check-tip-accounts.ts and patch the account list. ## Quick Start Ask the assistant to diagnose why my Jito bundle did not land, given the error message or bundle UUID from my script output.

Frequently Asked Questions about atomic-bundle-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why did my Jito bundle not land on Solana?▼

Jito bundles fail to land for a few common reasons: the tip is below the current floor, the bundle was outbid by a competing bundle, or it was dropped after acceptance during congestion. Check the bundle UUID with getBundleStatuses; if it stays PENDING for 10+ slots, re-submit with a 2-5x higher tip.

How do I check the status of a Jito bundle by UUID?▼

Run `npx tsx tools/check-bundle-status.ts <uuid>` to query the bundle status. It classifies the bundle as LANDED, PROCESSED, PENDING, or UNKNOWN, and you can poll it in a loop until it reaches a terminal state.

What does "Bundles must write lock at least one tip account" mean?▼

This error means the hardcoded tip-account list in your script no longer matches the live Jito tip accounts, which rotate over time. Run `npx tsx tools/check-tip-accounts.ts` to get the current list and update the JITO_TIP_ACCOUNTS constant in your submission script.

How much should I tip for a Jito bundle?▼

Tip size depends on the scenario: 0.001-0.003 SOL for off-peak fee collection, 0.005 SOL for a standard launch, and 0.01-0.05 SOL when competing with snipers. Above 0.05 SOL per bundle the cost usually exceeds the value of one attempt, so recheck the inner transaction validity first.

Why did my bundle land but the transaction had no effect?▼

A bundle can report LANDED while its inner transaction reverted on-chain, shown as a non-null err.Err in getBundleStatuses. Alternatively, another transaction changed the state first in the same slot, so your transaction executed against an already-empty vault or stale state.

Can I use a different Jito block engine region when the default endpoint fails?▼

Yes, Jito operates regional block-engine endpoints including amsterdam, frankfurt, ny, tokyo, and slc. If the default endpoint returns Invalid or 5xx errors consistently, switch to a region closer to the current leader by setting the endpoint URL in your script or status-check tool.