Agave 4.3.0 ships stable, carrying the first pieces of the Votor transport
Serguey Asael Shinder1 min readAgave 4.3.0 was published on 18 September 2026 as a stable release suitable for Testnet, Devnet and Mainnet Beta — not a release candidate. Its changelog is short, and two entries are worth separating.
Vote-commission CLI commands. The release adds vote-update-commission-bps and vote-update-commission-collector, letting validators set commission in basis points and nominate a separate collector — finer control than a whole-percent commission and a split between the voting identity and where the commission is paid.
votor-transport send-error stats. A backport improves error statistics in votor- transport. That is the networking layer for Votor, the vote-exchange mechanism at the heart of the Alpenglow consensus change — the same one whose SIMD is still in Review. Better send-error stats in that transport is the unglamorous instrumentation work that precedes turning a new consensus path on.
What it means
Stable, not a release candidate, is the line that matters for operators. 4.3.0 is marked suitable for Mainnet Beta. The earlier 4.3 material we covered arrived as rc builds; this is the one a validator actually upgrades to, and the distinction is exactly the one a rates- or crypto desk should never blur.
Commission in basis points is a small governance change with real money behind it. Setting validator commission to whole percents forces coarse choices; basis points let a validator compete on a tighter margin. The collector split is operational hygiene — separating the key that votes from the account that receives.
The votor-transport line is the one to watch across releases. Alpenglow's consensus change is not live, but the transport it needs is being hardened release by release. Instrumentation landing in a stable build is how you can tell the switch is being prepared quietly, ahead of the SIMD that would flip it.
Source: https://github.com/anza-xyz/agave/releases/tag/v4.3.0