feat(wasm): BuiltInCapabilities includes bulk_memory - #1
Merged
Conversation
Lets wasmd accept CosmWasm guests that emit memory.copy/fill/init once libwasmvm meters those opcodes. Local wasmvm replace stays uncommitted.
This was referenced Aug 20, 2026
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
1 participant
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.
Why
terp-core v6 does
append(wasmkeeper.BuiltInCapabilities(), ...). Addingbulk_memoryhere is how the chain advertises the metered CosmWasm VM so rustc ≥ 1.87 uploads are accepted.What
x/wasm/keeper/capabilities.goAvailableCapabilitiesin keeper testsNot in this PR
Local
replace => ../wasmvm-bulk-memory. After merge, keepreplace => ../zk-wasmvm(v3.0.7-zk).