Optimizations for genesis import #2397
Open
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.
This pull request introduces new exports and optimizations to the Wasm module's keeper to support efficient genesis imports and external integrations. The main changes focus on exposing internal methods for importing code, contracts, and sequence IDs, as well as improving contract history import performance during genesis.
Genesis exports for external tooling
x/wasm/keeper/genesis_exports.gothat wrap private keeper methods, allowing external packages to import Wasm code, contract instances, and sequence counters during genesis or state migrations.Performance optimizations for genesis import
appendToContractHistoryForGenesis, a specialized method that efficiently writes contract history entries without checking for existing data, significantly speeding up genesis imports with many contracts.importContractto use the optimizedappendToContractHistoryForGenesisinstead of the standard history appending method, ensuring better performance when importing contracts during genesis. [1] [2]