Skip to content

Commit a50d4e6

Browse files
authored
Version 2.12.4.0 (#463)
* Version 2.12.4.0 * Changelog for v2.13.0.0
1 parent 67efbb5 commit a50d4e6

File tree

2 files changed

+40
-4
lines changed

2 files changed

+40
-4
lines changed

website/docs/About/Changelog.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,26 @@ instead.
1616
> On 1/27/2022, Eth Docker's repository name changed. Everything should work as it did.
1717
> If you do wish to manually update your local reference, run `git remote set-url origin https://github.com/eth-educators/eth-docker.git`
1818
19+
## v2.13.0.0 2024-10-16
20+
21+
*This is a recommended release*
22+
23+
**Breaking** changes
24+
- Require Prysm `v5.1.1` or later
25+
26+
Changes
27+
- Add support for commit boost
28+
- A fresh Reth sync keeps all receipts, for compatibility with sundry protocols such as SSV, RocketPool, NodeSet,
29+
StakeWise
30+
- Improved IPv4/v6 dual stack support
31+
- IPv6 is enabled on hosts that have IPv6 connectivity
32+
- Add Titan relay to Lido CM config dialog. Thanks @vgorkavenko!
33+
34+
Bug Fixes
35+
- Fixes to Lido CSM support. Thanks @cnupy!
36+
- Undo the Prysm VC REST use that "snuck in" with CSM. Prysm VC uses RPC again on port 4000, until the Prysm team
37+
promote the REST VC from experimental to released
38+
1939
## v2.12.3.0 2024-09-20
2040

2141
*This is a recommended release*

website/docs/Usage/ClientSetup.md

Lines changed: 20 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -77,9 +77,10 @@ Choose one execution client:
7777
> If you wish to use the built-in Caplin consensus client with Erigon, use `erigon.yml` without a consensus client file,
7878
and it will use the built-in Caplin consensus client
7979

80-
Optionally, enable MEV boost:
80+
Optionally, enable MEV boost or Commit boost:
8181

8282
- `mev-boost.yml` - add the mev-boost sidecar
83+
- `commit-boost-pbs.yml` - add the cb-pbs sidecar
8384

8485
Optionally, choose a reporting package:
8586

@@ -138,14 +139,30 @@ to Internet.
138139
setup.
139140
- `CLIENT-vc-only.yml` - the other side of the distributed client setup.
140141

141-
## MEV Boost
142+
## Proposer Builder Separation
143+
144+
### MEV Boost
142145

143146
Your Consensus Layer client connects to the mev-boost container. If you are running a CL in Eth Docker, then in `.env`
144147
you'd add `mev-boost.yml` to `COMPOSE_FILE`, set `MEV_BOOST=true` and set `MEV_RELAYS` to the
145148
[relays you wish to use](https://ethstaker.cc/mev-relay-list/).
146149

147-
If you would like to ensure whether your MEV relay has registered your validator, follow the documentation for your chosen relays. For instance, if you have included Flashbots, you can see whether your validator has been registered by querying their API. Add your validator's public key to the end of this endpoint: https://boost-relay.flashbots.net/relay/v1/data/validator_registration?pubkey=
150+
### Commit Boost
151+
152+
This is an alternative to MEV Boost. Your Consensus Layer client connects to the cb-pbs container. If you are running
153+
a CL in Eth Docker, then in `.env` you'd add `commit-boost-pbs.yml` to `COMPOSE_FILE`, set `MEV_BOOST=true` and
154+
set `MEV_NODE=http://cb-pbs:18550`.
155+
156+
Next, edit `commit-boost/cb-config.toml` and configure the relays you'd like to use.
157+
158+
### Verify
159+
160+
If you would like to verify whether your MEV relay has registered your validator, follow the documentation for your
161+
chosen relays. For instance, if you have included Flashbots, you can see whether your validator has been registered by
162+
querying their API. Add your validator's public key to the end of this endpoint:
163+
https://boost-relay.flashbots.net/relay/v1/data/validator_registration?pubkey=
148164

165+
### Just a VC, example RocketPool
149166

150167
If you are running a validator client only, such as with a RocketPool "reverse hybrid" setup, then all you need to do
151168
is to set `MEV_BOOST=true` in `.env`. `mev-boost.yml` and `MEV_RELAYS` are not needed and won't be used if they are
@@ -158,7 +175,6 @@ Eth Docker supports some specialty use cases. These are the corresponding yml fi
158175

159176
- `ext-network.yml` - Connect to another Docker network, for example for reverse hybrid with RocketPool or connecting
160177
to a central traefik/prometheus.
161-
- `v6-network.yml` - part of enabling IPv6 support
162178
- `central-metrics.yml` - Scrape metrics from a
163179
[central prometheus](https://github.com/CryptoManufaktur-io/central-proxy-docker)
164180
- `nimbus-stats.yml` - Send Nimbus stats to beaconcha.in app

0 commit comments

Comments
 (0)