Jim McDonald

@rkapka yes we see that message prior to the error.

This error is still occurring with prysm 4.2.0. Recent call on sepolia: ``` /eth/v1/validator/blinded_blocks/4111200?randao_reveal=0xb13a6dcebaafa9ad8c429fe90fabf0f6d43cbf12d8f45ed216cd17ed3cb84b12bf6de430552395fc63abef8644f722d0148354d419a33e1f8007bddd0725821d2aa9dc230456c99e575619629fd253a38c2bfbc7ac042dfd5172f1524b74d2cb&graffiti=0x417474657374616e742f566f7563680000000000000000000000000000000000" ``` With response: ``` {"message":"Prepared block is not blinded","code":500} ``` ``` beacon-chain --version beacon-chain version Prysm/v4.2.0/3a2b486bde28f9b2a02c716782a738c64d62a8e8....

Please could we not pollute this issue with the on-going and contentious debate there? The adoption or not of that PR will make no difference to the changes put forward...

The current call to `/eth/v1/beacon/states/head/validators` returns over 200MB of data, and state is similar. As far as I am aware there is nothing even close to this that would be...

> Are we talking about basically if SSZ is returned, that the `data` field encoded as SSZ is returned? Yes. > Even more preferred would be specific use cases, rather...

> [...] it seems the validators list is about 35mb compressed None of the beacon API servers support compression today. But even if they did this would likely increase both...

I think that 204 is more technically accurate in this case. If the parameters were in the path a 404 would be reasonable, but the endpoint does indeed exist there...

Also see #281 which provides this plus additional functionality.

Regarding your points about not allowing a different set of withdrawal credentials with BLS: > Validator's withdrawal key was compromised. For some validators it would mean the validator signing key...

> That's a great way to introduce key rotation for staking pools that want to reduce their reliance on custodial or semi-custodial solutions. Note that this proposal does not allow...