Jump to content

X-Cash

Sign in to follow this  
  • entries
    36
  • comments
    0
  • views
    5639

DPOPS Beta Update — Phase 2

Sign in to follow this  
Snider

109 views

DPOPS Beta Update — Phase 2

0*_HA4CEgawC9It7Pk.png

Dear Community,

It is with great excitement that we are sharing with you this update about the DPOPS Beta progress.

During the last year, we have developed an innovative consensus protocol called Delegated-Proof-of-Private-Stake. This protocol is the first DPOS that allows the use of private stakes for staking. While we coded most of the features from scratch, we have chosen to rely on Monero’s core technology for the obfuscation of the transactions.

In this article, we are providing you with an update on what has been developed and fixed since the start of the Beta. We would also like to give a huge thanks to all the contributors who assisted us since the alpha to identify these bugs and also providing their feedback to improve DPOPS.

Bugs fixing

Below is the exhaustive lists of the bugs identified and solved in the last weeks.

Incorrect block producer picking up [DPOPS]

This issue caused some delegates to pay for blocks they did not create.

Wrong block producer in block [DPOPS]

The wrong block producer was stored in the created block.

Double pay replay round [DPOPS]

Shared delegates were paying double or more for replayed rounds.

Security issue VRF key generation [DPOPS]

VRF keys were generated using a non-CSPRNG generator, making them weaker.

Majority check for syncing not working [DPOPS]

Fixed the majority check which verifies the integrity of a DB synced from a delegate.

Server stability [DPOPS]

Various fixes to make server and messaging more stable and less prone to drops.

Empty DB sync error [DPOPS]

Syncing would get stuck if the DB to sync was empty.

False positives reserve proofs [DPOPS]

Some edge cases were causing false positives for reserve proofs.

Syncing issue [Core]

One should be able to sync even if 34%+ of delegates are offline, fall back is 80% of seed nodes need to be online to sync.

Sometimes vote fails but is added [Core]

Checking was too strict with a 100% seed nodes threshold + 67% of delegates. Now adjusted to 80% seed nodes + 67% of delegates.

Reorganization issues [Core]

Reorganizations were triggered while not allowed under DPOPS rules.

Changing from solo to shared setups [Autoinstaller]

Switching between setup was not working after the installation.

Blockchain bootstrapping [Autoinstaller]

Blockchain was not being bootstrapped during installation.

Spelling errors [Autoinstaller]

Various wording and spelling adjustments.

Showing wrong info sometimes [Delegates website]

Some wrong information was displayed in several delegates metrics/stats

Logo not showing [Delegates & Shared Delegates websites]

Fixed logo not being displayed

No-blocks produced error [Shared delegates website]

An error as displayed before producing the first block

Non-functional API error [Shared delegates website]

Don’t allow for lookup based on the hash of a block.

Features & Optimisations

We also added a few notable features thanks to your feedbacks !

Get online status [DPOPS]

Delegates are now sorted by online/offline status and followed by vote count. This way, only the top 50 online delegates are displayed.

Miscellaneous optimizations [DPOPS]

Various CPU optimizations.

Seed nodes backup DB [DPOPS]

Seed nodes now save a second physical backup of decentralized DB for extra security.

Seed nodes don’t produce blocks anymore [DPOPS]

Only elected delegates will now be eligible to become block producers.

Stricter block verification rules [Core]

Stricter rules for delegates to add blocks to the blockchain, and faster syncing for all users.

Average delegate estimate vote count [Delegates website]

Added an average estimate indicator for becoming a delegate (total votes / 45).

Show blocks produced [Delegates website]

Blocks produced are now displayed on the front page

What’s next

It is with great excitement that we are now moving to the next step of the tests: Beta v2. This version includes all the fixes and features described above and should be the last before the main net release.

On Saturday 29th August, at 6 pm Paris time, we will start the second phase of DPOPS Beta, all delegates should update both their version and their VRF keys.

To update your keys please refer to the documentation here.

On behalf of the team, the contributors, and all the network participants, I would like to thank once again our great community for their support in creating the first delegated Proof-of-Private-Stake consensus. With beta v2 we are one step closer to bringing our innovation to the ecosystem and continuing to make X-Cash a successful project.

Finally, as the project is progressing significantly, we are preparing a special announcement for next week that will strengthen once again our commitment to the X-Cash project.

stat?event=post.clientViewed&referrerSource=full_rss&postId=cc5bce8293e7

DPOPS Beta Update — Phase 2 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  


0 Comments


Recommended Comments

There are no comments to display.

Guest
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
      2.34 TH
    • Avg Hashrate
      874.29 MH
    • Total Miners
      2682
    • Miners Paid
      44744
    • Total Payments
      1560135
    • Total Hashes
      9.23 EX
    • Blocks Found
      1840415
  • Posts

    • 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?
    • Dear Community,    I would like to have these Hugepages supported now :-) I am thus referring to this thread here, which seems to be closed. I have tried the following to enable hugepages AND get them working until 1 GB.  See me output: Thanks so far! Bee *** Question: Why is HUGEpages 1 GIg not available?  How do I set the value correct? My output: 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 = 2349 vm.nr_hugepages_mempolicy = 2349 vm.nr_overcommit_hugepages = 0 *** and in xmrig *** 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 3.2/15.6 GB (21%) * DONATE 1% * ASSEMBLY auto:intel * POOL #1 pool.hashvault.pro:3333 algo auto * COMMANDS hashrate, pause, resume, results, connection * OPENCL disabled * CUDA disabled  
×
×
  • Create New...