What to Expect on Launch and Looking Towards the Future

We want to thank our community for being so patient with us. Recently our Co-Founder, Nick Saponaro, noticed a few people might have become “slightly” concerned if we are still on track.

Launching a Blockchain is a task that requires an incredible amount of attention to the details. It is insanely difficult to decide at which point you’ve prepared enough for unknown unknowns. Unlike any other form of software development, many decisions are immutable and must be perfect from the first go. We love this challenge, and we are working around the clock to deliver a result we are proud of. We know you are excited, and so are we.

What features will be shipping on the 2nd of July?

Blockchain features:

  • Five-tier Masternode — Manual Setup Only
  • Diamond 10,000,000
  • Platinum 3,000,000
  • Gold 1,000,000
  • Silver 300,000
  • Copper 100,000
  • Lottery Blocks
  • Staking Awards
  • Dynamic IP Masternode Capability
  • Genesis Block Documentation

Blockchain features completed, but disabled for further testing:

  • Human readable addresses (code is in place; disabled until wallet team storage specs are available)
  • PIN Code Transactions
  • Masternodes with multiple accounts (code is in place; disabled pending Divi process specs)
  • Masternode payout to different account addresses (code is in place; disabled pending Divi process specs)
  • DIVI governance (code is in place; disabled pending Divi process specs)
  • Voting (code is in place; disabled pending Divi process specs)

Desktop Wallet features:

  • Send/Receive
  • Staking
  • Wallet Locking
  • Addresses

Mobile wallet features:
Not available at launch; pushed out for Q3 release

Development features:

  • API library

Web features:

  • Blockchain explorer
  • Blockchain site documentation
  • Desktop wallet documentation
  • Brand new website

What didn’t make it into the launch?

  • Multi-factor Authentication
  • Mini Blockchain
  • Vaulting
  • Master Node P2P Storage
  • Atomic Swap Compatibility (requires BTC v0.14)
  • Masternode setup in the desktop wallet
  • Mobile wallet (iOS & Android)
  • One-click masternode setup

What went into the decision process for pushing features out?
Mainly money and time were the factors in the choices that were made. When I first took on the role as the head of development, I said we would have to make decisions on what would make it into the initial release. When I said that, I knew that we would have to cut features and delay them for a later release timeframe. At that time I wasn’t sure how much would have to be cut. When looking at a feature or piece of a release, you have to know what the MVP (Minimum Viable Product) is and how not releasing it could profoundly impact your launch. With new technology like blockchain, it isn’t so black and white.

With a burn rate of over USD 120k a month, just for development, we needed to make sure to get the new coin minting online to ensure that we had funding in place for future development. The way we prioritized features for the blockchain was on our original promise and white paper. That was one part that we wanted to get the most done and completed. Given that we could not really move the date, we had to look at defining the features better and picking the ones that mattered most without painting ourselves into a corner. But this included things like putting the BTC14 features off till after the launch. Hence, we’ll have to build that after the Divi Launch.

The blockchain though, all of the key features were built out that we were able to define well. There is some work that still needs to come from the community to define some of the features that will end up being used, for example, the Divi Governance. The system is a robust feature set on the back end. The system at the initial launch will be feature complete, and the blockchain is done in such a way that we can upgrade and polish it without breaking or forking.

The wallets were started much later due to the effort needed to get the backend wired. There is fundamentally much tooling that will be done, but the initial wallet is designed to set up a masternode, or wallet but not both due to some restrictions with the infrastructure. This will not stay that way, but to get something into the hands of fans it was decided this would allow us to hit the extremely tight deadline just in time to actually get it tested. This means you can expect frequent releases for a week or two as the code base is stabilized and the rest of the ‘smart wallet’, you can expect the features to come incrementally with a two-week cadence to engineering. One of the features that were cut initially, but will go in within the month, is our true one-click installation that allows anyone to set up a masternode easily and with no technical knowledge. As we were coming down to the wire, we realized it was not possible to get the other features and that done and adequately tested before launch.

This initial version deals with many issues with previous installs, configuration clean up and many other things. For example, if we have early beta testers or other Divi team members running the new wallet and they were using the older blockchain for Divi testing, then the wallet needs to be smart enough to deal with that in any of the supported platforms. I decided that it was more important than finishing the one-click remote deploy so we could get the blockchain and wallet out.

The week after the 25th we will be doing a lot more extensive testing with our internal testing team along with the beta testers on the testnet. Then on the 30th, we will be doing an open beta on the testnet of the masternode features before they get released to the public. The side effect is that this will also allow everyone to start their masternodes at the same time and ensure that they have been properly tested.

What development efforts can we expect after the 25th?
One thing that I would like to address is what you can expect after the June 25th launch as far as development and releases go.

Blockchain features remaining to be delivered:

  • Multi-factor Authentication
  • Mini Blockchain
  • Vaulting (including Bonus)
  • Master Node P2P Storage
  • Atomic Swap Compatibility (requires BTC v0.14)

Wallet features remaining to be delivered:

  • One click masternode install options (desktop and cloud)
  • Single-computer masternode install
  • Vaulting
  • Atomic Swaps
  • Multi-factor Authentication

Mobile apps:

  • Multiple account creation and management in-app
  • Easy spending proposal flow for shared wallets and group payments
  • BIP32 Hierarchical deterministic (HD) address generation and wallet backups
  • Device-based security: all private keys are stored locally, not in the cloud
  • Payment protocol (BIP70-BIP73) support: easily-identifiable payment requests and verifiable, secure bitcoin payments
  • Mnemonic (BIP39) support for wallet backups
  • Multiple languages supported

As always, thank you for your support. We are excited to finally deliver what we’ve been working on so passionately!

Roadmap 2018 Q3–2020 Q1

Q3 2018
Mobile app release (Android/iOS)

  • Multiple account creation and management in-app
  • Easy spending proposal flow for shared wallets and group payments
  • BIP32 Hierarchical deterministic (HD) address generation and wallet backups
  • Device-based security: all private keys are stored locally, not in the cloud
  • Payment protocol (BIP70-BIP73) support: easily-identifiable payment requests and verifiable, secure bitcoin payments
  • Mnemonic (BIP39) support for wallet backups
  • Multiple languages supported

Q4 2018
Updates to the blockchain

  • Vaulting
  • Atomic swaps
  • Mini blockchain
  • Masternode P2P storage

Q1 2019

  • Marketplace web plugins (WordPress, Magento)
  • Desktop app new features
  • UX updates

Q2 2019

  • Mobile app new features
  • More coins added
  • Exchange support
  • UX improvements

Q3 2019
*Updated masternode system support

Q4 2019

  • Security updates for all apps