terence
terence
I just dm'ed `baconBeacon` to learn more
I spoke with `baconBeacon` Here's the summary: It was a teku client running with 1 validator. It did not appear to crash or hang. Commands used to launch: ``` ./teku...
Would be nice to share and put all the test vectors for SSZ and fork choice under one repo
> For Lighthouse all we can recall (without additional history capabilities) is the latest `attestation.data.beacon_block_root` and `attestation.data.target.epoch` for each validator. Same for Prysm
> mev-boost tries to get the payload from all the relays, and as soon as it gets the payload from one it cancels the requests to other relays. Shouldn't this...
Could relay reply different responses to RM than to mev-boost? I don't see why relay would do this, but just a thought
Assuming both relay and builder don't have access to the block gossip layer. One minor downside is this will require an extra hop before gossiping the full block. I'm not...
> @terencechain : great point! however in my mind the builder had access to the block gossip layer, why do you assume they don't? > > if they did, i...
> The good news is that we have numbers to quantify this, in particular, Flashbots finds that on average, each additional second of waiting is worth 0.034 eth I'm curious...
There's also an active prototype by the lighthouse team to combat this: https://github.com/sigp/lighthouse/pull/2860 If it goes well, it'll likely land itself into the honest validator spec and all clients will...