Releases: base-org/node
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 up
v0.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
v0.2.1
Pointing at upstream commits:
Small improvements:
- expose geth metrics
- support for pre EIP-155 transactions (optional)
- Update OP_NODE_VERIFIER_L1_CONFS to 4 (helps with L1 reorgs)
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
v0.2.0
Pointing at upstream commits:
For the previous Regolith hardfork release (v0.1.1
), the sequencer was misconfigured which caused the Regolith hardfork to fail. We decided to reschedule the Regolith hardfork to timestamp 1683219600
(Thursday May 4, 2023 @ 17:00:00 UTC
) with ethereum-optimism/op-geth/pull/89.
This release also configures the op-geth
build to point to a commit from a hotfix provided by ethereum-optimism/op-geth/pull/90, which fixes some nodes stuck on block 3710592
(the block after the previous Regolith hardfork was scheduled). While the Regolith upgrade was reverted in v0.1.3
, some node operators still experienced stuck nodes, which this hotfix addresses.
To upgrade:
- ensure you are using the commits referenced above (or use our provided
Dockerfile
) - ensure your
goerli/rollup.json
has been updated to the latest version provided by this repo
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
v0.1.3
Pointing at upstream commits:
The sequencer was misconfigured which caused the Regolith hardfork to fail. This release reverts the Regolith configuration temporarily. We will follow up with a new Regolith hardfork release soon.
To upgrade:
- ensure you are using the commits referenced above (or use our provided
Dockerfile
) - ensure your
goerli/rollup.json
has been updated to the latest version provided by this repo
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
v0.1.2
v0.1.1
Pointing at upstream commits:
This schedules the Regolith hardfork for block at timestamp 1682614800
(Thu Apr 27 2023 17:00:00 GMT+0000). See ethereum-optimism/op-geth#83 and #44.
To upgrade:
- ensure you are using the commits referenced above (or use our provided
Dockerfile
) - ensure your
goerli/rollup.json
has been updated to the latest version provided by this repo
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