Upcoming Pectra mev-boost release: v1.9
We are preparing for an upcoming Pectra-ready mev-boost release: v1.9
ETA for the first release candidate is Tuesday, Feb. 4.
This is the main PR for the Electra changes: https://github.com/flashbots/mev-boost/pull/651
Other changes since v1.8: https://github.com/flashbots/mev-boost/compare/v1.8...develop
h/t to @jtraglia for implementing the majority of Electra related changes!
Published our first release candidate here:
- https://github.com/flashbots/mev-boost/releases/tag/v1.9-rc2
When will non-rc tag be created?
When will non-rc tag be created?
Hey @t10471, very soon 🙂 probably in the next couple days.
hello there, not able to install mev-boost v1.9 (required update for the upcoming Pectra upgrade) using the command go install github.com/flashbots/[email protected] --> no matching versions for query "v1.9" go install github.com/flashbots/mev-boost@latest --> still goes to v1.8.1 go install github.com/flashbots/[email protected] --> invalid version: unknown revision v1.9.0
why is this?
Same issue. Can't install v1.9 using go install
Hi there @hernanirvaz & @Devnant, thanks for bringing this up! It looks like I forgot to tag v1.9.0 (in addition to v1.9). Apparently, pkg.go.dev only recognizes semantic versioning and v1.9 is not valid there. I've just made a new v1.9.0 tag and can confirm that go install github.com/flashbots/[email protected] works now.
Running mev-boost --version from the release asset https://github.com/flashbots/mev-boost/releases/download/v1.9/mev-boost_1.9_linux_amd64.tar.gz return
INFO[0000] mev-boost 1.8
There might be a version info issue with the release.
Running
mev-boost --versionfrom the release asset https://github.com/flashbots/mev-boost/releases/download/v1.9/mev-boost_1.9_linux_amd64.tar.gz returnINFO[0000] mev-boost 1.8There might be a version info issue with the release.
Hey @remyroy, I think you might be running the binary installed on your system. Could you try running ./mev-boost after unpacking the tarfile? For example:
It could have been on me too. When I updated and relaunched my service it showed version 1.9.
Closing this issue, since we are preparing for the upcoming Fulu release!