-
Notifications
You must be signed in to change notification settings - Fork 298
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
[MEV boost\Builder] Builder spec 0.2.0
support
#5396
Labels
Comments
tbenr
changed the title
[MEV boost] support spec version 0.2.1
[MEV boost\Builder] support spec version 0.2.1
Apr 27, 2022
This was referenced May 2, 2022
2 tasks
2 tasks
This was referenced May 5, 2022
2 tasks
This was referenced May 11, 2022
This was referenced May 18, 2022
2 tasks
This was referenced May 19, 2022
2 tasks
2 tasks
2 tasks
2 tasks
tbenr
changed the title
[MEV boost\Builder] support spec version 0.2.1
[MEV boost\Builder] support spec version 0.1
Jun 28, 2022
tbenr
changed the title
[MEV boost\Builder] support spec version 0.1
[MEV boost\Builder] support spec version Jun 28, 2022
0.1.0
tbenr
changed the title
[MEV boost\Builder] support spec version
[MEV boost\Builder] Builder spec Jul 1, 2022
0.1.0
0.2.0
support
2 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
we want to support version
0.2.0
and . More info here:https://github.com/ethereum/builder-specs/releases/tag/v0.2.0
https://ethereum.github.io/builder-specs/
general flow requirements
builder_status
)builder_getHeaderV1
andengine_getPayload
with fallback handling (error or timeout)builder_getPayloadV1
with the payload returned byengine_getPayload
.Execution API Clients:
builder_
api fromexecution_
api clients (migratebuilder_
toExecutionBuilderClient
)builder_status
builder_registerValidatorV1
builder_getPayloadHeaderV1
tobuilder_getHeaderV1
builder_proposeBlindedBlockV1
tobuilder_getPayloadV1
ExecutionEngineChannel:
ExecutionLayerChannel
).engine_
,builder_
and someeth1_
endpoints via two separate jsonrpc clientsExecutionLayerManagerImpl
less a simple proxy for api calls and being responsible for the fallback logic. It could abstract away all the "general flow requirements".ExecutionEngineService:
builder_status
to track builder flow availabilityCLI and configuration
eb-endpoint
(execution builder)--Xvalidators-proposer-mev-boost-enabled
->--Xvalidators-registration-default-enabled
. #5638--Xvalidators-registration-default-gas-limit
(default value 30000000 mainnet) #5639Beacon Rest API:
register_validator
endpoint ethereum/beacon-APIs#209) inregister_validator
API. Must callbuilder_registerValidator
.Validator Client:
feeRecipient
for a validator registration #5636gasLimit
and use theenabled
flag for validator registration #5637Beacon Node:
builder_
(might be easy ifExecutionEngineChannel
will be responsible for most of the work)Latest Spec changes
builder_registerValidator
to accept an array of registrations #5595compute_domain(DOMAIN_APPLICATION_BUILDER)
#5613Bugfix - Improvements
/eth/v1/validator/register_validator
beacon node API returns 400 when downstream builder API fails with 502 #5880Monitoring/Logging
The text was updated successfully, but these errors were encountered: