Also sharing on Everstake progress. We are currently conducting extensive testing and have observed the following.
As mev-boost lacks sufficient metrics and does not offer the flexibility we require, we do believe commit-boost is currently the best candidate for replacement. The commit-boost team has been highly responsive and transparent throughout our interactions.
To facilitate the transition from mev-boost to commit-boost, we are collaborating on the following issues:
- [BUG] MUX relays don`t work correct · Issue #217 · Commit-Boost/commit-boost-client · GitHub
- [FEAT] Add num_registrations to log and metrics · Issue #218 · Commit-Boost/commit-boost-client · GitHub
- [FEAT] Add hot-reload via api · Issue #219 · Commit-Boost/commit-boost-client · GitHub
- [FEAT] Add more parameter to one log line · Issue #225 · Commit-Boost/commit-boost-client · GitHub
- [FEAT] Add new config parameter to set batch-size for registration validators on relays · Issue #226 · Commit-Boost/commit-boost-client · GitHub
Looking forward to further progress!