You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The value fields for qbft consensus wire messages were refactored to any protos in #1214, this was released in v0.11. The previous values has not been removed yet (for backwards compatibility), but this is causing double the amount network bandwith which is a problem for synthetic blocks. And it is time to compete the upgrade and drop support for old versions.
Note this will remove support for v0.10 and before, so v0.13 will only be compatible with v0.11 and v0.12
Proposed solution
Remove support for deprecated fields.
The text was updated successfully, but these errors were encountered:
Removes deprecated consensus wire protocol fields. New fields were introduced in v0.11, so this removes compatibility with v0.10 and older.
category: refactor
ticket: #1555
Reverts "reserved" fields since they are required to calculate correct hash when verifying signatures. Instead just stop using fields.
category: bug
ticket: #1555
Problem to be solved
The value fields for qbft consensus wire messages were refactored to any protos in #1214, this was released in v0.11. The previous values has not been removed yet (for backwards compatibility), but this is causing double the amount network bandwith which is a problem for synthetic blocks. And it is time to compete the upgrade and drop support for old versions.
Note this will remove support for v0.10 and before, so v0.13 will only be compatible with v0.11 and v0.12
Proposed solution
Remove support for deprecated fields.
The text was updated successfully, but these errors were encountered: