Following the problems encountered since the new ASIC cryptonight have entered service which are connected to our blockchain, we proceeded to create a New Version 2.1.3 Dinastycoin that especially includes the new cipher LWMA which is able to counter all attacks hash at the blockchain.

In the current version 2.1.2 we use the algorithm Zawy v.1 which has been found useful having solved the previous problems of bigminers that blocked the production of the block sometimes even for a few days. On this new LWMA algorithm latest version of Scott Robert you can find information and code on github by clicking here.

The algorithm allows us to keep the version of the cryptonight ministry algorithm without going to the cryptonight v.7 version as done recently by Monero, at least for the moment. 

The problem that is being posed now after the introduction of the New Asic for Cryptonight is that too much power is produced by some Miner and has created alternative chains, which have been canceled and restored, thus creating problems for all the pools.

We are now running the new version 2.1.3 in testnet mode to prove that the updates are effective and do not create any problems for the current blockchain.

In addition to the application of the LWMA algorithm, some bugs have been fixed making the blockchain and the wallets more stable, with less risk of crashes.

  • Added Enable_blockchain_explorer support that will allow the Pools to directly and more easily implement the Dinastycoin blockchain explorer
  • For Linux versions, the demon also supports the Blocking Host block that automatically blocks IPs that create blockchain problems
  • Added Fee Address option to demons
  • Added the mnemonic seed Import and export for the simplewallet that allows you to recover a wallet by remembering a sequence of keywords
  • Added New RPC Commands to the wallet

The version will also be released with the updated GUI Wallet

A fork is required to change to the new LWMA algorithm. At the time the version is made available we will communicate the exact block number where the new fork will occur