Project Update: Core and DPOPS 2021 into 2022

xcash project update

Dear community,

Today, we are starting a three part series of what to expect from X-Cash technology wise.

Today we will discuss what is upcoming with the DPoPS infrastructure and X-Cash Core for the end of the year and the start of next year.

What is DPoPS?

The DPoPS (standing for Delegated-Proof-of-Private Stake) is a brand new and unique Delegate-Proof-of-Stake consensus integrated into X-Cash, an open-source fork of Monero which has since the beginning of the project brought new innovation to the privacy coin space (notably FlexPrivacy, public & private transactions on the same blockchain, from the same wallet).

Updates for the end of the year

Our plans for DPOPS (and xcash-core) until the end of year is to make it more stable, resolve any known issues, and add any performance or compatibility update. There are a few issues remaining at this time, and DPoPS needs to be 100% bug free before we add protocols on top of it. This is mainly due to the fact that protocols like instant send payments not only interact on top of DPoPS, but use a stripped down base of the core code from DPOPS in their code base.

The plan is to include all of these into a xcash-core 2.1.0 update and a xcash-dpops 1.1.0 update that will be released at the same time. To review the code already added to these branches, they are located at

These updates will include (currently added but not limited to):


  • Various enhancements to the server and syncing blocks methods
  • Latest boost and other libraries compatibility
  • Latest Ubuntu Linux compatibility
  • latest GCC compatibility
  • Fix Docker file
  • Various updates to remove cryptnote legacy warnings and various C++ deprecated warnings, or libraries warnings


Testnet Release Date

We have for months needed to setup a testnet for the future of XCash. Not only to have a testnet of the live blockchain, but to safely test new updates and protocols to the DPOPS base protocol. We will also eventually need a testnet once smart contracts are released and other higher level features that will involve the community of developers.

We will use this large update and end of the year timing to setup a testnet and run this update on the testnet before we deploy it to the mainnet. There has been a lot of community support for running a testnet and we really appreciate the community support in the alpha and beta stages, and we want to draw long support for the testnet, just like the block reward is keeping the mainnet support going.

We really want people dedicated to keeping the testnet going. A lot of people have expressed interest in running testnet nodes as extra servers and to continue to run their mainnet servers, or some people have only wanted to participate in the testnet. There are also voters who don't have enough to participate in the mainnet but would like to run a server.

We also don’t want to run 20 servers like we did in the alpha with only 10–15 ‘community servers’, as we have seen, the more realistic conditions the better.

We have come up with a solution that we think will work great for all of the above.

We will run a “open testnet” where anyone can run a server. The requirement is to be in the top 50 to produce blocks just like the mainnet. We will use a forked xcash blockchain (height will be close to current height when we start) and the blockchain will be re forked from the mainnet after 50000 blocks have been produced on the testnet, or 6 months if issues arrive during the testnet. This is to stay current with the xcash values of the mainnet. Everyone will be able to use their mainnet xcash values on the forked testnet (xcash value prior to the snapshot) and will move up and down the ranks just like the mainnet.

We don’t expect servers to have voters like the mainnet, but we expect small voters and or people who are not currently participating at all, to try to participate in the testnet, since the pressure to run a node is very little and your knowledge of the xcash ecosystem will grow.

The incentive to participate in the testnet will be three different types of rewards (with real mainnet xcash) will be awarded each month to the delegate's address on the mainnet.
Basically the top delegate on each of the categories at the end of the month (last block of the month) will be awarded 1 million xcash!

We think that this will give incentive for smaller voters or people not participating in the DPoPS to run their own server on the testnet.

No release date has been given for the testnet and there is still some work to be done on the 2.1.0 and 1.1.0 branches, but we will let you know in advance before the testnet snapshot for round 1.

Next Protocol

Zach had a lot of time during the beta testing phase of DPoPS to research and work on some of the next protocols.

As we have seen with the instant send video (, that protocol is about 80% done and is almost ready for alpha. We also have another protocol that has not been mentioned until now. We believe that a voting protocol would be very useful for the community. It allows the team to propose a question to the community, and for the community to let their DPoPS delegate know what they want. Then the DPoPS delegates vote and the results are not artificially inflated since we carried out the vote on the xcash blockchain using the delegates and DPoPS infrastructure.

Those will be the next protocols, as both have coding done. We have not made a decision yet on which one, but of course we would love to hear the communities feedback on which one they think is more important at this stage.

Let us and Zach know on discord as this will be useful info.

If you have already not seen the demo of the instant send payments on xcash, you can watch that on Zach’s YouTube channel (Zachy Zone)

Wait what about a rebase?

A rebase (updating the xcash-core base Monero code from 13.0.4 to the latest) is always on the table with the modular design. Since most features will be built on top of DPOPS (which is created from scratch) it will be possible to rebase to another version of Monero at any time. As of now this is not in the immediate plans, but as time goes on and protocols get built, it will make sense at some point to rebase. We have not seen any features yet that makes us want to rebase, but future talked about features like StringCT (ability to set the RingCT count to greater than 1000 not less than 100) will be a big reason to rebase

Thank you everyone.

Project Update: Core and DPOPS 2021 into 2022 was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.

Read the original article