Skip to content

Add support for MEL - #216

Draft
TucksonDev wants to merge 4 commits into
releasefrom
add-support-for-mel
Draft

TucksonDev wants to merge 4 commits into
releasefrom
add-support-for-mel

Conversation

@TucksonDev

@TucksonDev TucksonDev commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

This PR adds support for MEL. Instructions for running the node for a pre-MEL and MEL chain are below.

A few notes:

  • no released nitro version includes the full MEL feature yet, tracked in branch mel/mel0-integration of nitro. Once that branch is part of a release, the default nitro image used in this branch should be updated
  • for now, this PR serves to run the testnode locally by building nitro as part of the initialization process, using the --dev parameter
  • there's a new CI job for running a pre-MEL chain
  • --wasm-module-root only 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.
  • for now, the validation node runs with 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):

NITRO_SRC=../nitro ./test-node.bash --init --l3node --dev --build-dev-nitro --no-build-dev-blockscout

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):

NITRO_CONTRACTS_BRANCH=v3.2.0 NITRO_SRC=../nitro ./test-node.bash --init --wasm-module-root 0xc10cd7ec6acaf1c441a3f6bd0900ad20f15855ba775a96f1939118cbc629dc97 --l3node --dev --build-dev-nitro --no-build-dev-blockscout

@TucksonDev
TucksonDev changed the base branch from bump-nitro-version-and-fix-stylus-activation to release November 20, 2026 11:02
Comment thread scripts/config.ts
"validation": {
"api-auth": true,
"api-public": false,
"use-jit": false // The image's mel0 machine lacks the wasm libraries the JIT needs

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If JIT is included in the mel0 machine, this should be removed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant