Releases: base/node
v0.4.0
Adds supervisord which enables support for running both op-geth and op-node in a single container. See https://github.com/base-org/node#running-in-single-container-with-supervisord for more information. Note this is backwards compatible, docker-compose is still supported.
Also upgraded the node software:
v0.3.3
v0.3.2
This release switches the OP_NODE_L2_ENGINE_RPC in the default configuration to use websockets instead of http (see #119). Using the http protocol can cause chain halts in certain scenarios, and this recommends switching to websockets to avoid this. If you configure your OP_NODE_L2_ENGINE_RPC / --l2 differently, we recommend updating your configuration to use ws.
Also upgraded the node software:
v0.3.1 (sepolia)
This release contains the Base sepolia configuration.
Also upgraded the node software:
v0.3.1-rc.3
Update op-node from v1.1.1 to v1.1.3
v0.3.1-rc.2
Fixes version reported from geth (geth --version or web3_clientVersion RPC): #101
v0.3.1-rc.1
Switch build to point to version tags:
This is a pre-release to pick up recent op-geth changes which prevent leakage of the txpool for folks running shared nodes.
v0.3.0 (mainnet)
This release contains the Base mainnet configuration.
No node software changes since the v0.2.3 release, still using versions:
If you are using docker-compose to run the node, you'll now need to select between Goerli and Mainnet. See the configuration in docker-compose.yml (uncomment the relevant env_file line for both containers).
v0.2.3
Switch build to point to version tags:
If you are using docker-compose to run the node, simply pull the latest version, and run:
docker-compose stop
docker-compose build
docker-compose upv0.2.2
Switch build to point to version tags:
- https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.1.0
- https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101106.0-rc.3
The op-geth update contains some fee estimate improvements for primarily empty blocks, which should reduce gas fees paid by users.
If you are using docker-compose to run the node, simply pull the latest version, and run:
docker-compose stop
docker-compose build
docker-compose up