Changed the MEV-boost usage in a more general "builder-API compatible endpoint". (Usage of MEV-boost is not mandatory when using external block building: You can directly target a relay (not common at all) or use any "MEV-boost like" tool (more common).
Change some prater instances into goerli.
Use bazel run //cmd/<xxx> instead of bazel run //<xxx>.
Add usage of --suggested-fee-recipient when running the Prysm validator client.
Add Sepolia/Holesky in testnets when needed.
Warning:
In builder.md, in the sentence:
There are risks to using a builder which may result in missed rewards, missed proposals, censored transactions, omitted transactions, and even slashing when used incorrectly.
I removed the
and even slashing when used incorrectly.
In my opinion, using builder cannot lead to slashing when used incorrectly. I believe the assumption behind this sentence was something like:
Get a block from a builder, sign it and broadcast it, then, for the same slot
Get a local block from the execution node, sign it and broadcast it
However, in this case, signing 2. is rejected by the anti-slashing module.
prater
instances intogoerli
.bazel run //cmd/<xxx>
instead ofbazel run //<xxx>
.--suggested-fee-recipient
when running the Prysm validator client.Warning: In
builder.md
, in the sentence:I removed the
In my opinion, using builder cannot lead to slashing when used incorrectly. I believe the assumption behind this sentence was something like:
However, in this case, signing
2.
is rejected by the anti-slashing module.