OpenSource Onslaught

Exactly ten days ago, a developer from the Particl community brought an issue regarding Divi’s improper usage of the GNU General Public License 2.0 attached to the Particl Desktop application to our attention. The following addresses the situation and provides remedies to any actions that breached the license:

Over a year ago, when we began development on Divi Desktop, we forked Particl and started working with some of the code as a framework. Our short timeline and the necessity to build OS-agnostic software are the reasons we use Particl's AngularJS + ElectronJS framework as a base very advantageous.

Since the day we forked Particl, many proprietary features have been implemented, including the Divi MOCCI (Masternode One-Click Cloud Installer). This fact made it difficult for us to make the repository open source immediately. According to our lawyers, there is no provision in the license agreement that would cause us to release MOCCI to the public under an OpenSource license. For this reason, we have created a new repo that only includes pieces of the code taken from Particl, credits Particl for the fork, and does not include MOCCI in the codebase.

The Divi Desktop Public repository is available for public viewing now, and the license is here.

Additional measures will be taken, if necessary, to ensure 100% compliance with the license.

I want to make it clear that it was never Divi’s intention to breach the GNU License. We are not IP attorneys and, although this may seem like “basic” knowledge to some, the scope of this law is immensely complicated, and it was crucial that we take the proper steps to rectify the issue.

I would also like to personally take responsibility for this misstep and apologize to the Particl development community for my misunderstanding of this law. We appreciate the hard work that you have put into the Particl project and wish you great success in your endeavor.

OpenSourcing Divi Core Development

After the incident described above, I went to the team, and we had a philosophical discussion regarding the Divi Development process. As I’ve mentioned in previous blogs, when it comes to Divi Core, we adhere to a development process that keeps everything private until we are prepared to push production-ready code to the public.

Moving forward, to keep our development process more transparent, we will be creating task-based branches on GitHub and pushing development-only code to them so that users, investors, and any other interested parties can get a more detailed scope of the work we are doing.

The process will look something like this:

A new task is created in our product management back end. A new branch is created, titled and numbered based on the issue report, and work begins on task. The task is completed, and a pull request is created to merge the code into the master branch. QA testing and security auditing take place on the branch in question. Once the code is deemed complete, QA tested, and production-ready, it is merged.

We hope this new, more transparent methodology will encourage members of the community to become more actively involved in development while providing a resource that shows proof of progress as we complete the items outlined on our roadmap.

The Divi Mobile Smart Wallet is coming together nicely, and final testing on wallet-based, backup, multi-signature, and transactional functionality is going well. However, those features are just the basics. What makes the Divi wallet stand apart are the additional features that will be available on zero-day.

Mobile MOCCI

We have determined the scope and requirements and a diagram of high-level flows for how the mMOCCI (Mobile Masternode One-Click Cloud Installer) will work is in use internally.

The deployment method we are building will provide the most hands-off user experience possible. Tap Deploy, pay for the service, and your device will receive a notification once the process is complete.

Divi Smart Links will enable users to share a link with a friend via SMS, email, or virtually any other medium of communication that contains $DIVI. Once the counterparty clicks the link, they will be sent to download the Divi Mobile Smart Wallet, and voila, they are the proud owner of some shiny new $DIVI. This feature enables users to experience a frictionless on-ramp to the project and empowers the network by increasing the number of Divi hodlers.

Crex24 Wallet Maintenance

As of the time of this writing, Crex24 Divi wallets are under maintenance due to an issue with inter-wallet transactions (sometimes called “move” transactions). These transactions can cause many functional issues, which is why the method no longer exists as of version 1.0.3 of Divi Core.

Our team is in direct contact with theirs, and we are working to resolve the issue. As of this morning, it seems the Crex24 team has determined the root cause and should have deposits and withdrawals re-enabled soon. We will keep the community apprised of any updates on this matter. Keep an eye on our Twitter and Telegram for the latest information.

We have partnered with Grow Your Base on a new initiative that will encourage users to perform specific actions, and in return, they will earn a bit of cryptocurrency. The campaign is live now, so go check it out!

As always, have a great weekend, and if you have any questions, find us on Telegram or the Forum