This guide explains how to connect a running OP-Stack rollup to the Elder network, including registration, configuration, and required ports. For the latest updates, see the official Elder OP-Stack integration docs.

​
Prerequisites

  • A fully operational OP-Stack rollup (batcher and proposer funded)
  • (Optional) A private Elder Node (see “Run an ELDER Node” in Elder docs)
  • Open ports on your machines:
    • Elder: 1317, 26657, 9090
    • OP-Stack: 8545, 8546

​
Steps to Integrate

1

Ensure OP-Stack Rollup is Running

Verify your OP-Stack rollup is operational. Make sure both the batcher and proposer are funded.
2

(Optional) Set Up Elder Node

If not using an internal devnet, set up a private Elder Node. See the “Run an ELDER Node” guide for details.
3

Open Required Ports

Ensure the following ports are public:
  • Elder: 1317, 26657, 9090
  • OP-Stack: 8545, 8546
4

Register the Rollup on Elder Chain

Register your rollup using the following command:
elderd tx registration register [executor] [name] [min-tx-fees] [max-txs] [stack] [data-layer] [stake] [flags]
5

Update OP-Stack Binaries

Pull the latest tags/main from the Elder GitHub repositories and build the binaries:Replace your original OP binaries with these builds.
6

Restart op-geth with Elder Flags

Restart op-geth with the following additional flags:
--rollup.disabletxpoolgossip=true \
--elder-seq \
--elder-seq-url=<Elder MACHINE IP>:9090 \
--elder-roll-id=<Rollup ID during registration> \
--elder-executor=<Elder executor private key> \
--elder-roll-start-block=<rollup geth block when Elder connection should establish>
For troubleshooting, advanced configuration, and the latest updates, see the official Elder OP-Stack integration docs.