Jim McDonald

> Hmm, is the idea here that a validator could transact from their fee recipient account and as long as the builder provided a proof of inclusion of that transaction,...

> @mcdee Do you see any failure modes of the post-block balance proof solution that ... > A. ... are likely to impact solo stakers ... > B. ... and...

I believe that there are a few steps that we could take. The first is to restrict names to characters that come from a single language, using block identifiers as...

This looks like a good change to me. Comparing with 1.11.3 using a complex ~6MB sample: ``` goos: linux goarch: amd64 pkg: github.com/wealdtech/yamltest cpu: 12th Gen Intel(R) Core(TM) i7-1265U │...

Is there really much of a requirement to do this? Yes we have a 1:1 relationship for (builder->blinded) and (local->unblinded), but that's on purpose, as you say, and defined in...

We can't just remove the default, it's already part of the released spec and it's possible that validator clients are sending in requests without this value and expecting it to...

The `/beacon` endpoints are meant to be those that contain beacon chain structures. Rewards are derived information, so should sit outside of this namespace. (Also beacon endpoints are mandatory for...

Not commenting directly on the proposal, but a quick check of the sizes of this endpoint's response (in bytes) over the wire: - JSON 755_681_269 - compressed JSON 119_710_818 -...

I'm very back-and-forth on including the index in the output. It complicates the work required by client teams (requiring a non-spec structure), but is definitely useful information. An endpoint that...

I have put together #452 that provides the validator identities endpoint for review. I'll have a further consider about how this plays out for validator clients. Ultimately I suspect that...