Core Updates & What’s Next

Dev update

Zano
Zano
Nov 20, 2019 · 4 min read
Image for post
Image for post

Hi Everyone, it’s been a while since our last update but today we want to give you a more in depth overview of developments that have been accomplished over the past few months.

With the hard fork to upgrade the POS consensus on September 21st these are the major changes that happened at that time.

As stated at the time of the fork the main objective was to secure Zano TX history to make 51% attacks practically impossible.

We also:
• Changed POS rule that previously would not allow locked coins to participate in POS mining as a result time-locked coins now immediately participate in POS mining.

• Implemented a more strict policy on staking to secure and prevent the consensus from a potential take over with major POS hashrate attack.

• Patched the difficulty adjustment algo to avoid potential strong fluctuations.

Multi lingual interfaces

New Database Implementation

With all that said on the technical side and reasoning behind testing MDBX, we were able to include both LMDB and MDBX in the latest build due to Zano’s architecture being very flexible. If you want to test out MDBX you can do it by specifying

--db-engine=mdbx

(if you choose to test this out please note that the entire blockchain will re-synchronize, Also make sure to update your git submodules if you are building from source)

git submodule update --init --recursive 

Bug Fixes and Minor Enhancements

Core & global

• fixed multi-precision overflow bug in fork choice rule

• global Unicode support improved: 1) it’s okay now to have complicated Windows username; 2) it’s okay if path to Zano includes non-ascii symbols; 3) simplewallet can work with non-ascii wallet file paths

• improved PRNG manipulation safety (for automated tests)

• merged DB basic_key_value_accessor and solo_value fixes from Boolberry

• NTP tools & core time sync checking were greatly improved

• terminal handler implemented for both daemon and GUI, it will help in complicated crashes investigation (if they ever happen)

• newly passwords should satisfy limited ascii-like character set

• wallet: safety improved when saving data: free space and possible write errors are taken into account

• wallet: fixed incorrect wallet’s balance on certain stages of contract processing

• core: very old pre-hardfork nodes are now filtered out by P2P subsystem to avoid meaningless traffic

• API: fixed resync market issue

• core: fixed rare multi-thread synchronization issue

• P2P: fixed a rare case of double connections between nodes

• P2P: fixed a rare case of invalid handshake handling

GUI

• GUI: fixed a bug with P2P state config not being saved before 30 min online period

• GUI: option — enable-qt-logs can be used to switch on Qt internal logs and forward it to the main log system

• GUI: animated icons and many minor fixes and improvements (including translations)

• GUI: issue with incorrect balance showing in wallet during certain stages of contract processing this has been fixed

Simplewallet

• simplewallet: wallet contracts RPC API implemented:

contracts_send_proposal, contracts_accept_proposal, contracts_get_all, contracts_release, contracts_request_cancel, contracts_accept_cancel

Deamon

• daemon: marketplace service enabled through new API and command-line options

What’s Next

The first being the mobile wallet which is currently under development. As you may have noticed on the github we are testing a few different things to use for the app. Time frame on this is 1–2 months depending on several factors regarding what code base we decide to use for it or if we go the route of writing it from scratch, this still has not been decided on yet.

Secondly, as we mentioned in other articles, we are working on implementing a new privacy protocol this is a much heavier task than the one above but we are making progress on it. As soon as our research is completed on it we will have more details on how the upgrade will happen. At some point after that there will be a hard fork to implement the new protocol.

As was mentioned earlier today in the discord both Andre and Pavel are currently out of the office on a business trip. This has been a planned business trip to Zurich to meet with potentially new business partners, following this they will travel to Copenhagen to meet with a Journalist from a crypto related media outlet. Stay tuned for more details!

Zano News

Zano is a next generation CryptoNote Cryptocurrency, focused on Privacy, E-commerce and Scalability.

Medium is an open platform where 170 million readers come to find insightful and dynamic thinking. Here, expert and undiscovered voices alike dive into the heart of any topic and bring new ideas to the surface. Learn more

Follow the writers, publications, and topics that matter to you, and you’ll see them on your homepage and in your inbox. Explore

If you have a story to tell, knowledge to share, or a perspective to offer — welcome home. It’s easy and free to post your thinking on any topic. Write on Medium

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store