Agave 4.4 beta lets validators set commission in basis points
Anza published Agave v4.4.0-beta.1 as a pre-release. Validators can set commission in basis points, separately for block revenue, and RPC gains new options. It is a beta, not a mainnet release.
On 13 October, Anza published Agave v4.4.0-beta.1 as a pre-release. This is not a mainnet release.
The changelog adds vote-update-commission-bps, which sets a vote account’s commission in basis points. --commission-kind selects inflation-rewards or block-revenue. vote-update-commission-collector sets the account that receives each kind, through the COMMISSION_KIND argument.
getTransaction accepts minContextSlot, and getSignatureStatuses accepts commitment and minContextSlot. With no commitment, getSignatureStatuses still defaults to processed. If the context slot is below the minimum, the error is -32016.
accountSubscribe and programSubscribe apply dataSlice. An empty dataSlice returns empty data. Omitting dataSlice returns the full account.
getLeaderSchedule returns -32022 when the given identity is missing from the schedule. External schedulers need scheduler-bindings version 5. Removed are --experimental-retransmit-xdp-interface, --experimental-retransmit-xdp-cpu-cores, and --experimental-retransmit-xdp-zero-copy.
The changelog names --xdp-interface, --xdp-cpu-cores, and --xdp-zero-copy alongside that removal. It does not say whether the new commission kinds already apply on mainnet.
Note: This is reporting, not investment advice.
Sources
- Anza — Release v4.4.0-beta.1, pre-release, 13 October 2026, 8:35 a.m. Berlin · Changelog, section 4.4.0. The release page itself does not list the changes. The changelog also adds
RpcClient::get_signature_statuses_with_config.