Jacek Sieka 607e23949c

require blocks to be ordered consecutively in block range request ...

Per the spec, if I request range 5-10, it is permissible for a client to
answer with block 7, 9 - even if the blocks 5, 6 and 8 exist.

Because blocks 7 and 9 cannot be validated as they arrive in such a
request, it seems better to close this gap - this update adds the spec
language that forbids well-behaving clients from answering this way.

2020-05-20 20:29:37 +02:00

..

beacon-chain.md

hww feedback for finality rewards fix

2020-05-20 10:12:57 -06:00

deposit-contract.md

reorg specs by fork and move ssz out to own folder. make all of the build and link changes to support move

2020-01-10 11:55:13 -07:00

fork-choice.md

Merge branch 'v012x' into ffg_lmd_vote_consistency

2020-05-05 13:40:27 -06:00

p2p-interface.md

require blocks to be ordered consecutively in block range request

2020-05-20 20:29:37 +02:00

validator.md

Merge pull request #1799 from ethereum/bls_v2

2020-05-18 07:35:49 -06:00