Repository navigation
Add support for MEL - #216
Draft
TucksonDev wants to merge 4 commits into
Draft
TucksonDev wants to merge 4 commits into
TucksonDev wants to merge 4 commits into
Conversation
…eRoot flags, add CI job for pre-MEL
TucksonDev
changed the base branch from
bump-nitro-version-and-fix-stylus-activation
to
release
November 20, 2026 11:02
TucksonDev
commented
Nov 20, 2026
| "validation": { | ||
| "api-auth": true, | ||
| "api-public": false, | ||
| "use-jit": false // The image's mel0 machine lacks the wasm libraries the JIT needs |
Contributor
Author
There was a problem hiding this comment.
If JIT is included in the mel0 machine, this should be removed
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
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 PR adds support for MEL. Instructions for running the node for a pre-MEL and MEL chain are below.
A few notes:
mel/mel0-integrationof nitro. Once that branch is part of a release, the default nitro image used in this branch should be updated--devparameter--wasm-module-rootonly accepts roots from the image's target/machines. The nitro-legacy machines are rejected for now, because with the JIT off validation runs on the arbitrator, which can't load their older machine.wavm.br format. The rest of the legacy setup (the allowed roots list and the validation node's machine directory) is unchanged.use-jit=false, so all validation goes through the arbitrator, pre-MEL chains included. The mel0 machine in the current nitro image lacks the wasm libraries the JIT loads (user_host.wasm, forward.wasm, program_exec.wasm). The setting can go once the JIT is able to run the mel0 machine.Running a MEL chain
Use the following command, assuming the nitro repo sits at the same level as the current directory and it's in the MEL0 branch (likely mel/mel0-testnode-image which builds on top of mel/mel0-integration and ships the MEL replay):
Running a pre-MEL chain
Use the following command, assuming the nitro repo sits at the same level as the current directory and it's in the MEL0 branch (likely mel/mel0-testnode-image which builds on top of mel/mel0-integration and ships the MEL replay):