Skip to content

feat(opstack): run op-rbuilder as a host process via builderBinary#3

Open
julio4 wants to merge 1 commit into
mainfrom
jules/opstack-builder-process
Open

feat(opstack): run op-rbuilder as a host process via builderBinary#3
julio4 wants to merge 1 commit into
mainfrom
jules/opstack-builder-process

Conversation

@julio4

@julio4 julio4 commented Jul 20, 2026

Copy link
Copy Markdown
Member

Adds builderBinary opstack recipe option that runs op-rbuilder as a locally built host process instead of pinned container. This needs a deterministic EL p2p identity + host-published p2p port so the host process can trusted-peer-dial the sequencer EL directly.

Current default container mode is unchanged.

@julio4
julio4 force-pushed the jules/opstack-builder-process branch from 8bddb1f to da0e72d Compare July 20, 2026 15:18

@canercidam canercidam left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks great! 🔥

Comment thread recipes/opstack.ts
// The bootnode is only needed for container mode's discovery-based
// peering; a host-process op-rbuilder dials the EL directly (see above).
...(builderHostProcess ? [] : [
{ name: "bootnode", containers: [{ name: "bootnode", prototype: "bootnode" }] },

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

If I am reading correctly, we are turning on the bootnode here but not doing the same when we switch to the processes instead. Is this intentional?

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.

2 participants