January 9, 2020, Weekly Update

Getting technical

Today's update is going to get technical because we are making incredible strides toward launching a revamped ecosystem that is not only easier to use but more efficient overall. Let's jump right in and talk about some of the future technology that users will soon have in their hands.

MOCCI 2.0 prototype

Our primary motivation behind enhancing the MOCCI (masternode one-click cloud installer) is allowing users to deploy and manage a masternode from a mobile device without the need for remote key storage or additional configuration by the end-user. Secondarily, we want to enable faster deployments from the desktop as well.

In other words, we wanted to take this

And turn it into this

Thanks to some innovative thinking and creative refactoring, we can begin to unveil our patent-pending solution to remotely deploying masternodes.

What makes MOCCI 2.0 different?

The O.G. Way

In MOCCI 1.0, there are three primary steps taken to deploy the node.

  1. Masternode funding
  2. Masternode creation
  3. Masternode relay

The funding step is pretty self-explanatory. It's the part where the DIVI collateral is allocated to the masternode using an on-chain transaction.

Masternode creation configures everything locally using your local wallet's private key and records it for future reference.

Finally, the Masternode relay broadcasts the new masternode's existence to the network, which validates it and records it. Once registered, the other peers in the network receive notification and log the node to their local configuration.

With MOCCI 1.0, the creation and relay steps are in permanent unity. This fact is essential to remember.

The new school way

In MOCCI 2.0, we have separated the creation and relay steps to allow for remote broadcast, without taking custody over the user's private keys (this is crucial). Now, the blockchain stores the configuration data required to broadcast as a hex string that can either start the masternode immediately locally or "pulled out" and transmitted from another node.

This methodology is very similar to the SIGHASH_ANYONECANPAY transaction signature that every UTXO-based blockchain possesses.

In simple terms, you can sign and secure your masternode and have another node finish the process for you. This updated process allows us to deploy masternodes from light or full clients with minimal invasiveness and virtually no friction for the user.


A MOCCI 2.0 prototype is working now, and we are making plans to begin integrating it with the current desktop wallet. Users will reap the benefits of this upgrade this quarter, assuming no security vulnerabilities or other risks come to light during testing.

Atomic Swaps

We are successfully executing BTC-to-DIVI atomic swaps on the post-fork testnet now. This single-endpoint solution allows for simple, trustless, peer-to-peer trades.

Hasn't this been done?

There is nothing new about the concept behind Atomic Swaps. However, we have spent a significant amount of time researching and designing a system that improves upon the technology in a way that makes it ready for mainstream usage.

Our core intention is creating a production use case for Atomic Swaps. Our API enables developers to use 1 API call via command line or HTTP POST that can broker an Atomic Swap between Bitcoin and Divi.

The O.G. way

In the original implementation by Decred (which is also possible with our extended API), an atomic was executed procedurally by the user.

  1. User 1 initiates an atomic swap on chain 1
  2. User 1 gives the secret hash to User 2
  3. User 2 creates a participating atomic swap on chain 2
  4. User 1 and 2 redeem the atomic swap contracts on their respective chains

The new school way

Divi's implementation improves the original by automating the entire process for atomic swaps. Send a single HTTP request to initiate an exchange. And it will automatically execute one. Just be mindful that blocks need to be mined for the atomic swap to execute.

  1. The user sends a post request to initiate an atomic swap
  2. Atomic Swap server creates an initiate atomic swap contract on chain 1
  3. Atomic Swap server creates a participate atomic swap contract on chain 2
  4. Atomic Swap server waits for at least 1 block confirmation on both chains
  5. Atomic Swap server redeems both atomic swap contracts


This technology is still undergoing testing but is getting closer to a release candidate every day. If you want to get started with Divi atomic swaps and help contribute to its development, take a look at our examples section.

Divi 2.0 preview

Debit cards

We are currently working through the Divi 2.0 fintech features. We know users are especially excited about the Divi Debit Cards, so here is a quick preview of how the UI looks!


Desktop performance dashboard

Users will never have to wonder how their node is doing again with the Divi 2.0 performance dashboard.



Geoff McCabe interview with Rice Crypto

Divi is the best masternode coin to watch for 2020 according to Go Crypto Wise


DigiByte DigiAssets Silver Divi Masternode - Interview

PolisPay integration and giveaway

Nick Saponaro Masternode presentation at ChainWise