-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add MEV-Boost package to Stakers Holesky #1898
Conversation
DAppNode bot has built and pinned the release to an IPFS node, for commit: ae1f3f0 This is a development version and should only be installed for testing purposes, install link
(by dappnodebot/build-action) |
@@ -233,7 +233,7 @@ export default function StakerNetwork<T extends Network>({ | |||
isSelected={newEnableWeb3signer} | |||
/> | |||
</Col> | |||
{(network === "prater" || network === "mainnet") && ( | |||
{(network === "prater" || network === "mainnet" || network === "holesky") && ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably there is a better way to do this. Something like:
["prater", "mainnet", "holesky"].includes(network)
(research a bit on the best way to do it)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The use of Array.includes()
makes the condition more expressive and self-explanatory. It clearly communicates the intent of checking whether the network value is among a predefined list of valid networks. So it is a better approach for readability, maintainability, and flexibility of the code.
Please see issue #1865
This pull request adds support for the Holesky testnet to MEV-Boost, including integration of working relays for Flashbots, Aestus, and Ultrasound networks. Additionally, it ensures a consistent user experience across different networks, mirroring the UX of MEV-Boost on other platforms. With Prater nearing deprecation and its relays no longer maintained, this update is crucial for seamless transition and continued functionality.