Releases: spacemeshos/smapp
Release v1.7.7
Important
The version v1.7.5 (released only as beta) of go-spacemesh introduced a bug into the code that handles incoming ATXs. This bug would cause the node to store invalid data in the database and could lead to a node disagreeing about the state of the network with other nodes. This version fixes the bug. If you are running v1.7.5 you should upgrade to v1.7.7 as soon as possible and rebuild your state.db, either via quicksync, from a backup from before you upgraded or by full syncing from genesis.
Compiled Binaries
What's Changed
- Fix of the error in Smesher Log: handle properly new node events and do not throw errors in case there will be added new ones by @brusherru in #1796
Full Changelog: v1.7.6...v1.7.7
Contributors
Assets 2
Release v1.7.6
Important
The version v1.7.5 (released only as beta) of go-spacemesh introduced a bug into the code that handles incoming ATXs. This bug would cause the node to store invalid data in the database and could lead to a node disagreeing about the state of the network with other nodes. This version fixes the bug. If you are running v1.7.5 you should upgrade to v1.7.6 as soon as possible and rebuild your state.db, either via quicksync, from a backup from before you upgraded or by full syncing from genesis.
Compiled Binaries
Release v1.7.4
Release v1.7.1
Warning
Ensure you are running v1.6.x before upgrading to v1.7.0, if you skip v1.6.x your node will not be able to fully migrate its local state. Upgrading from v1.6.x to v1.7.0 will require a time consuming database migration that optimizes how the node stores state locally and will not allow you to downgrade to v1.6.x again. The upgrade process requires you to have at least the same amount of free disk space as your current database size for the duration of the migration.
Compiled Binaries
What's Changed
Go-spacemesh v1.7.1