# Landing services Landing services are companies that exist to get your Solana transaction confirmed faster than the public network alone can. They charge a small tip per transaction in exchange for routing it through their direct validator connections or private mempools. You can enable as many as you want. FastTrack submits your transaction to every enabled service in parallel; whichever lands it first wins. Tips go straight to the service's own wallets — FastTrack does not see or take any cut of them. ## Why landing services exist Solana has no public mempool. Your transaction is sent directly to whichever validator is producing the next block. During busy markets, those validators are flooded — they drop transactions that aren't backed by enough priority fee or stake. A landing service has dedicated relationships with validators that won't drop your transaction. The tip is the lever. A higher tip is more likely to land you in the next block. ## Available services | Service | MEV protected | Minimum tip | Get a key | | ----------------- | ---------------------------- | ----------- | ------------------------------------------------------------------ | | **Jito** | ✅ (bundle atomicity) | 0.0001 SOL | [docs.jito.wtf](https://docs.jito.wtf/lowlatencytxnsend/) | | **NextBlock** | ✅ (with FRP flag) | 0.0001 SOL | [nextblock.io](https://nextblock.io/) | | **bloXroute** | ✅ (with FRP flag) | 0.001 SOL | [bloxroute.com](https://bloxroute.com/products/solana-trader-api/) | | **BlockRazor** | ✅ (with sandwich mitigation) | 0.001 SOL | [blockrazor.io](https://blockrazor.io/) | | **Nozomi** | ✅ (with MEV-protect key) | 0.001 SOL | [use.temporal.xyz](https://use.temporal.xyz/nozomi/) | | **Astralane** | ✅ (with mevProtect flag) | 0.0001 SOL | [astralane.io](https://astralane.io/) | | **Helius Sender** | ❌ | 0.0002 SOL | [helius.dev/sender](https://www.helius.dev/sender) | | **0slot** | ❌ | 0.001 SOL | [0slot.trade](https://0slot.trade/) | | **Falcon** | ❌ | 0.0001 SOL | Contact your provider | **Minimum tip** is the floor below which the service won't accept your transaction. FastTrack also enforces this on the settings page so you can't enable a service with a tip that wouldn't actually work. ## Per-service notes ### Jito The most-used Solana MEV infrastructure. Your transaction is bundled with other transactions targeting the same validator. Bundles are atomic — they execute as one unit or not at all — so they cannot be sandwich-attacked from within. Free to sign up via their API. ### NextBlock Direct validator connections plus an optional anti-front-running mode. When enabled, NextBlock holds your transaction until a trusted validator's slot comes up. Excellent for trades you specifically don't want to be sandwiched. ### bloXroute Large bandwidth-optimized network with several routing modes. Has explicit `frontRunningProtection` and `sandwichMitigation` flags. Mature product with extensive docs. ### BlockRazor A `sandwichMitigation` mode that defers your transaction until a safe leader window opens. Strict 0.001 SOL minimum tip. ### Nozomi (Temporal) Same-slot inclusion at median latency. Routes through self-hosted nodes plus Jito bundles. MEV-protect available via a special API key path — contact Temporal to request one if you need it. ### Astralane Optional `mevProtect: true` flag in their sendTransaction endpoint actively checks the current Solana leader and defers if it's flagged as a known sandwich operator. Lower per-tip cost than most competitors. ### Helius Sender Free, no API key required. Routes through Jito plus direct validator connections for speed. Does not have a native MEV-protect mode, but tips above \~0.0002 SOL pick up Jito's bundle protection as a side effect. ### 0slot Pure speed play, no MEV protection. Stake-weighted QoS for guaranteed access to leader TPU ports. Good as a redundancy add-on alongside another service. Requires a token (paste the value 0slot gives you into the API key field). HTTP-only endpoints by design — they're faster than HTTPS for this use case. ### Falcon Lightweight latency service. No native MEV protection — pair with Jito or NextBlock if you need that. ## Which should I pick? **On a budget** — just enable Jito. It's the cheapest MEV-protected option and works out of the box. **Serious about avoiding sandwich attacks** — enable NextBlock with **Front-running protection** on, or BlockRazor with **Sandwich mitigation** on. Both turn on Safe Mode candidacy automatically. **Maximum landing rate** — enable three or four services in parallel. FastTrack submits to all of them at once; whichever lands first wins, and the others just get dropped. Tip costs add up though, so consider this only for high-stakes trades. ## How to add a service 1. In FastTrack Settings, scroll to **Landing services**. 2. Click the **Add a landing service** dropdown. 3. Pick the service you want. FastTrack adds it with the minimum tip pre-filled. 4. Paste your API key. Jito is the only service that does not require one. 5. Click **Save**. Each enabled service adds a small SOL cost per trade equal to its tip. Tips are paid out of your trading wallet automatically, atomic with the trade. ## Safe Mode Safe Mode is a top-level toggle in the **Network** section. When on, FastTrack refuses to send any trade unless at least one enabled landing service is configured with an active MEV-protection mode. This includes: * Jito (always qualifies) * NextBlock with **Front-running protection** on * bloXroute with **Front-running protection** on * BlockRazor with **Sandwich mitigation** on * Nozomi with **MEV protection** on * Astralane with **MEV protection** on If Safe Mode is on and none of the above is enabled, your trade returns an error and the UI prompts you to enable a protected route. This is the right setting if you trade memecoins and don't want to be sandwich-attacked. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.willet.cc/getting-started/landing-services.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.