MEV Boost compatibility #2987
Closed
MEV Boost compatibility #2987
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- `PrivateBeaconBlock` - `PrivateBeaconBlockBody` - `SignedPrivateBeaconBlock`
- GET lighthouse/validator/blocks_private endpoint
This reverts commit 5982466.
…neric-transactions � Conflicts: � Cargo.lock � consensus/state_processing/src/per_block_processing.rs � consensus/state_processing/src/per_block_processing/block_signature_verifier.rs � consensus/types/src/beacon_block.rs � consensus/types/src/beacon_block_body.rs � consensus/types/src/execution_payload.rs � testing/ef_tests/src/cases/operations.rs
…neric-transactions
…neric-transactions � Conflicts: � beacon_node/http_api/src/lib.rs � consensus/types/Cargo.toml
|
Regarding our chat this morning about the merge transition and payload builders. I'm tempted to say that we don't try to produce blocks with a payload builder until the justified block is post-transition. The transition is a sensitive and complex time, I think it would be nice to keep things simple until 2/3rds of validators are agreeing up on the execution chain. I realise it will be lost profit for some stakers, but in the best case we'll see justification of the transition block in 2-3 epochs (~15mins). As I see it (and I might be missing things) I think being cautious around the transition is worth the costs. |
|
I'm going to close this branch but won't delete it because this is compatible with kintsugi. #3062 will be the kiln v2 target. |
3 tasks
bors bot
pushed a commit
that referenced
this pull request
Mar 31, 2022
## Issue Addressed MEV boost compatibility ## Proposed Changes See #2987 ## Additional Info This is blocked on the stabilization of a couple specs, [here](ethereum/beacon-APIs#194) and [here](flashbots/mev-boost#20). Additional TODO's and outstanding questions - [ ] MEV boost JWT Auth - [ ] Will `builder_proposeBlindedBlock` return the revealed payload for the BN to propogate - [ ] Should we remove `private-tx-proposals` flag and communicate BN <> VC with blinded blocks by default once these endpoints enter the beacon-API's repo? This simplifies merge transition logic. Co-authored-by: realbigsean <[email protected]> Co-authored-by: realbigsean <[email protected]>
paulhauner
pushed a commit
to paulhauner/lighthouse
that referenced
this pull request
Apr 4, 2022
## Issue Addressed MEV boost compatibility ## Proposed Changes See sigp#2987 ## Additional Info This is blocked on the stabilization of a couple specs, [here](ethereum/beacon-APIs#194) and [here](flashbots/mev-boost#20). Additional TODO's and outstanding questions - [ ] MEV boost JWT Auth - [ ] Will `builder_proposeBlindedBlock` return the revealed payload for the BN to propogate - [ ] Should we remove `private-tx-proposals` flag and communicate BN <> VC with blinded blocks by default once these endpoints enter the beacon-API's repo? This simplifies merge transition logic. Co-authored-by: realbigsean <[email protected]> Co-authored-by: realbigsean <[email protected]>
paulhauner
pushed a commit
to paulhauner/lighthouse
that referenced
this pull request
May 6, 2022
## Issue Addressed MEV boost compatibility ## Proposed Changes See sigp#2987 ## Additional Info This is blocked on the stabilization of a couple specs, [here](ethereum/beacon-APIs#194) and [here](flashbots/mev-boost#20). Additional TODO's and outstanding questions - [ ] MEV boost JWT Auth - [ ] Will `builder_proposeBlindedBlock` return the revealed payload for the BN to propogate - [ ] Should we remove `private-tx-proposals` flag and communicate BN <> VC with blinded blocks by default once these endpoints enter the beacon-API's repo? This simplifies merge transition logic. Co-authored-by: realbigsean <[email protected]> Co-authored-by: realbigsean <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue Addressed
MEV-boost compatibility
Proposed Changes
--private-tx-proposalsflag for the VC--payload-buildersBN flag for use with one or more MEV-boost like servicesAdditional Info
WIP