chore(v6): default CosmWasm stack to metered bulk_memory forks - #268
Merged
Conversation
Point gitmodules at the fork branches that now include metered memory.copy/fill/init (permissionlessweb PRs merged): - crates/cosmwasm → v3.1.0-zk.0 - crates/zk-wasmvm → v3.0.7-zk - crates/zk-wasmd → merge/upstream-wasmd-v0.70 terp-core already does append(wasmkeeper.BuiltInCapabilities(), ...), so bulk_memory is advertised once zk-wasmd is on that branch. Does not drop local ZK worktrees or uncommitted Stwo/path remaps.
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
v6 should accept rustc ≥ 1.87 CosmWasm guests with metered
memory.copy/fill/init.Already merged on the forks (do not revert)
v3.1.0-zk.0v3.0.7-zkmerge/upstream-wasmd-v0.70This PR
Updates
.gitmodulesdefault branches (and a go.mod comment) so v6 clones track those lines.app/keepersalready doesappend(wasmkeeper.BuiltInCapabilities(), ...), sobulk_memoryis advertised once zk-wasmd is on the merged branch.Not in this PR
feat/bulk-memory-ictworktree path replaces (crates/_worktrees/...) — those stay on the isolated integration branchRebuild libwasmvm muslc against the merged cosmwasm before shipping a new alpine image.