Skip to content

Comments

Extend nitro-testnode to run consensus and execution separately#177

Draft
bragaigor wants to merge 1 commit intomasterfrom
braga/consensus-exec-diff-proc
Draft

Extend nitro-testnode to run consensus and execution separately#177
bragaigor wants to merge 1 commit intomasterfrom
braga/consensus-exec-diff-proc

Conversation

@bragaigor
Copy link

@bragaigor bragaigor commented Feb 13, 2026

Extend nitro-testnode to run consensus and execution in different processes

relates to NIT-4241
fixes NIT-4202

Pulled by OffchainLabs/nitro#4386

Signed-off-by: Igor Braga <5835477+bragaigor@users.noreply.github.com>
@bragaigor bragaigor force-pushed the braga/consensus-exec-diff-proc branch from 52beb21 to 3b1d3b7 Compare February 19, 2026 16:56
@bragaigor bragaigor changed the base branch from release to master February 19, 2026 16:56
Comment on lines +227 to +248
regular-follower-node:
pid: host # allow debugging
image: nitro-node-dev-testnode
entrypoint: /usr/local/bin/nitro
ports:
- "127.0.0.1:7447:8547"
- "127.0.0.1:7548:8548"
volumes:
- "seqdata:/home/user/.arbitrum/local/nitro"
- "l1keystore:/home/user/l1keystore"
- "config:/config"
- "tokenbridge-data:/tokenbridge-data"
command:
- --conf.file=/config/consensus_config.json
- --http.api=net,web3,eth,txpool,debug,timeboost,auctioneer
- --node.seq-coordinator.my-url=http://sequencer:8547
- --http.api=net,web3,eth,txpool,debug,timeboost,auctioneer
- --graphql.enable
- --graphql.vhosts=*
- --graphql.corsdomain=*
depends_on:
- geth
Copy link
Author

Choose a reason for hiding this comment

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

we don't really need this but it was very helpful in debugging. I've added it behind --follower-node flag, but let me know if you prefer to remove it

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