Arqma status update 4.11.2020
Hello ArqManians.
Since our last release at the end of August, many of you have been regularly asking — ‘When are the service nodes coming to the ARQ-Network’?
We would like to let you know that our dev team has been coding hard, day and night, for many months on a private repository which will adapt the current codebase to integrate the anticipated service nodes into our ARQ-Network. The integration of this new technology into our base layer is not a trivial code implementation and has some impact to the economy of the ARQ-Network itself.
As you may already know ArQmA is a fork of Monero and a big part of the codebase has been refactored to fit the needs of the Core Developers. In fact, the working implementation of service nodes in the Cryptonote ecosystem is LOKI, but LOKI’s codebase is not really compatible with ArQmA for various reasons. Therefore we have rebased the core code to prepare for the integration. During the last few months, the cmake file structure has been totally reworked to fit perfectly alongside, and also the guidelines of modern CMake and external libraries have been updated to the latest versions too, plus the core code was adapted to the latest functions of those libraries. Nevertheless our developers have created a base for the integration but needed to take into account a large overhead.
The block explorer has been adapted to the new codebase and prepared for future references which include Service Node integrations. We are happy to say that all non-secure functions have been removed from the explorer codebase. We no longer use JavaScript or cache anymore. No information or code is kept or executed on the client side, everything now happens on the server side. Now, only the strongest TLS ciphers are forced and accepted by the server.
Recently while extensively testing an alpha commit, the testing team found some important security and stability issues which needed to be fixed before we could bring the nodes to mainnet. One of them was the SN deregistration process, and another was a sync problem caused by zmq on the daemon. This is why we decided to remove this alpha commit, which was pretty big by the way! We are pleased that this commit is progressing step by step on the dev branch while key issues are being fixed.
As of today, an implementation of a governance fee is being tested on the stagenet and the daily emission will be reduced to adapt the emission curve to foster a healthy environment for service nodes moving forward.
Recently zmq has been totally refactored and the pool code has been further optimized for the better. As you may have seen, the pool database has been moved to a new server and drastically improved. Actually pool.arqma.com is going strong with a luck factor of 87%. Its is quite amazing. The great Muscleman reworked the universal pool code, which is also compatible with many coins out there, if they would like to implement it.
The ArQmA Dev Team always aims for the utmost security and stability above everything else and will continue to do so, even in the light of a Service Nodes delay.
Hang tight, we have been working on some amazing things, and we cant wait for the day we present to you what we believe is blockchain progression fit for these modern times.
Stay tuned and safu and keep coding!
The ArQmA Team ;-)
