chore: migrate to Miden protocol 0.16.0-rc.3 and VM 0.29 - #1311
Draft
greenhat wants to merge 1 commit into
Draft
Conversation
Move the compiler and SDK onto the protocol 0.16 release-candidate line, which brings the VM 0.29 crate family, miden-debug 0.10, and miden-field 0.29. - Bump miden-protocol and miden-standards to =0.16.0-rc.3, the VM crates to 0.29, miden-debug to 0.10, miden-field to 0.29, and midenc-hir-type to 0.10. - Seed both core-library packages wherever a registry, executor, host, or assembler is set up: miden-core now ships with a separate miden-precompiles package that dependency resolution requires. - Follow the VM rename of log_precompile to log_deferred through the HIR op, dialect builder, MASM frontend, and codegen, and teach the frontend the operand footprints of the new deferred system events. - Adopt the typed AdviceStack advice API in the execution harnesses; consumption order is unchanged. - Rebuild the rpo-falcon512 auth example around the 24-felt transaction summary, which now binds the reference block commitment, the expiration delta, and seven user parameters. - Keep integration-network in the workspace by taking miden-client from its migration branch (0xMiden/rust-sdk#2356) until a protocol-0.16 client release exists, and port the mockchain tests to the miden-testing rc.3 transaction-builder API. - Refresh fixture and example lockfiles so the p3 crates resolve to 0.6.3, matching miden-field 0.29's num-bigint 0.5 requirement; miden-field's own p3 requirements are still too loose (0xMiden/miden-vm#3536), documented next to disabled floor pins in miden-base-macros.
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.
Closes #1310.
Migrates the compiler and SDK to the protocol 0.16 release-candidate line: miden-protocol/miden-standards
=0.16.0-rc.3, the VM 0.29 crate family, miden-debug 0.10, miden-field 0.29, and midenc-hir-type 0.10.The main adaptations: every registry/executor/host/assembler setup now seeds both core-library packages (miden-core plus the new miden-precompiles dependency); the
log_precompileinstruction rename tolog_deferredis followed through the HIR op, frontend, and codegen; the MASM frontend learns the operand footprints of the new deferred system events; the execution harnesses adopt the typedAdviceStackAPI; and the rpo-falcon512 auth example builds the new 24-felt transaction summary that binds the reference block commitment, expiration delta, and user parameters.No miden-client release supports protocol 0.16-rc yet, so
tests/integration-networktemporarily takes miden-client from the client's own migration branch (0xMiden/rust-sdk#2356, which pins the node migration 0xMiden/node#2421 by rev), and its mockchain tests are ported to the miden-testing rc.3 transaction-builder API.Fixture and example lockfiles are refreshed so the p3 crates resolve to 0.6.3, matching miden-field 0.29's move to num-bigint 0.5. miden-field's published p3 requirements are still
^0.6, so resolutions from stale registry caches can still break generated projects; this is filed upstream as 0xMiden/miden-vm#3536 and documented next to (currently disabled) floor pins inmiden-base-macros.The SDK changelog gains a breaking-change entry: compiled packages link against the updated transaction kernel and core library, so their commitments change, and hosts must use matching protocol 0.16.0-rc.3 crates. Guest code compiles unchanged.
TODO:
protocolto RC3 rust-sdk#2356 (client dependency migration) merged and a protocol-0.16-compatible miden-client released; then switchtests/integration-networkback to a crates.io miden-client and drop the git-branch dependency.p3*dependencies to 0.6.3+ miden-vm#3536 fixed and released (miden-field raising its p3 requirements to >= 0.6.3); then remove the workaround breadcrumb insdk/base-macros/Cargo.toml.