feature: hardcode formalize_loaded_transaction_data_size#338
Merged
topointon-jump merged 1 commit intoagave-v2.3.1from Aug 19, 2025
Merged
Conversation
mjain-jump
approved these changes
Aug 19, 2025
ripatel-fd
deleted the
topointon/hardcode_formalize_loaded_transaction_data_size
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before solana-foundation/solana-improvement-documents#186 formalize_loaded_transaction_data_size is activated, loaded account data size is unspecified. SIMD-186 precisely defines how the loaded account data size is calculated in a way that is easy for different clients to implement. As this feature will be activated soon, we hardcode this feature gate in our fuzz harnesses.