NC

> @ensi321 > > I implemented the interface for getting the withdrawal data. However, `curl -X 'GET' 'http://localhost:9596/eth/v1/builder/states/head/expected_withdrawals' -H 'accept: application/json'` still returns `{"message":"Route GET:/eth/v1/builder/states/head/expected_withdrawals not found","error":"Not Found","statusCode":404}`. It looks...

> Do I need to implement on my mainnet environment for conforming the logic? I recommend testing this kind of features by running it as a beacon node on mainnet...

> Hi, I would like to work on this. Can i get this assigned? Done! Thanks for your interest! If you encounter any issue just drop a message in our...

> Hi there, I investigated this issue and i can think of some cases where these tests could fail (This is my first issue so please forgive me if i...

It looks like this error happens in the first epoch transition regardless if there is a fork transition. I ran with `electra_fork_epoch: 2`, this error shows up in the first...

> The rewards API should return the whistleblower reward Are you talking about whistleblower reward for a) whistleblower himself or b) proposer including the slashing? If former, currently there is...

Something minor but I believe attester slashing is affected because the max length of `attesting_indices` in `IndexedAttestation` is changed. So get and post `/eth/v1/beacon/pool/attester_slashings`

No longer necessary as we are now shifting from using interval to either milliseconds or basis points

@philknows `web3_provider.node.test.ts` is blocking the PR from being merged. Need to rebase this branch to skip that test

> In Nimbus, it's trivial to implement https://github.com/ethereum/consensus-specs/pull/3787 simply by changing a constant - we're planning on having a separate OnchainAttestation type anyway because they appear in different contexts and...