ethDreamer
ethDreamer
So I found one bug with this. We were inappropriately downscoring the peer and disconnecting it when it sent us a block we couldn't optimistically import. I've created #3350 to...
> Looking really good! > > There are only two things I'd like to resolve before we merge: > > 1. What to do about the database schema change, i.e....
I've moved the schema migration from `v12` to `v13` so this PR can't be merged until * #3312 is merged and we rebase with `unstable`. But this should be good...
I've decided to work on withdrawals for now and I'll come back to this if someone doesn't hop on it :)
Yeah for sure 😊
GET fee recipient (key manager API) always returns the default one even if a new one was already set
> The POST is working fine (202) and saving into the `validator_defintions.yml` the given fee recipient config. > > The problem seems to be with the GET when having more...
Finally submitted a PR to `beacon-apis` for the endpoint: * https://github.com/ethereum/beacon-APIs/pull/245
@michaelsproul looks like another spurious failure of the windows tests.
yeah I thought the plan was to use `superstruct(flatten)` for the `IndexedAttestation` so that the types would be embedded
Looks like the reth team was [able to update alloy](https://github.com/alloy-rs/alloy/pull/185) just in time for `deneb` :tada:! After updating this PR to use `alloy` we no longer have build conflicts over...