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
Use the logic which was part of the protocol and persisted in the blockchain.
Actual behavior
When a 1.1.0 node sync from scratch with test network, the 1.1.0 node failed to sync due to differences in mem_accounts table (vote column) leading to change in delegate list order, the change in order of delegate resulting in unrecoverable fork3, here is the logs for more information.
The vote column in mem_accounts is impacted due to the changes #716 introduced in 1.1.0, before this change there was a difference of 1 beddow due to the way we handled javascript number, after the fixes in this PR #2187 the issue was fixed, however this changes will invalidate the blockchain.
Steps to reproduce
Run 1.1.0 node and sync from scratch with the test network
Which version(s) does this affect? (Environment, OS, etc...)
1.1.0
The text was updated successfully, but these errors were encountered:
Expected behavior
Use the logic which was part of the protocol and persisted in the blockchain.
Actual behavior
When a
1.1.0
node sync from scratch with test network, the1.1.0
node failed to sync due to differences inmem_accounts
table (vote
column) leading to change in delegate list order, the change in order of delegate resulting in unrecoverable fork3, here is the logs for more information.The
vote
column inmem_accounts
is impacted due to the changes #716 introduced in1.1.0
, before this change there was a difference of 1 beddow due to the way we handled javascript number, after the fixes in this PR #2187 the issue was fixed, however this changes will invalidate the blockchain.Steps to reproduce
Run
1.1.0
node and sync from scratch with the test networkWhich version(s) does this affect? (Environment, OS, etc...)
1.1.0
The text was updated successfully, but these errors were encountered: