Jito Details Validator Requirements Ahead of Solana Alpenglow Upgrade

Jito Details Validator Requirements Ahead of Solana Alpenglow Upgrade


Key Highlights

Jito has issued operational guidance for Solana validators ahead of the planned Alpenglow upgrade, outlining client requirements and temporary changes to its Block Assembly Marketplace (BAM) infrastructure.

In an October 9 update, Jito said the mainnet transition was approaching but did not confirm an activation epoch or maintenance schedule. Its guidance covers client compatibility, temporary changes to BAM operations and adjustments related to Solana’s planned reduction in slot times.

Jito lists client versions ahead of Alpenglow

Jito recommends that validators review their client versions ahead of the transition. Its guidance lists the following releases:

  • Jito-Solana: v4.3.0-jito.0
  • Agave: v4.3.0-jito
  • Firedancer (FireBAM): v26.09.5
  • Frankendancer: v0.1204.40300

Jito said FireBAM and FrankenBAM operators will need version 26.10 or later after activation. It also warned that production validators using dev-context-only-utils could be forked off the network.

BAM nodes will temporarily switch to block engine mode

Jito said BAM nodes will enter Maintenance Mode several days before activation and temporarily fall back to the standard Jito-Agave Block Engine.

During this period, bundles will continue to work, but BAM-specific features, including Multiple Packet Processing (MPP) and Dynamic Block Incentives (DBI), will be unavailable.

Jito said validators, FullSend users and those using standard Block Engine bundles will not need to take action.

Users relying on MPP should route oracle updates through the Transaction Processing Unit (TPU) or Block Engine. Those using DBI should switch to the legacy Block Engine bundle path during maintenance.

Shorter Solana slots require auction changes

Solana planned to reduce its slot time to 200 milliseconds at Epoch 1053. Jito’s October 9 update estimated that the change would take effect around 15:00 UTC that day, but did not confirm that the transition occurred as scheduled.

Jito said BAM’s auction cadence was changing from 25 milliseconds to 20 milliseconds to accommodate the shorter slots.

The status of the Epoch 1053 transition should be verified against current Solana network information before publication.

Jito details BAM performance issues

Jito’s update described several performance issues and changes intended to address them.

The company said a Linux kernel issue caused delays of 90–330 milliseconds in the first slot of some leader windows. A mitigation had been deployed and a kernel fix tested.

Jito also reported that memory compaction on trusted execution environment (TEE) hosts caused slowdowns of 7%–17%. It said a fix for false sharing reduced replay latency by about 20%.

Separately, Jito said filtering low-quality Block Engine search keys increased BAM tips per block by 15.5%.

BAM validator metrics and revenue distribution

At Epoch 1050, Jito reported that BAM had 164 million SOL delegated across 385 validators, representing about 37% of Solana’s network stake. FireBAM accounted for another 7.3 million SOL across 12 validators, or about 4.6% of BAM stake.

Jito said the BAM Registry had operated on testnet for more than two weeks without anomalous behaviour. Mainnet enrollment was targeted for late October, with FireBAM integration dependent on TLS support.

Jito also said preconfirmation revenue distribution was live, with the first payouts expected in October. Under the arrangement, BAM validators receive 35% of preconfirmation revenue.

Separately, Jito’s JIP-39 changed effective-stake reward bands, introduced a 2% pool-share ceiling and extended the claim window from 10 to 20 epochs. Jito reported that about 1,750 SOL in rewards went to roughly 360 validators over Epochs 1041–1050.

JIP-38 proposal covers JTO buybacks

In a separate development, Jito’s JIP-38 proposal was approved in July. According to an earlier report, it commits JTX revenue to JTO buybacks and burns through the fourth quarter of 2027.

The asset ticker and revenue wording should be checked against the original proposal before publication.

Jito has outlined client requirements and temporary changes to BAM operations ahead of Alpenglow, but its October 9 update did not confirm the final activation epoch or maintenance schedule.

Validators should review the applicable client requirements and monitor Jito’s latest announcements for confirmed transition details.

Also Read: Aave MCP Integrates With MetaMask Agent Wallet for DeFi Transactions


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *