This week in development, we’ll be moving a large amount of bugs to beta testing in the coming week. We’ve updated block rewards and masternode reward distribution to be more accurate according to the specs outlined in the whitepaper and dev wiki. We fixed an issue with openssl that caused compilation errors on some systems. We removed the unnecessary fees from coin stakes. We fixed some old bugs with a method called ConnectBlock and another method that saves proof of stake hashes. We fixed the bug that caused block times to be inconsistent, they should be much closer to 60s now. And we also fixed a bug that caused blocks to be minted from the future. As you can see we have been very busy this week, and we are making very good progress towards redemption and release.

Blockchain bugs moved to testing

Staking bug (moved to testing)

Bug - Staking isn't consistent with the rewards or time.

Details - We are trying to make sure that the staking is more consistent and that we can get the reward times closer and more consistent.

Block time is still not consistent around 60 seconds (moved to testing)

Bug - Block time can be between 20 - 300 seconds

Details - This isn’t really a bug it’s more of a performance tweak. It is common to see different block times. A block contains reference to the previous block and the solution to a mathematical problem. The block time isn’t dependant on the time, however whenever the block gets solved, the block time is said to be equivalent to the amount of time taken to solve for that particular block.

Sometime's new block has a lower timestamp than the previous block. (moved to testing)

Bug - Block number 'n' must have a higher number of timestamp than the previous block.

Details - This seems like it could be related to the rescan API, but we need to dig into this further to make sure.

Sending large amounts of DIVI get split up (moved to testing)

Bug - When you are receiving large amounts of funds that it would show up as one transaction. It splits up the transaction into 50k transactions and spams you until it is done.

Details - We are looking into this and it seems it might be related to a hidden privacy “feature”. We should have this fixed next week.

Active blockchain bugs

fundmasternode -> "Transaction is not valid" on MN setup

Bug - COIN = 100000000 Divi Satoshi's (aka 1 DIVI)

Details - This has been fixed, it looks like the removal of this multiplication factor was dropped and the node allocation funding went down to 0.001 divi for a copper etc.

Masternode fund allocation bug/error

Bug - COIN = Instead, for copper, only 0.001divi is allocated and 0.003divi for silver etc.. After running the allocate funds command, then a corresponding transaction is given. This transaction confirms that only 0.001divi was allocated, and can also be verified using the list accounts command. When trying to proceed with the fund masternode command, then the whole thing fails as the transaction is deemed invalid for the masternode level.

Details - This has been fixed, it was related to the previous bug.

Remaining security features

First run info for security hygiene and wallet setup

Details - This is to help inform the user on best practices around crypto security.

Remaining - This will be a link to our wiki where we will store all of this information and keep it up to date. We think that this is very important for users, both new and experienced. We are working on this and will be asking the community to pitch in and help keep it current.

Seed phrase on first run GUI

Details - This allows the user to get their seed phrase so that they can restore if needed.

Remaining - We have started work on this and have flows for the development team. Currently this already works via command line interface.

Recover with seed phrase GUI

Details - This allows a user to be able to restore their wallet with a seed phrase.

Remaining - We have started work on this and have flows for the development team. Currently this already works via command line interface.

Password for unlocking GUI

Details - This will allow the user to require a password before unlocking the desktop wallet.

Remaining - We have already worked on this along with the lock/unlock feature.

Dev team build up

We are proud to announce that we have enlisted a new lead blockchain engineer, Yuri Oleksyshyn. He is an extremely experience blockchain engineer who has a wealth of knowledge regarding Dash, PIVX and other Proof of Stake protocols. He outperformed everyone on his technical interview, it was the best we’ve ever seen since starting Divi.

He will be added to the site in the coming week and his LinkedIn profile will be accessible through the link in the description. Before you ask, yes, he will be adding Divi to his profile as soon as possible.

Please remember to head over and post your questions for our coming AMA.

https://ama.diviproject.org/