v1.17.5-jito

Pulls in upstream changes from Solana Labs v1.17.5

Jito-specific changes:
#406- Make MEV tip distribution run faster and more reliable
#446 - Revert Bank::simulate_transaction to match upstream
#428 - Add runtime plugin to run custom code with access to bank_forks
#449 - Fix account unlock bug from bundle simulation

v1.16.19-jito

Pulls in upstream changes from Solana Labs v1.16.19

Jito-specific changes:

• #406 - Make MEV tip distribution run faster and more reliable
• #446 - Revert Bank::simulate_transaction to match upstream
• #428 - Add runtime plugin to run custom code with access to bank_forks
• #449 - Fix account unlock bug from bundle simulation

v1.16.18-jito

Pulls in upstream changes from Solana Labs v1.16.18

v1.16.17-jito

Pulls in upstream changes from Solana Labs v1.16.17

Features:

• Add upsert function to AccountOverrides (#420)

v1.16.16-jito

Pulls in upstream changes from Solana Labs v1.16.16

Fixes:

• Fixes simulate_bundle RPC endpoints not returning error statuses (#407)

v1.17.1-jito

Pulls in upstream changes from Solana Labs v1.17.1

v1.14.28-jito

Pulls in upstream changes from Solana Labs v1.14.28

v1.16.14-jito

Pulls in upstream changes from Solana Labs v1.16.14

Fixes:
#376 : Fixed a bug that caused validator to error during leader slots due to state mismanagement involving packet removal in BankingStage.

v1.16.13-jito-fix-unprocessed-tx-storage

Pulls in upstream changes from Solana Labs v1.16.13

Fixes:

• #376 : Fixed a bug that caused validator to error during leader slots due to state mismanagement involving packet removal in BankingStage.

More about the bug:

Background:
The Jito-Solana validator has several internal cranking operations required to successfully operate that can't be interrupted. One of these is managing the state of the tip receiver. At the beginning of every slot, the validator checks to see if the MEV tip receiver is configured to the right address and if not, will change it. In order to prevent a non-validator transaction from changing the tip receiver, we added a set of blacklisted_accounts, which include a tip program config account and the 8 tip receiver accounts, which must be passed in during any tip program operations.

During the removal of these packets, state was not properly managed and the packet was not removed from the ConsumeScannerPayload.message_hash_to_transaction properly, which caused an internal error. This release (PR #376) fixes that issue by running the same logic that happens during an invalid packet that contains too many account locks.

v1.16.13-jito

Pulled in upstream changed from v1.16.13