LIVE ON WORLDCUP/SOL POOL · MAINNET

Landing Solana
transactions
under extreme contention.

A developer-first execution SDK. Decode account contention with sub-100ms Yellowstone telemetry, optimize compute, and self-heal drops with AI diagnostics — to win block space, every slot.

@autoland/core v1.2.0 Jito Bundles Yellowstone gRPC MIT Licensed
0
% landing rate
0
ms p50 telemetry
0
× tip efficiency
0
core pipelines
Section 01 — Technical context

How Jito and writable accounts actually work.

Solana's parallel engine handles separate state paths, but execution clashes when transactions compete to write to the same account. Jito coordinates this off-chain in three steps.

01

Bundle account locking

Jito's BundleAccountLocker extracts and locks all read/write accounts across a bundle, securing block-wide atomicity.

02

Conflict set grouping

Bundles requesting overlapping locks — trading bots competing for the same DLMM pool — are isolated into a Conflict Set.

03

Localized auctions

Only one conflicting bundle lands. Jito runs an off-chain priority auction; the top Priority Score wins.

Live · Conflict set grouping path
Tx 1 · Rebalancewrites: pool
Tx 2 · Arb botwrites: pool
Tx 3 · Swapperwrites: pool
→
JITO CONFLICT SET
WORLDCUP/SOL · pool lock
↳ off-chain priority auction
→
✓ LANDED
slot 429341336
Key insight — Standard RPC submission broadcasts to public mempools, exposing transactions to sandwich attacks and leader-level drops. AutoLand routes bypass this entirely via private Jito channels.
Section 02 — The auction

Denominator optimization wins auctions.

Inside a Jito Conflict Set, bundles are ranked by Priority Score — tip density per compute unit — not absolute tip.

Priority Score = Total Jito Tip (lamports) ÷ Compute Units Requested

Tx A · AutoLand optimized

Requested compute50,000 CU
Jito tip0.005 SOL
Priority score100 lamports/CU
✓ LANDED FIRST

Tx B · Default unoptimized

Requested compute1,400,000 CU
Jito tip0.070 SOL
Priority score50 lamports/CU
✕ DROPPED · OUTBID

Tx B pays a 14× higher absolute tip yet loses — because its CU denominator is bloated. AutoLand shrinks that denominator.

Interactive · Bid simulator

Move the sliders. Watch the auction shift.

Compete against a standard bot at 70M lamports / 1.4M CU (50 lamports/CU baseline).

Jito tip0.005 SOL
Compute units requested50,000 CU
tip:   5,000,000 lamports
cu:    50,000 units
bench: 50.00 lamports/CU
100
LAMPORTS / CU
✓ OUTBIDS COMPETITOR
Section 03 — The engine

Six layers, one contention engine.

AutoLand builds an active bidding profile for target accounts. Live gRPC streams feed tip scaling; global fee percentiles hold the floor when pools are quiet.

01

Telemetry

Yellowstone gRPC subscribes per-account.

02

Leader schedule

Times dispatch to Jito-supported slots.

03

CU resize

Pre-flight sim + 10% margin.

04

Dual bidding

Outbids under contention, p50 baseline otherwise.

05

LLM advisor

Diagnoses drops, stale hashes, retries.

06

Commitment

Tracks processed → confirmed → finalized.

[CLIENT] your-bot.tstypescript
// 1. Bot detects pool imbalance
const pool = await getDLMMPool(POOL_ADDR);

if (pool.priceChange > threshold) {
  // 2. Build rebalance txs
  const txs = await buildRebalanceTxs(pool);

  // 3. Hand batch to AutoLand
  const result = await autoland.submitBatch(txs, {
    targetPool: POOL_ADDR,
    outbidMultiplier: 1.15
  });
}
[SDK] execution pipelinetelemetry
[gRPC]       stream WORLDCUP/SOL
[gRPC]       competitor floor: 84.5 lamports/CU
[optim]      simulated: 41,200 CU
[optim]      envelope: 45,320 CU (+10%)
[bid]        Jito tip: 3,829,540 lamports
[dispatch]   → regional block engines
[jito]       ✓ landed slot 429341336
              attempt 1 · 100% confirmation
Feature · Multi-channel routing options

AutoLand Options: Normal vs. High Urgency

Developers can specify transaction urgency in AutoLand submit options. This guarantees cost-effective execution paths depending on the context:

[SDK] autoland-urgency-options.tstypescript
// Example 1: High Urgency transaction (DLMM rebalancing, arbitrage, liquidations)
const highResult = await autoland.submit(rebalanceTx, {
  urgency: "high" // Routes to the private Jito block engine stack with dynamic tip outbidding
});

// Example 2: Normal Urgency transaction (Standard token transfers, admin tasks, fee collections)
const normalResult = await autoland.submit(transferTx, {
  urgency: "normal" // Bypasses Jito tips entirely; dispatched directly to standard public RPC nodes
});

Urgency: "normal"

Public RPC Dispatcher

Target Transaction TypeSimple / non-time-sensitive (e.g. transfers, approvals)
Bypasses Jito TipYes (0 Jito tip paid)
Routing ChannelPublic Solana Mempool (sendRawTransaction)
Confirmation ModeStandard RPC slot tracking
ZERO TIP COST

Urgency: "high"

Jito Bidding Stack

Target Transaction TypeHigh-contention events (e.g. liquidations, HFTs, mints)
Bypasses Jito TipNo (dynamic bidding via telemetry)
Routing ChannelPrivate block engine channels (Jito Bundles)
Confirmation ModeSub-100ms Yellowstone gRPC streams
MAX LANDING PROBABILITY
Why this dual routing is critical: Liquidations, IDOs, and DLMM pool rebalances must land in a specific slot or they expire/get frontrun. Normal transactions (like transferring fees out of the bot or executing standard administrative commands) do not require microsecond-level speed. Forcing simple actions through the private Jito bundle stack would unnecessarily waste Jito tips, while sending high-contention actions to the public mempool would result in transaction drops and MEV exploitation.
Section 04 — Live console

Bundles landed on mainnet.

Real submissions, hashes verifiable on-chain. Each bundle is dispatched, tracked, and reconciled against Jito leader windows.

autoland@mainnet · ~/logs · stream
10:52:14 [gRPC] subscribed · WORLDCUP/SOL · depth 4
10:52:14 [leader] next Jito window · slot 429341333 · +1.2s
10:52:15 [optim] sim 41,200 CU → envelope 45,320 CU
10:52:15 [bid] floor 84.5 lam/CU · outbid → 97.2 lam/CU
10:52:15 [dispatch] bundle → ams · fra · nyc · tokyo
10:52:16 [jito] ✓ landed · slot 429341336 · attempt 1
10:52:16 [confirm] processed 412ms · confirmed 798ms
10:52:16 [gRPC] awaiting next contention window

Recent landed bundles

[ENTRY 01]

Bundle 82de89b4b61c088ce08137818628d924d088f6e9dc09be457fc6c408449fefc4

Finalized
Sub 429341336
➔
Proc 429341349
➔
Conf 429341349
➔
Final 429341349
Tip Paid6,851,610 lamports
Attempt1
OperationMeteora Remove Liquidity & Other & Meteora Add Liquidity
ConfirmationJito Stream
Signatures & Explorer Links
3s48PtttU1wuBu3msbq8WABBDsViEcAiCypswfH8nLcd3NiJ9eosSbNm7AxbAEiooKqPKB1T4BQHizkZ2VBHnbsZ Solscan ↗
4NKTCrZeXNc3zAWn8s1f7LaxPDkgbiAWuto9QiiqYwyK4i7oBfsLjsvSADxbCmHsPskdvPJL4LBDjkyKUp7m3jmY Solscan ↗
4pa2FYcgAcM4pQTGtAYFgpksN86U5LEJvoSrKs2BrNKui6vL7ik5ae3oue952EHm7Zx95KrMx2wtBZNpJGbLra5e Solscan ↗
[ENTRY 02]

Bundle 4858d2377ff9b7b621307c6ab0ab35e475dbbf81af3fd68237a42d19949a22ef

AI Recovered
Sub 429331685
➔
Proc 429331836
➔
Conf 429331836
➔
Final 429331836
Tip Paid15,000 lamports
Attempt3 (AI Retried)
OperationMeteora Remove Liquidity
ConfirmationJito Stream
AI Diagnostics & Action: Attempt 1 failed due to TIMEOUT (Blockhash expired or Jito fee war). The AI Advisor recovered by refreshing blockhash parameters and outbidding competitors to finalize successfully.
Signatures & Explorer Links
5tNGQ1tzy3BTwx7rG3qyXQeK5a5jDqMuDXTRS4cYktUzWiXMYGcSAaNmPxwqJdDTvviLWk678sXryGvphphAPqxC Solscan ↗
[ENTRY 03]

Bundle 96b8c42cfc5105edb8abad9a923f5c620e368a2c67daac5c0f1376c9c8337146

Finalized
Sub 429055156
➔
Proc 429055162
➔
Conf 429055162
➔
Final 429055162
Tip Paid11,588,776 lamports
Attempt1
OperationMeteora Remove Liquidity & Other & Meteora Add Liquidity
ConfirmationJito Stream
Signatures & Explorer Links
2FLUzdtGxE7EVcgDHAWtsn2ziTu6EYTNg6p2hEKZbqacog39uBd1xTRrLivepGdRe1BnBCwgzCksQYFtPVR6mHCY Solscan ↗
54r4SoHmybzaqzAjbHkKq8tLQSXrnJeQLBsQPbtErZmptJH6NLkrgaseksjvvejQEJrqJaBiq7rnKEtecyESFPCP Solscan ↗
5tte7g5hmrXnPSVJTxVo6aMa68cap1SdPgJddJ4d3BGJUnno8xMzKisANiBaL7eMeZKTPJoA4sGEMvrZoGyHP8kS Solscan ↗
[ENTRY 04]

Bundle 88759dd83e9a2ef46c607fe04e9e9f0f030ccf5f05600b75ea9bd8725a1c2b04

AI Recovered
Sub 429055014
➔
Proc 429055015
➔
Conf 429055015
➔
Final 429055015
Tip Paid15,000 lamports
Attempt3 (AI Retried)
OperationMeteora Remove Liquidity & Meteora Add Liquidity
ConfirmationJito Connection
AI Diagnostics & Action: Attempt 1 failed due to bundle_dropped (fallback RPC initiated — Forced public RPC fallback guardrail triggered after attempt 3). The AI Advisor recovered by refreshing blockhash parameters and outbidding competitors to finalize successfully.
Signatures & Explorer Links
3LenJ49MV9BWfooPPFyGGqiQWvfveAuJz419vpq9TLnnaGSJ3p5jqnUvFhtU6KVihaDi9Ab3s5atqZKugj85zaDj Solscan ↗
5VtctK5QfNMGS5Qf4ncPRpBv97hyVRjBMzruSfFK3FAacxkjcxEnEGD53RgYWF6KAUQfJ5itNKZzXrvTJ9J7XEzL Solscan ↗
[ENTRY 05]

Bundle 143efc2f1d80bdf5d108fce815b53e836d3ca19644270ff2da089f72d3a968cb

AI Recovered
Sub 429045955
➔
Proc 429045964
➔
Conf 429045964
➔
Final 429045964
Tip Paid15,000,000 lamports
Attempt5 (AI Retried)
OperationMeteora Remove Liquidity & Other & Meteora Add Liquidity
ConfirmationJito Stream
AI Diagnostics & Action: Attempt 1 failed due to TIMEOUT (Blockhash expired or Jito fee war). The AI Advisor recovered by refreshing blockhash parameters and outbidding competitors to finalize successfully.
Signatures & Explorer Links
4NuJjjK3wMbDN2zmUabSdi7d6cCPkKgH2KYbitFKdsQ9Wh9AqZTjCT7dUmjeDvJVkVtx6SDbNNegRnKHZnCz311G Solscan ↗
4p1YkwxPcQtpkEy9eNZ8mRonBrDhbKDEm3hw2NGAeZu5Gb25MtJtXe36A2Cak23kFq98b1U9UQZYMLaF4WWsM3f4 Solscan ↗
5zjwZtKxxTXriqxvPLpqL18N5p6GFDPdKbHCkZtidnKjhnyHjMDNF7Yw3HZQfRdL8ykYFnR4zAvzAqd3WEbgPFUM Solscan ↗
[ENTRY 06]

Bundle 308f6e9629d13bb7265c7b303694d624eb2d0a3aa159949de2f938946a3c5082

Finalized
Sub 428635810
➔
Proc 428635813
➔
Conf 428635813
➔
Final 428635813
Tip Paid10,375,682 lamports
Attempt1
OperationMeteora Remove Liquidity & Other & Meteora Add Liquidity
ConfirmationJito Stream
Signatures & Explorer Links
279GEZTKT4crCNPj4FzjNNYwQzZXPpvREEiBN8vmfEMFK2osd7YQqLosv1kbscSizRjgFLh4Zo5Ad12vH7oSQ2x9 Solscan ↗
2ZRTL6ZtqeQG6sD2tW8dH42NB35bjDFtn12GrpfkBcHSsco2Yx8TZDhJax4f2gWaUFVXESDqrXSYJMJrjH3VVtRG Solscan ↗
sa51npZvQfpwvQwF8Q8MeShKnXa6E9DZ1F4ogUJQ6norUhXNBz26tfqzU4gH8X6djQWNH1hwEueWEfe5AmmL55X Solscan ↗
[ENTRY 07]

Bundle 1c8d08b725913a93076c2f8b73984e052bbca48568cbe2ba9683d38fc81d2ad8

Finalized
Sub 428635758
➔
Proc 428635766
➔
Conf 428635766
➔
Final 428635766
Tip Paid10,417,111 lamports
Attempt1
OperationMeteora Remove Liquidity & Other & Meteora Add Liquidity
ConfirmationJito Stream
Signatures & Explorer Links
3wcVJPRR3sty4m8ZqbvaJ1SEh6HLUyPGYmjdeZ8v5mA2NjHAoJfSYN7kVD8piYn3nXPFvrskjX9nWkZxV5D1Nshk Solscan ↗
4Zeax1DQVYQnumee23rWppV1PxQ2WUjceHExZzUwYqcaeLNDiz93ZDnAX4UYf1B9DwPuw27NTGW7v7BQcAiCbv1u Solscan ↗
UWKJ6T2mHukPpPR9cW3hzubtYGdTgjWFqHoXSQYe9NcuCGByS4rw718NWxj8JdYJ3fHLfAPvgkfDctaQNzgzi7u Solscan ↗
[ENTRY 08]

Bundle 5f35b7cd873816221f672eecd6cfe691edab7b9c5e35216a59edb6afd2553ae0

Finalized
Sub 428632708
➔
Proc 428632712
➔
Conf 428632712
➔
Final 428632712
Tip Paid10,963,089 lamports
Attempt1
OperationMeteora Remove Liquidity & Other & Meteora Add Liquidity
ConfirmationPublic RPC Fallback
Signatures & Explorer Links
2Z59PQ5UxuuzeyQjHQ3yTYAogxGzi6nidQjXv5sUtFiGYJPcZGReP3tEL7D6yoY3ZRqxqR71shzey2BnEoKaeJq Solscan ↗
3e6gSbWn6xmnY4mW62YBWVgVpDhbcUfXZ2KMiXVhagtK1NhedKX18TZWj5BoZZtnKNW889v4YKi2kueZkkRmr1wf Solscan ↗
Uyh8o5cANS81tHK5huMexzycamZhHSGcKauwzdcc3q7VkmmBtvhhYxnb8364k6zTYfbxCrCDrWFEshdgeoBHifC Solscan ↗
[ENTRY 09]

Bundle 3bfbb722bb7b11aab8e4597e9659e11b95b91910630830e86548f32bf895c247

Finalized
Sub 428628204
➔
Proc 428628211
➔
Conf 428628211
➔
Final 428628211
Tip Paid6,052,744 lamports
Attempt1
OperationMeteora Remove Liquidity & Other & Meteora Add Liquidity
ConfirmationJito Stream
Signatures & Explorer Links
2PDtiALfQYC4xCLgS3Yzp53REaP7RuTQwPLDazfueX7jvqkgySioJdhdTx1K2hmWosm2trnwiJzajECRsaGkiiVm Solscan ↗
2fKXZA4rPRqP5yNanuwF3sapnYi8Y5EK1TSSVUVHCqZvFjCtXhuHexxvQmwgxk254Fp1m9DvhtuGpXtEf32V379i Solscan ↗
539jhaoRW4DkFMSSmyLFMwxcDrysZf242EK7YZXHbegcL22WseSz8u83rWTVoKBHsKVt5HbUBZBwT3G2ZejyUuGa Solscan ↗
[ENTRY 10]

Bundle 3bad93b2ad3c6d3bf41a0c04227f1d4c392ecd74e3c794e6d1678465bc9367a1

Finalized
Sub 428627097
➔
Proc 428627108
➔
Conf 428627108
➔
Final 428627108
Tip Paid6,503,220 lamports
Attempt1
OperationMeteora Remove Liquidity & Other & Meteora Add Liquidity
ConfirmationJito Stream
Signatures & Explorer Links
3FU6dfHxePAif4HGqR5pNc3578iGbM78oUCCVjQSo6s5dP2iF4efERjKvJfo6yQC8nFZxy6EQEC7goipD2zjokB6 Solscan ↗
3JFnUdi8bGEKQp5mp2nzNjsUXQb6jCGnTGvrcjTEUJxeKjCtYh1Gv3RQPGC8xuAeLoKnpNyp1QhF4PcvK1GASqGG Solscan ↗
4K2ei2eZtURL1Hk9TSvWhG3LbVz4wRN9kQDrs3QEJdTdp9vESpLPjb9tZe4SGVGx1neyFuKnW1DKPJJBBBCugjib Solscan ↗
Section 05 — Operational insights

Field notes from mainnet.

Answers to the network-level questions that surface during real contention runs.

Measures consensus vote propagation across the validator network.
  • Low-Congestion Slots: 400–800 ms (1–2 slots). Landed bundle 82de89b4...449fefc4 verified a processed-to-confirmed delta of **380 ms** in our logs.
  • Peak Congestion Behavior: 2+ seconds. Landed bundle 5f35b7cd...d2553ae0 verified a delta of **1,250 ms** (~3 slots) due to consensus propagation delay.
  • SDK action: AutoLand scales backpressure delays until consensus stabilizes.
Blockhashes are valid for 150 slots (~60s); finalized status takes ~13–15s.
  • Validity loss: A finalized hash burns 20–25% of its lifespan before signing.
  • Staleness risk: Congested slots stretch time. Trace 4858d237...949a22ef had a slot gap of **151 slots** (60.4s) before landing; a finalized hash would have expired on-chain.
  • SDK action: Queries blockhashes at confirmed and uses the AI Advisor to refresh the hash on attempt 3.
Jito bundles route off-chain to a specific validator. Skipped slot = dropped bundle.
  • Leader skip drop: In trace 88759dd8...5a1c2b04, attempt 1 was dropped because slot leader `429055014` skipped their block.
  • Multi-region & AI: AutoLand dispatches in parallel, detects the skipped slot drop, and has the AI Advisor recover to land on attempt 3.
  • Leader tracking: LeaderWindowDetector holds dispatch if the window is unfavorable.
No, a Jito UUID is a red herring—it does not solve drops under heavy mainnet congestion. Landing transactions is an optimization and fee pricing problem.
  • Bundle Optimization: We minimize requested Compute Units (CUs) via pre-flight simulations, maximizing our priority score.
  • Competitor Outbidding: AutoLand decodes competitor transactions via Yellowstone gRPC in real-time, scaling tips up to the p99 percentile during peak congestion.
Instead of using concurrent asynchronous event handlers (which trigger parallel loops and require mutex semaphores), AutoLand prevents concurrency races by design using a strict sequential promise chain.
  • Sequential Loop: The SDK core blocks and synchronously awaits the transaction's confirmation or timeout window before calling the AI Advisor.
  • Single Thread Logic: Only after the advisor completes its diagnostic and returns an action does the next attempt run via a recursive promise chain, ensuring state mutations never overlap.