Nano has officially announced the mainnet launch of Nano V19.0 codenamed “Solidus” in their blog (Solidus is a golden Roman coin, in case you wondered). The release should further polish Nano, helping it to become a leading digital currency.
A solid amount of new features
The V19.0 brings along several new important features that should benefit Nano’s P2P network. Here are the most notable ones:
- Thanks to the introduction of WebSockets, Nano node notification mechanisms can now work more efficiently, providing an easier to use solution to receive notifications
- The switch from User Datagram Protocol (UDP) to Transmission Control Protocol (TCP) brings many benefits, such as substantial bandwidth reduction and lower resource usage. What’s more, because TCP has a wider support, this switch should make it easier to integrate Nano with other networks
- The Nano network is made more immune to spam attacks with the introduction of Dynamic Proof-of-Work. By design, Nano can be prone to spam attacks due to being fee-less; the combination of Dynamic Proof-of-Work and several other software mechanisms now allows Nano to track spammers and automatically increase their PoW difficulty
- Perhaps one of the most important new features is Confirmation Height. In the future, it will make it possible to make the DAG network more secure and efficient, decreasing the number of elections needed
The complete list of new features can be found here.
Things to keep in mind while upgrading
Nano team has created a list of things anyone wishing to upgrade should take into consideration. Here are the most important points:
- When upgrading from version V17.1 and earlier to V19.0, sequential database upgrade will be carried out, impacting the ability of the node in question to participate in P2P network. Nano advises to upgrade to V18.0 first for the upgrade to go as smooth as possible
- From Solidus release onwards, all addresses emitted from the node will use the nano_ prefix instead of xrb_, continuing the rebranding process
- It is recommended to verify network ports setup and consider setting up a new node on internal networks during the upgrade for users running production services
All the recommendations can be found here.