Paladin

Paladin is a modified Solana validator client, forked from Jito-Solana, that launched in September 2024 with two distinct goals: blocking sandwich attacks at the validator level and extracting additional revenue from atomic arbitrage opportunities left behind after standard Jito bundle processing. Validators run the Paladin binary in place of standard Jito-Solana and receive both MEV rewards and the PAL governance token without changing their staking arrangements or requiring delegators to interact with any new protocol.

The Problem: MEV Sandwich Attacks on Solana

Solana's high throughput makes it attractive to automated MEV bots that detect large pending trades, place a buy order immediately before them, and sell immediately after — a sandwich attack. Users absorb the cost as worse execution prices. Traditional approaches to this problem operate at the RPC or relay level, which means validators themselves remain passive participants. Paladin instead intervenes at the block-production stage, where the leader has direct authority over transaction ordering.

How Paladin Works

Paladin as a Validator Client Fork

Paladin is built directly on top of Jito-Solana and inherits its bundle auction infrastructure. The project is open-source under an Apache-2.0 license and maintained under the GitHub organization paladin-bladesmith. Validators install the Paladin binary by rebasing onto the current Jito-Solana version — as of early 2025, tracking releases such as v2.1.18-paladin — and open two additional QUIC UDP ports to enable the P3 Priority Port.

The P3 Priority Port

The P3 (Paladin Priority Port) is Paladin's primary user-facing feature. It exposes two dedicated QUIC ports on each validator: port 4819 for transactions that execute even if they revert, and port 4820 for MEV-style transactions that must succeed on-chain. Transactions submitted through P3 travel directly to the current block leader, bypassing RPCs, relays, and swQoS stake-weighted routing — the intermediary hops where sandwich bots typically observe and front-run transactions.

P3 enforces a rate limit of 100 transactions per second and a minimum priority fee at the 90th percentile of network activity. Transactions that fall below this threshold are dropped. The rationale is that P3 is designed for high-value trades where the cost of sandwiching outweighs a moderately elevated priority fee, not routine transfers.

Sandwich Detection and Bundle Rejection

Paladin's execution stage is modified to automatically reject bundles that match sandwich patterns — a buy, a victim transaction, and a matching sell in the same block position. The mechanism is heuristic-based pattern matching applied at block production time. Independent analysis by Buffalu (a Jito Labs contributor) noted that this approach is not cryptographically robust: the pattern is detectable by sophisticated searchers, who reportedly developed workarounds within days of Paladin's launch. Paladin's team framed the goal as raising the cost and complexity of sandwiching rather than making it technically impossible.

Atomic Arbitrage MEV Bot

Beyond P3, Paladin embeds an on-validator MEV extraction bot that identifies and captures atomic arbitrage opportunities — price discrepancies across DEXes and between DEX and CEX prices — after Jito bundles have been executed in a given slot. This is backrunning rather than front-running: the bot acts on price changes that result from included transactions, not on pending transaction visibility. A Chorus One performance study in October 2024, run on a validator with 1.15 million SOL in stake, found that Paladin captured approximately 15.84% of available atomic arbitrage opportunities during the test window. Chorus One estimated the annual size of the accessible atomic arbitrage market at roughly 42.4 million USD across the network — translating to approximately 0.07% additional APY for validators at full adoption.

PAL Token

Paladin introduces a native token, PAL, with a fixed supply of one billion. The token serves two functions: capturing a portion of P3 priority fees for holders, and acting as collateral that economically deters validators from sandwiching their own P3 users.

The token distribution is as follows:

• 50% to validators and delegators
• 23% to Solana ecosystem contributors
• 20% to the Paladin team
• 7% to a future development fund

Revenue from the embedded MEV bot is distributed as:

• 90% to validators (who may pass a portion to delegators)
• 7.5% to PAL stakers
• 2.5% to an ecosystem fund

P3 priority fees also contribute a 2.5% allocation to the PAL system. The governance mechanism around PAL allows staked holders to vote to slash a validator's PAL stake if that validator is proven to have sandwiched a P3 user — a majority threshold above 50% sustained for one week triggers the slash and burns the tokens.

Validator Adoption

Paladin launched in September 2024 and was made fully open-source in January 2025. By January 2025, approximately 130 validators representing around 10% of Solana's total staked SOL had adopted the client. Published figures from March 2025 cited 205 validator nodes running Paladin with 53 million SOL staked under the client. Paladin's team reported that validators saw an immediate 10–20% increase in block rewards upon adoption, with a figure of +12.5% cited as a representative gain in early communications.

Independent Analysis and Criticism

Two detailed independent assessments have been published. Buffalu's analysis argued that Paladin's sandwich detection is pattern-matchable and that, controlling for Jito tip revenue, Paladin validators may earn 25–50% less in combined fees and Jito tips than standard Jito-Solana validators — processing roughly 23% fewer transactions per block. Buffalu attributed this partly to the additional overhead of sandwich filtering and partly to transaction flow diversion away from Paladin validators.

Chorus One's October 2024 report took a more measured view. It confirmed that Paladin's atomic arbitrage bot showed early promise but identified meaningful gaps: the bot's strategy set did not cover many emerging memecoins, missing a significant portion of available MEV. Chorus One also flagged operational friction for validators, as each strategy update requires a client restart. The report concluded that Paladin's effectiveness depends on improving token coverage and establishing clear community governance for ongoing maintenance.

bloXroute routes transactions via a combined path of Jito and Paladin alongside its own propagation channels for front-running-protected transaction submission, representing the first major integration partner for P3.

Ecosystem Position

Paladin occupies the validator client layer of Solana's MEV infrastructure — a narrow but structurally significant slot, since validators have unilateral authority over transaction ordering in their assigned slots. It does not compete with Jito's block engine directly but adds an additional tier of protection and extraction on top of it. The project is one of several signals that Solana's validator ecosystem is moving toward differentiated client software, with operators weighing MEV policy, reward profiles, and token incentives when choosing which client to run.