Coin Brief ENDE

Jito-Solana ships v4.3.0-jito.0 and patches a validator failover crash

The Jito Foundation published Jito-Solana v4.3.0-jito.0 on 2 October, a stable point release of the validator client most Solana stake runs on. Its changelog lists four backports to the 4.3 line: sending the first shred faster, draining messages for skipped banks before serialisation in turbine, debug-symbol builds, and a fix to BAM tip refresh with simpler scheduler plumbing. BAM is Jito's block assembly marketplace.

Two further fixes were merged to the 4.3 and 4.4 branches on 1 October and are not in that changelog, so they should reach operators in a following release.

The first addresses a crash. set-identity, the command validators use to switch the key they produce blocks with, for example when failing over to a backup machine, could update the shared identity while the block creation loop was waiting for a leader-window notification or for its parent block to replay. The loop could then hold an identity different from the scheduled leader, and the resulting mismatch panic stopped the validator. The fix, adapted from Anza's Agave pull request 15582, returns a LeaderIdentityMismatch error before a leader bank is created, skips the affected window and continues with later notifications. Regression tests cover both normal production and fast leader handover.

The second bounds what a BAM configuration response can cost a node. Responses over 64 KiB after authentication are now rejected before protobuf decoding; only the first 32 valid, unique shred receivers are kept; and per-entry warnings are replaced with one summary line. A connection that receives an oversized response keeps its last good configuration.

Jito-Solana ships v4.3.0-jito.0 and patches a validator failover crash
Jito-Solana ships v4.3.0-jito.0 and patches a validator failover crash — Coin Brief

Why it matters

Identity switching is how operators do hot failover without missing slots, so a race that panics the validator during the switch hits exactly the moment they are trying to avoid downtime. The BAM limit is the kind of hardening that matters once outside parties feed configuration into block production.

Written by Victoria Shinder.