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

..

phase0

require blocks to be ordered consecutively in block range request

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

phase1

Merge branch 'dev' into v012x

2020-05-19 10:02:18 -06:00