Jump to content


Sign in to follow this  
  • entries
  • comments
  • views

X-Cash project update: DPOPS, new website, and future plans.

Sign in to follow this  



Dear community,

today, we think that it’s necessary to take the time and take a step back to write about the latest development in the X-Cash ecosystem.

We would like to preface this article by addressing some concerns that arose from recent discussions within the community. Some members of the community have pointed out that it seems that most of X-Cash development is focused on DPOPS at the moment, and because it’s taking longer than planned it feels like the rest of the project is at a stop.

While this is true to some extent, we are moving forward in the background on several other projects that are not directly related to the state of the DPOPS development, albeit linked to its release. As you might know, we prefer not to make much noise about unfinished products.

With this in mind, we would like to write today about the progress that has been made to the DPOPS, talk about the new X-Cash website and what it means for the projects, and drop some hints about a project we have been thinking about since the birth of X-Cash.

DPOPS Beta update

At the time we are writing the article, the 10th beta run has just concluded, and we are preparing for the 11th with a series of updates and fine-tuning. Although those tests are taking a long time, we would like to point out that they are mandatory, as once we switch to main net there is no coming back. The DPOPS needs to be thoroughly tested, and with the unwavering help of our beta-testers, we are getting much quicker at pointing out issues.

1*N8Q-QK0hrXv5X_s6W-uD7g.pngNearly 1600 commits, 10 contributors, 30 closed issues and pull requests. The contributors help is getting more representative every day.

Since the start of the beta, there has been many software relaibility, quality of life, and compatibility improvments. The auto-installer has been revamped and made easier to use, the delegate explorer’s design has been drastically improved, LXC containers support have been fixed, and much more.

As Zach pointed out, we are in the lastest test runs before mainnet. Once the beta has been running for a satisfying amount of time, with a stable uptime for all beta delegates, we will start the transition to the mainnet.

The new X-Cash Website

The current X-Cash website hasn’t been updated for a while now, and it is mostly due to gathering most of the community activity on our Discord server. As the project is moving forward, we are well aware our current website is lacking updates and crucial elements to help newcomers and new investors into the project.

We have decided to reconstruct the website entirely, and bring some much needed features to help newcomers into the project.

Please be minded that every screenshot presented below is of a work in progress, and will change as we are closer to release.

The new website will have:

  • A “Get Started” guide for newcomers of the projects. This place will provide a step by step guide to get introduced to the project, and find all necessary information for new joiners.
  • A “Developer Hub” for contributors and people who want to build on X-Cash.
  • All the necessary link, list of exchanges, documentation, and a newly hosted blog directly on the website.
  • Instructions to become a delegate, how to vote and stake your XCASH, and a view into the delegates ecosystem.
  • Accessing every ways to securely store your XCASH.
  • The contributor program will be hosted on the website. We will list all open contribution’s projects directly on the website for contributors to come and check if they can participate and earn a reward.
1*Pg_5auuIzAf03O9K43DnBA.pngThe technical roadmap of X-Cash.

Updating the website is important. When the DPOPS mainnet rolls in, we want new joiners to gain as much information as possible on the website, and go further by joining the discussion on Discord with the already well active community.

The new website will be the showcase of the project, and while we believe that the current website is satisfactory, we can do much more to ease the integration of new people into the project.

We would like to release the website before the mainnet of the DPOPS, but there is still much to write and to design. Do not hesitate to post feedback or ideas in Discord!

Codename: Viaduc

We don’t want to announce anything before its at least in a prototype stage, but we still want to address what is brewing in the background. I will give some bullet points of information I can safely share at this stage:

  • This project is heavely tied to the X-Bank;
  • It will help with X-Cash’s interoperability with other protocols;
  • It was designed a long time ago to help X-Cash listing on exchanges, but the current timing has pushed it up in the list.

It is still too early to tell you more about it, but we are waiting impatiently to present you the Viaduc Project in a longer article. In the meantime, put on your tinfoil hats and speculate on what it could be. ?

Closing words

Since the beginning of the DPOPS beta, we have seen a lot of involvement from the community, and we couldn’t be more happy from the direction the project is taking. We have seen people trying to engage deep discussion on Discord, forwarding news on Twitter and trying to bring new people in by posting engaging comments, etc… Theses past few months, the number of contributors on the DPOPS repository has skyrocketed, and participants have brought valuable if not gamechanging updates to the software.

We recognize these contributors as an integral part of the project, and we will enforce ourselves to incentives more projects with the contributor program. As discussed with some of you already, we will also reward projects and contributions retrospectively to keep it fair for early helpers.

There are still a lot to come before the end of this year, so let’s build together ?

The X-Network Team & X-Cash Foundation.


X-Cash project update: DPOPS, new website, and future plans. was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.

View the full article

Sign in to follow this  


Recommended Comments

There are no comments to display.

Add a comment...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • HashVault Latest Blocks

  • HashVault Stats

    • Global Hashrate
      1.65 TH
    • Avg Hashrate
      657.13 MH
    • Total Miners
    • Miners Paid
    • Total Payments
    • Total Hashes
      9.23 EX
    • Blocks Found
  • Posts

    • IMPORTANT! Nvidia drivers for Windows 10 since ver. 460.79 (and newer) cause crash when PhoenixMiner starts. If you want to use these drivers, you need to upgrade to PhoenixMiner 5.4c or later version. IMPORTANT! Ethereum Classic (ETC) network switched to a modified version of ethash, called ETCHash. If you are mining ETC you must upgrade to PhoenixMiner 5.3b or later, otherwise you will get only rejected shares when mining ETC. IMPORTANT! All owners of AMD cards with 6 GB or 8 GB RAM must either keep drivers 20.4.x or lower (do not upgrade to 20.5.1 or later), or upgrade to PhoenixMiner 5.2e or later version to continue mining after DAG epoch 384 (ETH will pass it before the end of 2020). IMPORTANT! All owners of AMD cards with 4 GB RAM must upgrade to PhoenixMiner 5.2e or later version to continue mining after DAG epoch 373. Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.2e and later: Changes in version 5.5c (since 5.4c): Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows Added support for the latest AMD Windows driver 21.1.1 (still, we don't recommend using the 21.1.1 driver yet - we had some instability issues with it even when just idling on the desktop!) Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs won't work with these drivers! Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating Added new -mcdag parameter to reset the memory overclock on Nvidia cards during DAG generation. This may allow you to set higher memory overclock on your Nvidia cards without risking corrupt DAG buffer, which can lead to excessive number of incorrect shares. Use -mcdag 1 (by default the value is 0, which means turned off) to use this new feature. Under Linux -mcdag 1 will execute provided by the user shell script named daggen.sh (if present in the current directory) for each Nvidia GPU, passing the GPU index as the first argument, and PCIE bus ID as second argument. The miner will then wait for about 7 seconds before starting DAG generation to allow the script enough time to reset the memory overclock. The -tt parameter is now strictly for controlling the fan behavior. E.g. -tt 60 sets auto-fan speed with target temperature 60C; -tt -70 sets fixed fan speed 70%; and -tt 0 turns off the fan control. All these can be specified per GPU. There is a new -hwm parameter that allows controlling the frequency of the hardware monitoring, which was also done by -tt in the previous versions of PhoenixMiner Other small improvements and fixes PhoenixMiner is fast (arguably the fastest) Ethash (ETH, ETC, Muiscoin, EXP, UBQ, etc.) miner that supports both AMD and Nvidia cards (including in mixed mining rigs). It runs under Windows x64 and Linux x64 and has a developer fee of 0.65% (the lowest in the industry). This means that every 90 minutes the miner will mine for us, its developers, for 35 seconds. PhoenixMiner also supports ETCHash for mining ETC, Ubqhash for mining UBQ, ProgPOW for mining BCI, and dual mining Ethash/Ubqhash with Blake2s. The speed is generally faster than Claymore's Ethereum miner in eth only mode (we have measured about 0.4-1.3% speed improvement but your results may be slightly lower or higher depending on the GPUs). To achieve highest possible speed on AMD cards it may be needed to manually adjust the GPU tune factor (a number from 8 to about 400, which can be changed interactively with the + and - keys while the miner is running). If you have used Claymore's Dual Ethereum miner, you can switch to PhoenixMiner with minimal hassle as we support most of Claymore's command-line options and confirguration files. Screenshot: 1. Quick start You can download PhoenixMiner 5.5c from here: Download: https://www.sendspace.com/folder/ugy44z 2. Features, requirements, and limitations * Supports AMD RX5700, Radeon VII, Vega, 580/570/480/470, 460/560, Fury, 390/290 and older AMD GPUs with enough VRAM * Supports Nvidia 30x0, 20x0, 16x0, 10x0 and 9x0 series as well as older cards with enough VRAM * Highly optimized OpenCL and CUDA cores for maximum ethash mining speed * Optional "green" kernels for RX580/570/560/480/470/460 to lower the power consumption by 2-3% with small, or no drop in hashrate * Lowest developer fee of 0.65% (35 seconds defvee mining per each 90 minutes) * Dual mining ethash/Blake2s with lowest devfee of 0.9% (35 seconds defvee mining per each 65 minutes) * Advanced statistics: actual difficulty of each share, effective hashrate at the pool, and optional showing of estimated income in USD * DAG file generation in the GPU for faster start-up and DAG epoch switches * Supports all ethash mining pools and stratum protocols * Supports secure pool connections (e.g. ssl://eu1.ethermine.org:5555) to prevent IP hijacking attacks * Detailed statistics, including the individual cards hashrate, shares, temperature, fan speed, clocks, voltages, etc. * Unlimited number of fail-over pools in epools.txt configuration file (or two on the command line) * Automatic GPU tuning for the AMD GPUs to achieve maximum performance with your rig * Supports devfee on alternative ethash currencies like ETC, EXP, Music, UBQ, Pirl, Ellaism, Metaverse ETP, PGC, Akroma, WhaleCoin, Victorium, Nekonium, Mix, EtherGem, Aura, HBC, Genom, EtherZero, Callisto, DubaiCoin, MOAC, Ether-1, and EtherCC. This allows you to use older cards with small VRAM or low hashate on current DAG epochs (e.g. GTX970). * Full compatibility with the industry standard Claymore's Dual Ethereum miner, including most of command-line options, configuration files, and remote monitoring and management. * Supports the new Ubqhash algorithm for the UBQ coin. Please note that you must add -coin ubq to your command line (or COIN: ubq to your epools.txt file) in order to mine UBQ * Supports the ProgPOW algorithm for the Bitcoin Interest (BCI) coin mining. Please note that you must add -coin bci to your command line (or COIN: bci to your epools.txt file) in order to mine BCI * Supports the ProgPOW algorithm for mining BCI. * More features coming soon! PhoenixMiner requires Windows x64 (Windows 7, Windows 10, etc.), or Linux x64 (tested on Ubuntu LTS and Debian stable).
    • Hey guys. Can somebody help me? I wanted to have some fun and start mining Monero.  This is my config:    {     "autosave": true,     "donate-level": 2,     "cpu": true,     "opencl": true,     "cuda": true,     "pools": [         {             "url": "pool.hashvault.pro:3333"         },         {             "url": "pool.hashvault.pro:443",             "user": "-------------",             "keepalive": true,             "tls": true         }     ] }   I generated on website. Can you help me with user? What should I put there? A wallet address? (i have Coinomi wallet). Where to get it? Don't have any serious expectations about mining but i have a PC with two RTX 3060 so maybe i will dig something in free time just to be happy, even if it will be worth 1$ 🙂 Thank you in advance.
    • А куда пул вообще пропал? Нужно было посмотреть txid своих старых выплат, а страница тупо пропала.
    • Dear Community,   Reading the "Getting Started" section in the Pool area and some threads on the Forum, I still have a little question.  Whom do you recommend mining solo?  The hash rate seems to be the same whether I do SOLO mining or not.  Thanks! Bee *** My machine is a simple workstation with a slim linux running: * ABOUT XMRig/6.7.0 gcc/9.3.0 * LIBS libuv/1.38.1 OpenSSL/1.1.1i hwloc/2.2.0 * HUGE PAGES supported * 1GB PAGES unavailable * CPU Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHz (1) 64-bit AES L2:1.0 MB L3:8.0 MB 4C/8T NUMA:1 * MEMORY 1.1/15.6 GB (7%) * DONATE 1% * ASSEMBLY auto:intel * POOL #1 pool.hashvault.pro:3333 algo auto * COMMANDS hashrate, pause, resume, results, connection * OPENCL disabled * CUDA disabled  
    • Update: Having applied the Script from the thread linked to above, I get another outcome. Is that as it is supposed to be?? Thanks again Bee alpinehost:/home/alp# chown root /usr/share/hugepages.sh alpinehost:/home/alp# /usr/share/./hugepages.sh enable Huge pages enabled alpinehost:/home/alp# sysctl -a | grep hugep sysctl: error reading key 'net.ipv6.conf.all.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.default.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.eth0.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.lo.stable_secret': I/O error vm.nr_hugepages = 9 vm.nr_hugepages_mempolicy = 9 vm.nr_overcommit_hugepages = 0 alpinehost:/home/alp# The vm.nr_hugepages changed dramatically. What does it mean anyways?
  • Create New...