protolambda

If other clients are in for a change too, we can change it. But don't want to break the working setup of anyone right before spec freeze.

@prestonvanloon Can you form a concrete counter proposal, to be executed after spec freeze, if it works for everyone?

Was thinking of something more radical. If we give up on readability, there should be much better options.

So pretty much all data, unless it's not a SSZ object, will also be available as ssz-encoded raw bytes in the next testing release. See https://github.com/ethereum/eth2.0-specs/pull/1320 An example can be...

@prestonvanloon there are a few small files that just say things like "there are 10 deposits to read from ssz files", "there are 6 blocks to read", "BLS required here"....

The problem here is that we are hosting mainnet-configuration tests, which are quite large. Too large really for a normal git repository. But we still wanted to version them. And...

Ah that's crazy, I wonder if one of the teams is still pulling in the complete repository every CI run. Will check with them, and see what others think. I...

@karalabe you can download the test vectors from the releases like this: ```make SPEC_VERSION ?=v1.5.0-alpha.3 download-tests: mkdir -p tests/spec/eth2.0-spec-tests wget https://github.com/ethereum/consensus-spec-tests/releases/download/$(SPEC_VERSION)/general.tar.gz -O - | tar -xz -C tests/spec/eth2.0-spec-tests wget https://github.com/ethereum/consensus-spec-tests/releases/download/$(SPEC_VERSION)/minimal.tar.gz...

@ericsson49 Great, thanks for this work :). Regarding the problems: - file size: agreed, I would like to change the spec tests in general to share parts of state, and...

@JustinDrake What do you think? Does it make sense to prioritize this, even though the current `hash_to_G2` is non-final/unsecure?