ethereum-consensus
ethereum-consensus copied to clipboard
ralexstokes
after #17 we have the infra in place to run the consensus-spec-tests we should figure out how to run them in the CI, perhaps only when merging into `main` an...
e.g. if something like this happens: https://github.com/ralexstokes/ethereum-consensus/pull/220 right now we get an opaque error but we should be able to provide more information, even field by field about which thing(s)...
some of the beacon APIs return different status codes in the 2XX range to indicate different notions of success e.g. https://ethereum.github.io/beacon-APIs/#/Beacon/publishBlock 200: `The block was validated successfully and has been...
it would be handy for debugging, etc. to have a command line utility that is just a thin wrapper over the various API methods: `$ beacon-api-client --endpoint http://NODE_URL node version`...
this issue requires a bit of an invasive change to implement some kind of epoch-level cache I imagine there is such a cache available from the `Context`, and `get_beacon_committee` can...
right now this repo only supports the JSON codec for the API although the beacon APIs support a SSZ codec for some methods
Ideally there would be static test vectors that replicate the request/response cycle of a consumer/provider of this API but we don't really have anything like that right now It would...
the `spec-gen` utility is now idempotent let's add a CI job to make sure this is the case it would do something like: when there is no change to either...