Nano Node v19 marches onto the primary internet
We’re happy to announce the discharge of the most recent model of the Nano node software program, in what is without doubt one of the most in depth protocol updates thus far. By way of a group of great updates and smaller focused optimizations, Solidus brings the resilience and immutability essential to foster belief and confidence in Nano as a number one digital forex.
The V19.Zero launch wouldn’t have been doable with out our military of neighborhood beta-testers and contributors who’ve dedicated to offering probably the most environment friendly and complete beta testing thus far. Their work has been instrumental in guaranteeing that Solidus is nicely ready for launch and we want to lengthen our appreciation to the entire individuals concerned in contributing to this launch.
Earlier than we get into the good options, there are some necessary improve concerns to name out. All node operators, providers and exchanges integrating with Nano ought to carefully assessment these particulars earlier than upgrading.
Upgrades from variations V17.1 and earlier to V19 will contain a sequential database improve and impression participation of the node on the community. RPC calls will probably be unavailable for an extended time frame amongst different impacts. It’s extremely really helpful that nodes are upgraded to V18.Zero first or a V18.Zero ledger is acquired and used when upgrading to V19.0.
Affirmation monitoring concerns
The addition of affirmation peak to the database requires the node to validate that blocks are confirmed earlier than the cementing can happen. This course of can take as much as 24 hours or longer to finish however received’t impression participation on the community. For integrations watching confirmations, the present HTTP callback, block_confirm RPC and confirmation_history RPC strategies will proceed to perform as earlier than, nonetheless it’s required that monitoring of confirmed block hashes outdoors the node is completed to keep away from potential duplicate notifications from inflicting points. This was a requirement in earlier variations and stays the identical with V19.
For these seeking to make the most of the brand new WebSocket affirmation subscription or new confirmed discipline in block_info RPC responses, particular concerns ought to be taken if implementing earlier than affirmation peak updates are full — discover out extra particulars see the V19.Zero Launch Notes.
Emitting nano_ prefixed addresses
On this and future variations, all addresses emitted from the node will use the nano_ prefix. It would proceed to help enter for xrb_ prefixed addresses, however all providers should confirm they’re correctly set as much as deal with the node outputting nano_ prefixed addresses.
Reside community visitors over TCP
Reside community visitors over TCP is now obtainable and operates on the identical port (7075 for foremost community, 54000 for beta community) because the bootstrapping community that was already obtainable over TCP. Due to this, present community setups which are open inbound and outbound on port 7075 for TCP ought to perform as anticipated with V19.0. For these operating manufacturing providers, it’s nonetheless really helpful to confirm community ports setup and contemplate establishing a brand new node on inside networks to make sure it might join and take part on the primary community earlier than manufacturing nodes are upgraded. Particulars on checking this may be discovered within the V19.Zero Launch Notes below Improve Notices part.
Different gadgets to assessment
New configuration choices have been launched to permit tuning of sure behaviors and useful resource utilization on the node. This consists of energetic elections measurement and bandwidth limiting together with another probably helpful choices to regulate. For particulars on these and different updates to RPC calls, CLI instructions and extra, assessment the V19.Zero Launch Notes.