New Dynastycoin 2.1.3 version in beta testnet
Following the problems encountered since the new ones ASIC cryptonight entered circulation and connected to our blockchain we proceeded to create a New Dynastycoin Version 2.1.3 which mainly includes the new algorithm LWMA extension which is able to thwart all hash attacks on the blockchain.
In the current version 2.1.2 we use the algorithm Zawy v.1 which proved to be useful having solved the previous problems of bigminers that blocked the production of blocks, sometimes even for a few days. About this new algorithm LWMA extension latest version by Scott Robert you can find information and code on github by clicking here.
The algorithm allows us to keep the cryptonight mining algorithm version without switching to the cryptonight v.7 version as Monero recently did, at least for now.
The problem that is arising now after the introduction of the New Asic for cryptonight is that the too much power produced by some Miners has created alternative chains, which have been canceled and restored, creating problems for all pools.
We are now running the new 2.1.3 version 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 wallets more stable, with less risk of crashes.
- Added Enable_blockchain_explorer support which will allow Pools to directly and more easily implement the Dinastycoin blockchain explorer
- For the Linux versions the daemon also supports the block Falling Host which automatically blocks the IPs that create problems for the blockchain
- Added Fee Address option to daemons
- Added the mnemonic seed Import and export for the simplewallet which 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 Wallet GUI
A fork is required to switch to the new LWMA algorithm. When the version is made available we will communicate the exact block number in which the new fork will take place