Chris Hager

the thing is that `main` is not necessarily as stable as it implies, PRs could be merged without exhaustive tests having run. These would only run before a new release....

Created `develop` branch, set it as repository default branch, and removed `main` branch.

Currently `pdfx -c` checks all the links without the ability to restrict to only pdfs. I will add this to the feature backlog. On Tue, Jul 26, 2016 at 9:20...

I'm not a fan of these proposed changes. First, I don't subscribe to the initial problem statement. * With some smart caching on the relay side, almost no signatures need...

More significantly, any interaction between the beacon node and builder network should be governed by this repository (builder-specs) only, and be part of the `/eth/v1/builder` URL namespace. And moving the...

Yes, we've been thinking about this too, and are currently experimenting with API design between builder and relay. The idea is that builders push full blocks to the relay, and...

I feel like adding a builder signature would be good. An alternative to the signature addition suggested above could be to embed both public keys into BuilderBid and have both...

I'd like to propose https://github.com/ethereum/builder-specs/pull/30/files as first step, adding both the builder and relay pk into the BuilderBid. This is useful for many cases, including not only relying on the...

Thinking about it, upgrading `v1` to allow for it seems kind of straight forward this way: 1. beacon-node calls `getHeader` with request header `accept-encoding: application/ssz` 1. If response is SSZ...

cc/ @terencechain @tbenr @StefanBratanov @tersec @realbigsean @dapplion @lightclient