You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When compute_budget instruction set_loaded_accounts_data_size_limit is not used, transaction currently has implicit limit of MAX_LOADED_ACCOUNTS_DATA_SIZE_BYTES. #1355 propose an reasonable default limit to be used instead of MAX.
New default limit could fail some transactions with TransactionError::MaxLoadedAccountsDataSizeExceeded, therefore the change should be behind a feature gate
Feature ID
CVvWw7NMVCn2Yp5RfxqrcTHXnaYyh91A2bGbkk88XXMM
Activation Method
Single Core Contributor
Deployment Considerations
Should communicate to dev community to adapt set_loaded_accounts_data_size_limit instruction. Thoughts here.
Minimum Beta Version
2.0
Minimum Stable Version
No response
Testnet Activation Epoch
No response
Devnet Activation Epoch
No response
Mainnet-Beta Activation Epoch
No response
The text was updated successfully, but these errors were encountered:
SIMD
none
Description
When compute_budget instruction
set_loaded_accounts_data_size_limit
is not used, transaction currently has implicit limit ofMAX_LOADED_ACCOUNTS_DATA_SIZE_BYTES
. #1355 propose an reasonable default limit to be used instead of MAX.New default limit could fail some transactions with
TransactionError::MaxLoadedAccountsDataSizeExceeded
, therefore the change should be behind a feature gateFeature ID
CVvWw7NMVCn2Yp5RfxqrcTHXnaYyh91A2bGbkk88XXMM
Activation Method
Single Core Contributor
Deployment Considerations
Should communicate to dev community to adapt
set_loaded_accounts_data_size_limit
instruction. Thoughts here.Minimum Beta Version
2.0
Minimum Stable Version
No response
Testnet Activation Epoch
No response
Devnet Activation Epoch
No response
Mainnet-Beta Activation Epoch
No response
The text was updated successfully, but these errors were encountered: