SLV Completes Solana v4 Support — Provides XDP-Accelerated Turbine and Alpenglow-Ready BLS Registration as an Operational Recipe Reproducible by Anyone via AI Agent Dialogue

ELSOUL LABO B.V. (Headquarters: Amsterdam, Netherlands, CEO: Fumitake Kawasaki) and Validators DAO are pleased to announce that SLV, the open-source Solana validator tool they develop and operate, has completed support for Solana v4 (Agave 4.x).

With this update, the optimizations adopted by the highest-performing Solana validators—Anza's XDP-accelerated Turbine retransmission and early support for the Alpenglow BLS public key registration workflow defined in SIMD-0387—can now be implemented by any operator using the same operational recipe, either through dialogue with an AI agent or via CLI commands. By consolidating the advanced tuning that previously required deep knowledge of Linux and Solana into SLV, operators without that specialized background can now reproduce these optimizations through simple dialogue.

SLV Official Website

SLV GitHub

Democratizing Top-Tier Validator Operations — Making World-Class Optimizations Reproducible by Anyone

SLV is an open-source initiative that enables high-quality, cost-effective Solana validator maintenance anywhere in the world by operating validators alongside an AI agent.

In the Solana ecosystem, the gap between raw validator performance and the operational expertise behind it has been widening. Low-latency network design, kernel and NIC tuning, thorough preparation for protocol upgrades—achieving top-tier validator performance has required deep expertise in Linux and Solana, along with continuous manual effort. As a result, best-in-class operations have often been accessible only to a select group of operators with that specialized knowledge.

SLV exists to bridge this gap. By aggregating the operational know-how accumulated by world-class validator operators into AI agent skills, anyone can reproduce the same operational recipe through dialogue alone. This Solana v4 support applies that philosophy directly to the latest optimizations. The very technologies used by the highest-performing validators—XDP and BLS—are now open to all SLV users, without requiring them to give up their choice of client or environment.

What Changes with Solana v4 Support — XDP, BLS, and Restart Safety Combined

Solana v4 (Agave 4.x) is the latest generation validator client recommended by Anza for mainnet. It enhances core performance while preparing the network for larger blocks and the upcoming consensus upgrade, Alpenglow. SLV's v4 support covers three areas particularly important for operators migrating to this foundation:

- XDP-Accelerated Turbine Retransmission: Enables a high-performance network path for faster block propagation, turnkey.
- Early Support for Alpenglow BLS Public Key Registration (SIMD-0387): Prepares the registration workflow in advance, allowing operators to register immediately after the Alpenglow feature gate is activated.
- Agave 4.1+ Restart Safety: Adjusts port ranges and gates cluster-restart-specific flags to prevent boot failures that could otherwise be avoided during client migration.

All of these are handled through the same SLV workflow—dialogue with an AI agent or CLI—so migrating to Solana v4 does not become a manual, error-prone project. The latest SLV release provides all of the above as part of the v2026.6.6 series, with BLS, XDP, and restart safety fixes leading, followed by Firedancer and RPC hardening within the same series.

What is XDP? — A High-Speed Path in the Linux Kernel for Accelerating Turbine

XDP (eXpress Data Path) is a Linux kernel technology that allows high-performance networking code to bypass much of the kernel's normal packet processing path. By reducing data copies and context switches, it processes packets with significantly less overhead than the standard network stack.

In Agave, XDP is applied to Turbine, the protocol for propagating blocks between validators. Incoming shreds are processed by an eBPF program attached near the network interface card (NIC) and mapped to user-space buffers via AF_XDP. Outgoing shreds are transmitted directly using XDP_TX, eliminating system calls and copies on the hot path. Anza introduced XDP for Turbine in the Agave 3.x series (from v3.0.9) and carried it forward into the Agave 4.0 foundation.

According to Anza's setup guide, with XDP, large validators can approach 150,000 outgoing packets per second. Anza positions XDP as part of the headroom to prepare validators for 100M-CU blocks and advance the IBRL (Increase Bandwidth, Reduce Latency) roadmap, and has published an official setup guide for operators who adopt it.

Anza Agave XDP Setup Guide

SLV Makes XDP Turnkey — Enable with Dialogue and a Few Configuration Variables

Manually deploying XDP is not straightforward. It requires a new kernel (6.14 or later for igb drivers, 6.8 or later for others), an XDP-compatible NIC, appropriate systemd capabilities for the validator process, and correct startup flags. The proper selection of CPU core pinning (including PoH cores) determines the performance of the path. This is precisely the kind of specialized work that has kept advanced optimizations out of reach for many operators.

SLV turns this into a turnkey step. XDP retransmission acceleration is enabled opt-in through per-host inventory variables: xdp_enabled, xdp_interface, xdp_cpu_cores, xdp_zero_copy, and xdp_poh_pinned_cpu_core. When enabled, SLV applies the appropriate XDP startup flags for the target Agave/Jito version and automatically grants the required systemd capabilities (CAP_NET_RAW, CAP_NET_ADMIN, CAP_BPF, CAP_PERFMON). These variables apply to Agave and Jito validators. Firedancer natively uses XDP, so no separate enablement is needed. (XDP has matured through Agave releases. In Agave 4.1, it is no longer experimental, and the corresponding flag names have evolved accordingly.)