ssv VS mev-boost

Are you strapped in and ready to make history? We're in the heart of the mission control room, preparing for the Limited Launch of the ssv.network mainnet.

After seeing this post about ssv.network, I became curious about what the rest of reddit thought about it.

It's pretty much an alternative to https://ssv.network/ (DVT)

Solo stakers and other community stakers are invited to participate in the next round of DVT testing with Obol Network and SSV Network. Deteails in the original Twitter thread.

I would start here - https://ssv.network/

Currently we are supporting Staking on testnet as well as creating a testnet Node Operator for the SSV network (https://ssv.network/) As you can see from the video, there is still a ton left to do, a lot of components/features we are planning to implement missing and polish to apply before we can think of a full release.

What you're describing already exists! It was on the top of Vitalik's roadmap (https://twitter.com/VitalikButerin/status/1466411377107558402), funded through a grant from the Ethereum Foundation, and has a working public testnet that is close to mainnet launch. Check out ssv.network. And here's a good video that gives a decent overview: https://www.youtube.com/watch?v=TV70EgAKkrI

I thing ssv.network did present something in AMS this week which shares portions of the validation keys accross a network of operators who need to aggregate a signature to validate. It's still not your keys, not your validator, but at least you are dilluting the risk by splitting the trust into several parties which would need to collude to slash you, which they also have no incentive to. Now do you trade the key split for the convenience of delegating the infra is another topic :)

FYI, this is fixed now: https://github.com/flashbots/mev-boost/issues/541

mev-boost v1.6 was released yesterday - it's often the part of the validator stack that gets neglected when it comes to updates.

For the setup, did you look at https://boost.flashbots.net/ ? Pretty straightforward, and examples of configuration for validator nodes are provided for each soft (prysm, lighthouse, nimbus...). I remember using that (and potentially doing one or two little adjustments). For the explanation, flashbot doc is nice, you can start here: https://docs.flashbots.net/new-to-mev

Are you also using MEV? Because a few people seem to have this same issue. Maybe it is a MEV-Geth thing. If so could you post your MEV logs?

Ahh I see yep, on the builder side not the validator side. Validators using https://github.com/flashbots/mev-boost but whichever builder gets chosen may likely be using those (especially if flashbots has the highest bid).

Personally I think the risk benefit is better to have mevboost activated. https://github.com/flashbots/mev-boost/issues/518

The same thing happened to me, I opened an issue in prysm and in mevboost, we are not the only ones with bad luck, https://github.com/prysmaticlabs/prysm/issues/12434 https://github.com/flashbots/mev-boost/issues/516 try adding the --build-block-parallel flag I also removed 2 relays, flashboot and brute. Hopefully next time we'll have better luck. sorry for my bad english

MEV-Boost is an implementation of proposer-builder separation (PBS) built by Flashbots for proof of stake Ethereum. Validators running MEV-Boost maximize their staking reward by selling blockspace to an open market of builders.