Skip to content

Releases: De-Crypted/dcrptd-miner

2.3.0

09 Sep 18:50
680b2ca
Compare
Choose a tag to compare
  • Added linux-arm64 build
  • pufferfish2bmb fee reduced to 1%

2.2.1

20 Aug 20:01
Compare
Choose a tag to compare

Stratum

  • Fix null errors after client has disconnected multiple times in row
  • Check if client received empty json

Stats API

  • Added accepted shares

2.2.0

18 Aug 19:19
Compare
Choose a tag to compare
  • Added stratum support
  • Small improvement to pufferfish2 hash rate

2.1.0

10 Jul 17:51
Compare
Choose a tag to compare

Changes

  • pufferfish2bmb algo hash rate improved up to 20%
  • Added benchmark feature. Run benchmark with --benchmark pufferfish2bmb
  • Added more stats to periodic report
  • Bugfix: Use proper shutdown (Ctrl -C) process instead of killing the process. Fixes issue where console might become unresponsive to user input after closing miner.

Benchmarking feature contains experimental Power Usage logging which required admin / sudo access to work. You may run benchmark without admin / sudo access but power usage will not be displayed.

2.0.2

01 Jul 18:18
Compare
Choose a tag to compare

Changes

  • ~5-8% improvement to Pufferfish2 hashrate
  • Added version information to miner startup and console title
  • Do not incorrectly display SUCCESS message as error

2.0.1

29 Jun 17:26
Compare
Choose a tag to compare

Fixes and Features

  • Added pufferfish2bmb algo support for osx-arm64 (consider this experimental for now)
  • Added block id information to 'New Job' output
  • Fixed block generator for BambooConnectionProvider to properly include transactions
  • Better connection handling when retry count has been exhausted and new connection provider is initialized
  • Connected / Disconnected messages are hidden when entering and leaving dev fee with ShifuPoolConnectionProvider
  • Better error reporting with regular logging if connection fails with ERR_CONNECTION_FAILED error

Known issues

  • osx-x64 version has been deprecated as the pufferfish2 library is not built correctly. If you wish to contribute by compiling shared library on your machine please let me know!

2.0

15 Jun 09:26
Compare
Choose a tag to compare
2.0

OLD CONFIGURATION FILE IS DEPRECATED recreate your configs

Supports multiple algorithms

  • Added support for algorithms sha256bmb and pufferfish2bmb
  • Algorithm change from sha256bmb to pufferfish2bmb will be done automatically.
  • Configuration file split to algorithm specific configs
    -- config.json = generic settings
    -- config.sha256bmb.json = sh256bmb algo specific settings
    -- config.pufferfish2.json = pufferfish2bmb algo specific settings
    -- Algorithm specific settings from command line need to be prefixed by algorith name, for example --sha256bmb:cpu:enabled false

OLD CONFIGURATION FILE IS DEPRECATED recreate your configs

Bug fixes

  • Fixed potential deadlock issue with BambooNodeConnection provider
  • Fixed issue where previous connection state was not properly reset after disconnecting and reconnecting

Dev fee change

  • Dev fee is now algorithm specific
    -- sha256bmb 1% fee
    -- pufferfish2bmb 1.5% fee

1.1.1

20 Apr 18:36
Compare
Choose a tag to compare

New Features

  • Added worker name support for Shifupool. Set it along with wallet address wallet_address.worker_name
  • Added hotkeys for pause and resume (and help)
    P - Pause
    R - Resume
    S - Periodic report stats
    H - Help

Bug Fixes

  • Handle random timeouts occurring to Shifupool better, do not crash.

1.1.0

14 Apr 18:20
Compare
Choose a tag to compare

New features

Improved connection management

You may now specify one or more urls. Miner will connect them in the order specified. If connection to pool is lost and not restored after retries done miner will connect to next url in list. You may also mix different connection protocols.

config.json example
"url": [ "bamboo://192.168.1.10:3000", "bamboo://192.168.1.11:3000", "shifu://185.215.180.7:5555" ]

commandline example
dcrptd-miner --url:0 bamboo://192.168.1.10:3000 --url:1 bamboo://192.168.1.11:3000 --url:2 shifu://185.215.180.7:5555

You may also configure retry count against each url and action taken after all urls have been looped through. Possible actions to take are RETRY (= restart from first url) and SHUTDOWN (= shutdown miner).

config.json example
"retries": 5, "action_after_retries_done": "SHUTDOWN"

commandline example
--retries 5 --action_after_retries_done SHUTDOWN

Configurable periodic report

You may now configure initial delay before first periodic report is done and also interval for subsequent reports

Keyboard actions

Support for keyboard actions have been implemented with one available action. You may now hit "s" key on your keyboard and miner will output periodic report.

Bug fixes

  • Log and report dropped shares.
  • Do not require ipv6 support. Prefer ipv6 over ipv4 if available.
  • Make console output atomic, no more "New job" in middle of periodic report.

It's a release!

05 Apr 18:08
Compare
Choose a tag to compare

BREAKING CHANGES - Do not use old config.json! Due to changes to GPU autodetection work_multiplier should be null and work_size should be 512 (you may explore different values if you want to try to optimize).

New Features

Multi-GPU Mining

By default miner will mine with first GPU it finds but you may specify one or more in config.json or commandline. When miner starts it will list all available GPU devices with their index numbers such as [0], [1], [2] etc.

If you want to run miner on GPUs 0 and 2 you may set in config.json
"device": "0,2"

Or on commandline
--gpu:device=0,2

Bamboo solo mining (dev fee 2%)

Miner now supports connection against bamboo node. First you need node address to connect against . Find one from http://ec2-34-218-176-84.us-west-2.compute.amazonaws.com/ or run your own. Change http: prefix to bamboo: and miner will know which connection profile to apply.

config.json
"url": "bamboo://127.0.0.3000"

commandline
--url=bamboo://127.0.0.1:3000

Other fixes

  • AMD support should be much better than before and manual configuration should not be needed.
  • Lower CPU usage on NVIDIA GPUs
  • Multiple fixes to status reporting, connection issues, GPU autodetection.