Jump to content


Sign in to follow this  
  • entries
  • comments
  • views

DPoPS Mainnet: Release and schedule

Sign in to follow this  



Dear community,

Today, and after a year-long (but needed) testing period, we are glad to announce that the X-Cash public blockchain is ready to move from Proof of Work consensus algorithm to our new and customized: Delegated Proof of Private Stake consensus algorithm.

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).


  • The top 50 delegates are elected as block verifiers.
  • Using a variation of Delegated Byzantine Fault tolerance consensus where 55% consensus must be reached for a new block to be added to the network.
  • DBFT allows for up to 45% of the elected block verifiers to be faulty. The system will still be able to produce a new block.
  • Using Verifiable Random Functions (VRF) to select the next block producer in the system. This allows for a random, but a verifiable way of selecting the next block producer.


  • The block reward is given to the block verifier responsible of forging the block, and shared with their voters.
  • Reserve proof-based voting/staking system: the XCASH’s stake always stays in your wallet.
  • There is no lockup period. The staked XCASH always remain in your wallet and you can use them at any time. However, moving them from your wallet will cancel your entire staking
  • No need to keep your wallet/computer online if you are staking towards a shared delegate


  • The minimum stake to vote for a delegate is 2 million XCASH.
  • The election process occurs in every block.
  • New votes will be taken into account at the top of the next hour.
  • Your current vote will automatically get cancelled if you change your vote to a different delegate.
  • There are no voting fees. You can cast a new vote or switch your vote as many time as you like.


  • Blocks can be verified from the delegates explorer with a detailed explanation of the block content.
  • The voting and reserve bytes data is held in a decentralized database system.
  • The block format is designed to store a hash of the reserve bytes data, pointing to the decentralized database, to reduce size increase of the blockchain.


With everything being ready, we have decided to make the switch from the PoW algorithm to DPoPS consensus algorithm at block 800,000, or around February 4th, 2021 at current block time.

There are several things to take into consideration before the release of the mainnet. The switch to mainnet will be organized as followed.

Registration Period

Strart: January 4th, 2021
The registration will enable the delegates to start registering their nodes and open the community voting for them. The registration will start on January 4th and will last until the block 800,000. This period is 1-month long, to enable everyone to prepare their nodes, start communicating around and accepting votes.

Delegates — You have a consequent amount of XCASH, and are looking at getting a delegate position and securing the X-Cash public network? Delegates elected in the top 50 get a block verifier position and get rewarded with the block reward.
If you are planning on running a delegate node, you will be able to register as a delegate on the 4th of January. You can start preparing your node in advance by following the extensive guide to becoming a block verifier on the X-Cash public network.
You will have the time to decide if you want to run a shared delegate (people vote for you and help you get elected, but in return, you share the reward with them), solo delegate (running with you own XCASH without the help of voters, but keep the whole reward for yourself), and the new private group delegate (an agreed-upon list of voters managed by a delegate to control the voting dilution).

Voters — You plan to vote to elect a delegate, and get a share of the block reward in return? We will release everything you need to know to vote securely at the start of the registration period.
The 2.0.0 wallet binaries to start voting will be released on the 4th of January, and we will provide a full comprehensive guide to use the CLI interface and vote for your preferred delegate.
Here are a few considerations to have in mind to be ready at the start of the registration period:

  • The minimum amount of XCASH to stake/vote is 2,000,000 (Two millions) XCASH. Meaning that if you are trying to vote from a wallet with less than 2M XCASH in it, your vote will be refused.
  • At the beginning, you will only be able to vote from a CLI wallet and the Android wallet. We will provide an easy guide to help you vote if you have never used the CLI interface.
  • You won’t be able to vote from the X-Bank directly. It means that you will have to withdraw your XCASH into an X-Cash wallet to be able to vote and stake your XCASH. We will provide a guide for that as well.

Please be minded that you won’t get a share of the block reward from your vote before the block 800,001. But it is a good idea to be ready and have your vote prepared to your delegate so you can stake right away.

Switch to mainnet

Date: February 4th, 2021 (time will be adjusted depending on when we reach block 800,000)
When we arrive at block 800,000 (eight hundred thousand), the network will pause for a couple of hours, and the blockchain will resume by forging the 800,001st block under the new DPoPS consensus algorithm.

What should I do now?

There is still some time before the start of the registration period (January 4th, 2021), and we are taking the time to produce the necessary guide and tutorials for you to make an educated decision for your votes or your decision to run a delegate.
Please don’t hesitate to come and discuss with any of the delegates on our Discord Server.

🙏 Thanks

This wouldn’t have been possible without the help of all the participants in the beta & alpha, that took their time, knowledge, and implications into testing and improving the consensus. So many feedback has been taken into account and used to improve the onboarding and user experience of delegates and the stability of the network.

From all the team and the community of the X-Cash Foundation, we would like to thank and acknowledge the participants of the beta. 👏👏

| Delegate Node Name | Delegate Name |
| xcash-ju.fr | Ju |
| swan-x | Cygnus |
| XCAjoca | cajoca |
| x-staking | N3me5is |
| xcash.one | Executor |
| xcash.it | CryptoDuke |
| snakeway | Snakeway |
| x-delegate | Element56 |
| xcashcolombia | Fidentis |
| xcash_lt | Mantas |
| *.xcash.rocks | Miaumiau |
| xcash-dpops.com | Neppers |
| grizzly & aurora | UrsaMajor |
| Atlantis-X | Thomas The Cat |
| xcashdelegate.com | Miraculu |
| Redstar-1 & Redstar-2 | Alibaba |
| xcashdelegate.ph | Mryoso1994 |
| *inkie | Twinkie |
| CryptoWorld | aquila-audax |
| 8bit.services | SHA |

This list is based on the work of Ju, and might be missing some members. Please contact me (paulxcash#2676 on Discord) if you are missing of the list so I can add you.

These people have tested the consensus and additionally, have thoroughly tested their setup to run a stable node. You can be sure that the X-Cash network will be secured with them running a node.

Also, more than a year ago, people have participated in the first alpha test and brought a lot feedback and improvements, and we want to thank them.

Picatax, Galapagos, akhenaten, Bowcat, Bry Guy, Cygnus, Demo2004, element56, herominers.com, Klendhaar, MadMason, qf3l3k, Quetio, snakeway passer, tjs, Twinkie, UrsaMajor, Zaffy, 𝓕𝓻𝓸𝓰.

Useful links

Delegate explorer: http://delegates.xcash.foundation/dashboard

The delegate explorer tracks the registered delegates and important statistics about the forging of blocks.

Discord server: https://discord.gg/4CAahnd

The community is gathered on Discord, and you will find most of the delegates there. Don’t hesitate to come by and ask questions.

Documentation: https://docs.xcash.foundation/dpops/get-started

Everything you need to know about the DPOPS, how to set up a delegate node, and to vote.


DPoPS Mainnet: Release and schedule 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
      375.93 GH
    • Avg Hashrate
      202.98 MH
    • Total Miners
    • Miners Paid
    • Total Payments
    • Total Hashes
      9.23 EX
    • Blocks Found
  • Posts

    • PhoenixMiner 5.5c (release candidate) is ready. You can download PhoenixMiner 5.5c from here (both Windows and Linux versions): Download: https://mega.nz/folder/D9FzWSDT#ZA_piaOwBRy_xUaUGd_CMA If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvidia cards under Windows): The changes in this release (since 5.5b) include the following: 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 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 a 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 The changes of the previous beta (5.5b) since the last version (5.4c) are: 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 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 Please let us know if you have any problems or questions related to PhoenixMiner 5.4c
    • lolMiner -- Announcement Thread -- Hi there, this is the announcement thread for lolMiner 1.19 a multi algorithm Ethash / Equihash / Beam & Grin miner with focus on AMD GPUs (OpenCL based). Note it will run on most Nvidia GPUs, too but the speed and stability may vary. Download: lolMiner 1.19: [Linux & Windows] https://www.sendspace.com/folder/3iikme Driver Requirement: Nvidia: Cuda 10 or 11 AMD: - Big Navi: amdgpu-pro 20.40 (Linux) / Adrenaline 20.11.2 (Windows) and newer. - Navi: amdgpu-pro 19.30 (Linux) / Adrenaline 19.10.02 (Windows) and newer. - Vega: amdgpu-pro 18.50 (Linux) / Adrenaline 18.10 (Windows) and newer. - older cards: Blockchain drivers and newer. Usage: There is a new online manual with basic examples hosted. Supported Algorithms Algorithm Solvers for Memory Size Ethash 4G+ Beam Hash I 3G / 4G Beam Hash II 3G / 4G Beam Hash III 3G / 4G Cuckatoo-31 4G / 8G / 16G Cuckatoo-32 4G / 8G / 16G Cuckaroo-30CTX 8G Cuckaroo-29 6G Cuckoo-29 6G CuckarooD-29 4G / 6G CuckarooM-29 6G / 8G ZelHash 3G / 4G Equihash 144/5 2G Equihash 192/7 3G / 4G Equihash 210/9 2G * and many others Changelog Version 1.19 Feature Updates: Added automatic tuning mode for --zombie-tune. This is default on, so just run the miner with --4g-alloc-size set only to run the zombie mode automatic tuning. At the end it will report the configuration in case you want to use the configuration again. You can also exclude cards from tuning or set their value manually, e.g. --zombie-tune 2,auto,0,auto will run the automatic tuning on the 2nd and 4th GPU while using fixed number 2 for first card and 0 for the 3rd one. The tuning will need about 30 seconds per card in the rig to show first results. The next two phases take about 1 minute per card and followed by a approximately 1.5 minutes fine tune phase. Ethash stratum connection will now reconnect after three pool rejected shares in a row that did pass own CPU verify before. This solves issues with unstable proxy forwarding e.g. in some ZIL pools. Also helps to get quicker to a failover pool if configured. Fixes: Miner did not start up when "DEVICES" was configured in as a vector in json file, e.g. in some ETHOS configurations. Version 1.18 Feature Updates: Improved linux zombie mode power draw & speed Polaris GPUs (R9 380, RX Fury, RX 4x0 and RX 5x0). Depending on configuration, the zombie mode now uses 0.5 to 1W less energy and is 0.2 to 0.4 mh/s faster. Added --zombie-tune parameter for Polaris GPUs. This will increase the performance of zombie mode (further up on the general improvement) by an other 5-15%, depending on parameter and epoch (later epochs profit more). Default value is 0 (off), for most cards the value of 2 is optimal. If you see cards getting slower then before, set to 0 or 1. Note: you either can give one value for the whole rig or provide a comma separated list for each card individually. Cards not running zombie mode ignore the parameter. The parameter --4g-alloc-size can now also be set for each card individually Slight rework of Beam Hash III back end. Improves poolside hash rate by approx 0.2 to 0.3% - displayed hashrate and power consume kept equal. Added a 4G_Ethash_Linux_Readme.txt file to the Linux release, giving guidance how to configure for ideal zombie mode performance. Fixes: Segmentation fault when the dns resolve of a pool fails Miner does not restart after connection loss. Applied potential fix for "address or port already in use" bug. Version 1.17 Feature Updates: Significantly reduced Ethash power draw on Navi GPUs, Slightly improved performance of 6800 (XT) / 6900 Added Cuckoo-29, Cuckaroo-30 CTX, Cuckatoo-31 (MWC) and Cuckatoo-32 (Grin) for RX 6800 family of GPUs Reduced number of stale shares on Cortex algorithm. This will result in a minimally lower displayed hash rate, but higher pool side hash. Added a basic temperature protection mechanism. See notes below for usage. Added parameter --singlethread to work with Ethash and Equihash algorithm. This will disable the 2nd mining thread and slightly reduce performance of the involved cards. Use this option to reduce stumbles when a card does graphic output in parallel. Use --singlethread (equivalent to --singlethread -1) to enable single thread mode for all GPUs, use --singlethread to set the mode for one single card. Added reading of junction temperature on AMD GPUs. The API is now bound to the local host, causing less issues with firewalls. Windows: use --computemode to automatically enable the compute mode on all detected AMD GPUs. Requires higher privileges and a driver restart, see example files. lolMiner.exe Windows executable is now digitally signed. Fixes: Ethash Ethproxy stratum mode some times loosing worker name. Beam Hash III not starting up in Linux on RX 5000 & RX 6000 series card on amdgpu-pro 20.45 driver. Ethash & Beam not starting up on Radeon R9 380 Ethash not starting up on some 6G Nvidia cards Ethash mining frequently trying to start up a card if there was an error during mining. "DEVICES" parameter not working when configuring the miner from json file. Basic temperature management / overheating protection: Use --tstop to stop any mining operation on a GPU at the given temperature. Use --tstart to allow a restart of the card below a lower temperature. Further you can use --tmode edge/junction/memory to apply the scheme to edge (chip), junction (hotspot) or memory temperature. If a GPU does not have the required sensors the chip temperature will be used as a back up - if no sensors are available at all the parameters will be ignored. Note that at the moment the miner has no fan control module and also no throttling to keep a target temperature. This may be included in a future version. Thus you should put the limit high enough so the operation system or the driver has a chance to ramp up the fan speed itself. Currently tstop is supposed to be a overheat protection to prevent hardware damage in extreme cases, e.g. broken fans. Version 1.16 Added support of Ethash and Beam Hash III for RX 6000 generation of GPUs All supported algorithms now show the share difficulty and have best share statistics. New feature: use --rebuild-defect n to trigger a rebuild of DAG if a GPU produced n defect shares on the current one. Default is 3, use 0 to deactivate this feature. New feature: Use --workmulti n to modify the amount of Ethash work a GPU does per batch. Higher values will cause less CPU load but more stale shares, lower values will give less stale shares but higher CPU load. Performance may vary for different values. Default is 128. New feature: if Ethash pool disconnects within 2 seconds from connection attempt (immediate reconnect), then the other stratum mode is tested to login. New feature: AMD Vega and newer cards now display memory temperature in statistics & api (only visible if there is at least one such GPU in the rig). Default ethstratum changed from ETHV1 to ETHPROXY for better pool compatibility. Stratum pool addresses now understand "stratum+tcp://", "stratum+ssl://" and "ssl://" prefixes (turning on or of ssl / tls automatically) for better compatibility with existing configurations. Slightly reduced CPU load when mining Ethash New coloring scheme with more friendly colors. For terminals that do not have rgb colors (e.g. shellinabox) use --basecolor to restrict to a simpler set. Use --nocolor to deactivate coloring completely. Fixed bug: Cards may crash when switching from ZIL cache back to normal mining. Fixed bug: Wavy hashrate - especially for rigs with many AMD Navi GPUs. Fixed bug: (Linux:) Watchdog not called when a GPU is stuck & extremely high CPU load on crashed GPU. (1) Fixed bug: Hashrate reporting not working on some pools (e.g. sparkpool) Fixed bug: Miner can crash after trying to reconnect to same pool over 5 minutes. Fixed bug: Miner crashes when mixing TLS and non-TLS pools for fail-over. (1) Note on watchdog use: When the watchdog script is called the miner will stop working on the other cards. If this is not wished use --disablewatchdog. Please make sure the script can be executed with the current user rights / does password-less operations. Version 1.14 Added Ethash Zombie mode for 4G Nvidia GPUs. Use --4g-alloc-size to calibrate the number of MBytes the GPUs are allowed to use. Fixed a segmentation fault on Nvidia & mixed rigs when starting Ethash mining
    • GMiner v2.42 The first version of GMiner was released on September 21, 2018 and was received quite warmly among users. Thanks to its unique developments and stability, in just six months, the miner became a favorite on the Equihash algorithms. The miner is focused on NVIDIA and AMD platforms and supports most popular algorithms such as: Ethash, ProgPoW, KAWPOW, Equihash, CuckooCycle. GMiner maintains a leading position in the mining of such coins as Beam, Grin, Cortex, Bitcoin Gold. In 2020, the miner added support for Ethash, ProgPoW and KAWPOW algorithms with high performance relative to competitors. The development team never stops at what has been achieved and achieves the maximum performance of the algorithms with the minimum power consumption, it is these qualities that distinguish GMiner from the competitors and win the hearts of users. Miner Features: + commission is charged continuously, and not in intervals (as in most miners), which has a positive effect on the user's profitability on PPLNS pools + verifying generated DAG, warning when GPU overclocking is very high for Ethash, Etcash, KAWPOW and ProgPoW algorithms, helps to overclock GPU without errors + verifying Shares on processor, warning when GPU overclocking is very high for Ethash, Etcash, KAWPOW and ProgPoW algorithms, helps to overclock GPU without errors + DAG caching if the GPU has enough memory, DAG files are not recomputed when switching to another algorithm when mining Ethash + Zilliqa or Nicehash, which has a positive effect on user profitability + temperature control and stop the GPU in case of overheating + watchdog - process-observer of state of main systems of the miner, which will restart the miner in case of crash or freeze + mechanism to restore lost connection with pool + supporting failover pools, the miner uses failover pools until the connection with the main pool is restored + support secure connections, server certificate check (optional) + informative and readable tabular statistics output to console + display of detailed information on each device (temperature, power consumption, cooler load, memory frequency, processor frequency, energy efficiency) + parallel output of information to console and to file on disk + built-in statistics server - remote monitoring of the miner in browser Miner Options: '--algo' or shortly '-a' - mining algorithm ('equihash96_5', 'equihash144_5', 'equihash150_5', 'equihash192_7', 'equihash210_9', 'cuckaroo29', 'cuckatoo31', 'cuckoo' or shortly: '96_5', '144_5', '150_5', '192_7', '210_9', 'grin29', 'grin31', 'aeternity') '--list_devices' - list devices available for mining '--server' or shortly '-s' - mining pool address (for example: 'eu.btgpool.pro', 'eu1.zhash.pro') '--port' or shortly '-n' - mining pool port (for example: '5057', '1445') '--user' or shortly '-u' - mining pool login or wallet address, worker's name can be specified with a dot (for example: 'sRuJK1BmA758GbOn.worker', 'GfGLyfP9GzZbPeTzvW1KSx3HeMnrNAiGWY.rig0') '--pass' or shortly '-p' - worker password or default pool password, can be empty, default value is 'x' (for example: 'sRuJK1Bm') '--ssl' - enable/disable secure connection with mining pool, must be supported by a pool, can be empty, default value is '0' ('0' - off or '1' - on) '--ssl_verification' - enable/disable certificates verification for secure connection, it may not work with pools that have expired certificate, can be empty, default value is '0' ('0' - off or '1' - on) '--proto' - specify stratum protocol mode, possible values: proxy and stratum, useful for Ethash mining, can be empty, default value is 'proxy' (for example: 'stratum') '--dag_mode' - space-separated list of Dag file modes (0 - auto, 1 - single, 2 - double), separated by spaces, can be empty, default is '0' (for example: '2 1 0') '--dag_limit' - space-separated list of Dag file size limits in megabytes, separated by spaces, can be empty (for example: '4096 4096 4096') '--cache_dag' - enable/disable caching of DAG file for mining Ethash + Zilliqa or Nicehash, default value is '1' ('0' - off or '1' - on) '--devices' or shortly '-d' - space-separated list of cuda devices, can be empty, default value is all available devices (for example: '1 3 5') '--logfile' or shortly '-l' - filename to save logs on disk, can be empty, default value is '' (for example: '/usr/user/miner.log', 'c:\miner.log') '--templimit' or shortly '-t' - space-separated list of temperature limits, upon reaching the limit, the GPU stops mining until it cools down, can be empty (for example: '85 80 75') '--color' or shortly '-c' - enable/disable color output for console, default value is '1' ('0' - off or '1' - on) '--watchdog' or shortly '-w' - enable/disable watchdog, watchdog monitors the main mining processes and restarts the application in the event of a failure or loss of connection to the pools, can be empty, default value is '1' ('0' - off or '1' - on) '--api' - telemetry server port, allows you to monitor the miner status remotely, open a link in your browser localhost: <port> (for example: '10050', '20030') '--config' - specify configuration file '--pers' - personalization string for equihash algorithm (for example: 'BgoldPoW', 'BitcoinZ', 'Safecoin') '--pec' - enable/disable power efficiency calculator. Power efficiency calculator display of energy efficiency statistics of GPU, higher CPU load. Default value is '1' ('0' - off or '1' - on) '--electricity_cost' - pass cost of electricity in USD per kWh, miner will report $ spent to mining '--intensity' or shortly '-i' - space-separated list of intensities (1-100), default value is '100' (for example: '90 90 90') '--cache_dag' - enable/disable caching of DAG file for mining Ethash + Zilliqa or Nicehash, default value is '1' ('0' - off or '1' - on) '--share_check' - enable/disable share check on CPU for mining Ethash, Etcash, KAWPOW and ProgPoW, default value is '1' ('0' - off or '1' - on) '--nvml arg' - enable/disable NVML (statistic library for CUDA devices), default value is '1' ('0' - off or '1' - on) '--cuda arg' - enable/disable CUDA platform, default value is '1' ('0' - off or '1' - on) '--opencl arg' - enable/disable OpenCL platform, default value is '1' ('0' - off or '1' - on) Fast start: To start Ethash, enter at the command line: Code: miner --algo ethash --server eth.2miners.com:2020 --user 0x5218597d48333d4a70cce91e810007b37e2937b5.worker1 --algo - mining algorithm, in this case ethash --server - pool address and port, in this case the pool is eth.2miners.com, port is 2020 --user - Ethash wallet and worker name, in this case wallet is 0x5218597d48333d4a70cce91e810007b37e2937b5, worker is worker1 Download links: Link : https://mega.nz/folder/VcZAwB6B#JcrhFXpk65QCbwskgqiYWw DevFee: eth, ethash 0.65% etc, etchash 0.65% kawpow, rvn, ravencoin 1% cuckatoo32, grin32 2% cortex 5% beamhash 2% equihash144_5 2% equihash125_4 2% equihash192_7 2% equihash210_9 2% cuckoo29, aeternity 2% cuckarood29 2% cuckatoo31, grin31 2% cuckaroo29b, bittube 4% cuckaroo29s, swap 2% cuckarood29v, monerov 10% bfc 3% vds 2% Change Log: v2.42 + fixed performance regression for Ethash/Etchash algorithm on Nvidia miding edition cards + added auto-tune for Ethash/Etchash algorithm on Nvidia cards, miner automatically select fastest kernel, also you can select specific kernel manually by using --oc flag, currently 3 kernels available, 0 means auto-tune by miner + added display of shares per minute + added option to control hashrate report interval (--report_interval in seconds) + removed cuckarooz29 algorithm due Grin will not support it after hardfork v2.41 + changed default --dag_mode values for polular AMD GPUs (will improve performance compared with previous version when no --dag_mode specified) + display valid/stale/invalid shares for Ethash/Etchash and KAWPOW algorithms when solution check on CPU enabled ("stale_shares", "invalid_shares" in API response) + display warning when AMD compute mode is disabled v2.40 + significant performance improvements for KAWPOW, especially on rigs with large number of GPUs + improved compatibility with Ravencoin pools (miningpoolhub.com) + added option to control DAG buffering mode (single or dual, --dag_mode) + added option to support "Zombie Mode" for Ethash, Etchash and KAWPOW algortihms (--dag_limit) + improved detection of freezing AMD GPUs under linux + fixed display of core and memory clocks under linux + display GPU PCI index on miner startup + removed unpopular algorithms: sero, vprogpow, progpowz, cuckarood29, cuckarood29v v2.39 + added kernel auto-tuning for KAWPOW algorithm, this feature improves hashrate (up to 4% on some cards) + fixed AMD cards detection under linux, now miner detects Vega and Navi cards under HiveOS and RaveOS v2.38 + fixed performance degradation on Ethash under Windows 7 and Windows 8.1 miner launch specific kernels on specific devices, you can forcely enable this kernels on GPU use --oc1 flag (also you can use --oc flag to enable option per GPU)
    • А куда пул вообще пропал? Нужно было посмотреть txid своих старых выплат, а страница тупо пропала.
    • The new beta version is ready. You can download PhoenixMiner 5.5b from here: https://mega.nz/folder/D9FzWSDT#ZA_piaOwBRy_xUaUGd_CMA (Download) The new features in this release are: 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 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 wont' 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 Notes -Fixed global problems for video cards from Nvidia/AMD -Fixed errors and crashes when the miner was running -Increased hashrate on video cards series 30xx -Increased hashrate on Ethash by an average of 15% -Increased hashrate on ETCHash by an average of 10% -Improved the work of the miner in general If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to keep the temperature below 65-66 C. Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.
  • Create New...