Currently , adding new header bytes is supported by header serialization, but unparsed bytes are not stored in Header, thus roundtrip property is broken. There is need to add unparsed bytes to Header and then at some point in when nearly all the nodes are updated it will be secure to add new bytes.
This done in this PR, with new bytes being accounted by clients >= 5.0.22 version only after 7.0 protocol activation (so 7.0 would be breaking for clients < 5.0.22)
close #2150
Currently , adding new header bytes is supported by header serialization, but unparsed bytes are not stored in Header, thus roundtrip property is broken. There is need to add unparsed bytes to Header and then at some point in when nearly all the nodes are updated it will be secure to add new bytes.
This done in this PR, with new bytes being accounted by clients >= 5.0.22 version only after 7.0 protocol activation (so 7.0 would be breaking for clients < 5.0.22)