Development this Week - Aug 24, 2018

Development progress

This week we moved 14 GUI issues to testing and the beta testers have their hands on the latest builds. The wallet team is now adding the one-click masternode install into the wallet now.

Now that most of the bugs in the core have been closed or resolved, the reward structure is being fine tuned so that it is more in line with the whitepaper specifications.

The blockchain and wallet teams are working together wherever necessary to support each other in terms of required features and the product management flow that we have adopted seems to be much more efficient than what we had before.

The legal structure in Lithuania is being developed and a legal team has been contracted to begin work out there.

As we get closer to redemption, we encourage everyone in the community to engage with one another in our new forum at forum.diviproject.org. Sign up and join the conversation.

Also for those of you who are interested, you can now track our progress on the Divi GitHub Public Project Board.

First run info for security hygiene and wallet setup (Moved to testing)

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

Transaction not valid on funding MN setup (Moved to testing)

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 (Moved to testing)

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.

Seed phrase on first run GUI (TESTED & COMPLETED)

Details - This allows the user to get their seed phrase so that they can restore if needed.
Remaining - We now have this working on the blockchain and working in the CLI. We will be moving this into the client and moving to testing shortly.

Recover with seed phrase GUI (TESTED & COMPLETED)

Details - This allows a user to be able to restore their wallet with a seed phrase.
Remaining - We now have this working on the blockchain and working in the CLI. We will be moving this into the client and moving to testing shortly.

Password for unlocking GUI (TESTED & COMPLETED)

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.

Blockchain bugs moved to testing

Staking bug (TESTED & COMPLETED)

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 too.

Block time is still not consistent around 60 seconds (TESTED & COMPLETED)

Bug - Block time can be between 20 - 300 seconds
Details - This isn’t really a bug it’s more of a performance tweak. It's common to see different block times. A block contains a reference to the previous block and the solution to a mathematical problem. The block time isn’t dependent 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.

Sometimes new block has a lower timestamp than the previous block. (TESTED & COMPLETED)

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 gets split up (TESTED & COMPLETED)

Bug - When you are receiving large amounts of funds it would show up as one transaction. It splits up the transaction into 50k transactions and spams you until it's 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

No bugs currently

Remaining security features

No remaining features