lighthouse-pulse/consensus
realbigsean ea783360d3 Kiln mev boost (#3062)
## Issue Addressed

MEV boost compatibility

## Proposed Changes

See #2987

## Additional Info

This is blocked on the stabilization of a couple specs, [here](https://github.com/ethereum/beacon-APIs/pull/194) and [here](https://github.com/flashbots/mev-boost/pull/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 <seananderson33@gmail.com>
Co-authored-by: realbigsean <sean@sigmaprime.io>
2022-03-31 07:52:23 +00:00
..
cached_tree_hash
fork_choice
int_to_bytes
merkle_proof
proto_array
safe_arith
serde_utils
ssz
ssz_derive
ssz_types
state_processing Kiln mev boost (#3062) 2022-03-31 07:52:23 +00:00
swap_or_not_shuffle
tree_hash
tree_hash_derive
types