OP-Stack

Steps to integrate a running op-stack rollup with Elder network

GitHub access for Elder is currently limited to early partner projects and may not be available to everyone.

The documentation may be outdated due to rapid development. Expect improvements as the code goes public and the project approaches its internal testnet phase.

Steps for running an op-stack rollup with ELDER

• Ensure your op-stack rollup is operational. For thoroughness, verify that both the batcher and proposer have sufficient funding.

• When not utilizing an existing internal devnet, a private Elder Node can be set up by following these steps - Run an ELDER Node

Make sure the ports of machines for Elder ( 1317, 26657, 9090 ) and Op-stack (8545, 8546 ) are public.

Register a rollup on Elder Chain

• Register the rollup on Elder.

elderd tx registration register [executor] [name] [min-tx-fess] [max-txs] [stack] [data-layer] [stake] [flags]

• Pull latest tags/main from 0xElder github and build their binaries.

GitHub - 0xElder/optimismGitHub

0xelder/optimism

GitHub - 0xElder/op-gethGitHub

0xelder/op-geth

• Build their binaries and replace with the original OP binaries.

Restart op-geth with the following additional command flags :

--rollup.disabletxpoolgossip=true --elder-seq --elder-seq-url=<Elder MACHINE IP>:9090 --elder-roll-id=<Rollup ID during registration> --elder-executor=<Elder executer private key> --elder-roll-start-block=<rollup geth block when the Elder connection should establish i.e. hardfork >