• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

A How-To..., with the -QT Wallet - PART THREE

M

MangledBlue

Guest
--------------------
3) -HOW TO SOLO-MINE
--------------------
Most people will tell you that Solo-Mining is point-less.
To a point, I agree.....
I think of it from time to time, how much of a lost art it really is.
Pushed to the side and never talked about really.
But if everybody would turn ON their -Qt Wallet to Solo-Mine,
our Network would maintain a minimal Hash-rate, constantly.

- Be sure that you have created the above <darkcoin.conf> file
----------------------------------
- OPEN your DarkCoin -Qt Wallet before mining
----------------------------------
-Qt Wallet will not start mining until you run a, Command-line
----------------------------------
- Transactions will appear in the Overview window.
-- When you find a Block Solo-Mining, it will appear as an incoming transaction.
-- You'll see a really cool Mining Icon (X)
-------------------------------------------

3.1) (CPU) (local) -Qt Wallet
----------------------------------
If you want the quick and easy answer to CPU Solo-Mining,
CLICK: Help
CLICK: Debug Window
CLICK: Console

Input the following command-line: setgenerate true -1

-And now your Solo-Mining-
-------------------------------

3.1.1) More details........
---------------------------------
To START mining: setgenerate true -1

To STOP mining: setgenerate false

Proof of/if mining: getgenerate
(TRUE = ON FALSE = OFF)

Shows a lot of mining info: getmininginfo
-----------------------------------------------

3.2) (GPU) (local) -Qt Wallet
----------------------------------
You'll need to alter your favorite mining software...
- Command-line and/or your GUI Miner to represent Solo-Mining

Instead of listing a Pool when GPU Mining,
-Replace the Pool with: localhost or 127.0.0.1 or 0.0.0.0
-Port: 9999
-Username:<match your .conf file rcpuser>
-PSW:<match your .conf file rcppassword>

--Then leave all other settings that work for you, as they are.

- YOU SHOULD BE SOLO-MIING WITH YOUR GPUs NOW -

NOTE: You can solo-mine with both CPU and GPU at the same time.
---------------------------------------------------------------

3.3) (CPU) and (GPU) (remote) -Qt Wallet
----------------------------------------
You'll need to alter your favorite mining software...
- Command-line and/or your GUI Miner to represent, Remote Solo-Mining

Instead of listing a Pool when Remote Mining,
-Replace the Pool with:<the IP address of your remote DRK -QT Wallet> <what.ever.yours.is> 192.168.0.127 10.0.0.127
-Port: 9999
-Username:<match your .conf file rcpuser>
-PSW:<match your .conf file rcppassword>

--Then leave all other settings that work for you, as they are.

- YOU SHOULD BE REMOTE SOLO-MIING WITH YOUR CPU and/or GPUs NOW -

NOTE: To find the IP address of a local machine:
- OPEN/RUN: CMD.exe
- At the command promt TYPE: <ipconfig /all>
- You will find you local machine IP here.
-------------------------------------------

----------------------
3.4) CONTROLLING THE CPU
----------------------

3.4.1) CPU Afinity 1.0
-----------------------
Type this Command-Line to Mine all CPU cores: setgenerate true -1

If you want to use a specific number of CPU cores,
Or, if you experience lag - use this Command-Line or a variance....
instead of -1, remove the (-) symbol and type number of core(s): setgenerate true 4
(if you have an 8 core CPU, this will generally use 0-3, or 50% of CPU cores)

NOTE: Helps for lag issues
-------------------------------------------------------------------------------

3.4.2) CPU Afinity 2.0
-----------------------
You can also use the Task-Manager to set CPU Afinity
OPEN: Task-Manager
CLICK: Processes (tab)
LOCATE: darkcoin-qt.exe*32
RIGHT-CLICK: darkcoin-qt.exe*32
- Small Menu pops up.
CLICK: Set Afinity
CLICK: Check-mark the CPU core(s) you wish to use
CLICK: OK

DarkCoin -Qt Wallet will only use the CPU core(s) you have assigned
-------------------------------------------------------------------

3.4.3) CPU Afinity 3.0
--------------------
With CPU Afinity, you use a combination of both forms.

100%
Console Command-Line to use all CPU cores: setgenerate true -1
Leave the Task-Manager as it is.

50% with 6 CPU cores
Console Command-Line to use (3) CPU cores: setgenerate true 3
Leave the Task-Manager as it is, or
OPEN: Task-Manager and assign (3) of the (6) cores to be used by -Qt Wallet.

I'm sure you can be very creative with CPU Afinity 3.0
------------------------------------------------------

3.4.4) CPU - SET PRIORITY
-----------------------
When setting the Priority of the CPU,
-Remember to set all -Qt Wallets the same or,
--The -Qt Wallet with the highest priority will dominate the CPU usage.
-Only set CPU Priority: LOW to HIGH - never use realtime

OPEN: Task-Manager
CLICK: Processes (tab)
LOCATE: darkcoin-qt.exe*32
RIGHT-CLICK: darkcoin-qt.exe*32
- Small Menu pops up.
CLICK: Set Priority
-Remember to set all -Qt Wallets the same: LOW to HIGH - never use realtime
--The -Qt Wallet with the highest priority will dominate the CPU usage.

NOTE: CPU Priority can also assist with lag issues


--------------------------------------------------
BEWARE - Do not forget your Encryption PSW

BEWARE - Do not delete your wallet.dat file

***AND BACK-UP wallet.dat FILE OFTEN***
---------------------------------------------------
If this has helped you in any way...
...donations accepted but not required.
-------------------------------------------------------
STEP OUT OF THE LITE AND INTO THE DRK
-------------------------------------------------------

https://dashtalk.org/search/233808/...ate&c[title_only]=1&c[node]=3&c[user][0]=1612
all 3 - click above
[all need to be updated]
 
Last edited:
MangledBlue said:
--------------------
3) -HOW TO SOLO-MINE
--------------------
Most people will tell you that Solo-Mining is point-less.
To a point, I agree.....
I think of it from time to time, how much of a lost art it really is.
Pushed to the side and never talked about really.
But if everybody would turn ON their -Qt Wallet to Solo-Mine,
our Network would maintain a minimal Hash-rate, constantly.

- Be sure that you have created the above <darkcoin.conf> file
----------------------------------
- OPEN your DarkCoin -Qt Wallet before mining
----------------------------------
-Qt Wallet will not start mining until you run a, Command-line
----------------------------------
- Transactions will appear in the Overview window.
-- When you find a Block Solo-Mining, it will appear as an incoming transaction.
-- You'll see a really cool Mining Icon (X)
-------------------------------------------

3.1) (CPU) (local) -Qt Wallet
----------------------------------
If you want the quick and easy answer to CPU Solo-Mining,
CLICK: Help
CLICK: Debug Window
CLICK: Console

Input the following command-line: setgenerate true -1

-And now your Solo-Mining-
-------------------------------

3.1.1) More details........
---------------------------------
To START mining: setgenerate true -1

To STOP mining: setgenerate false

Proof of/if mining: getgenerate
(TRUE = ON FALSE = OFF)

Shows a lot of mining info: getmininginfo
-----------------------------------------------

3.2) (GPU) (local) -Qt Wallet
----------------------------------
You'll need to alter your favorite mining software...
- Command-line and/or your GUI Miner to represent Solo-Mining

Instead of listing a Pool when GPU Mining,
-Replace the Pool with: localhost or 127.0.0.1 or 0.0.0.0
-Port: 9999
-Username:<match your .conf file rcpuser>
-PSW:<match your .conf file rcppassword>

--Then leave all other settings that work for you, as they are.

- YOU SHOULD BE SOLO-MIING WITH YOUR GPUs NOW -

NOTE: You can solo-mine with both CPU and GPU at the same time.
---------------------------------------------------------------

3.3) (CPU) and (GPU) (remote) -Qt Wallet
----------------------------------------
You'll need to alter your favorite mining software...
- Command-line and/or your GUI Miner to represent, Remote Solo-Mining

Instead of listing a Pool when Remote Mining,
-Replace the Pool with:<the IP address of your remote DRK -QT Wallet> <what.ever.yours.is> 192.168.0.127 10.0.0.127
-Port: 9999
-Username:<match your .conf file rcpuser>
-PSW:<match your .conf file rcppassword>

--Then leave all other settings that work for you, as they are.

- YOU SHOULD BE REMOTE SOLO-MIING WITH YOUR CPU and/or GPUs NOW -

NOTE: To find the IP address of a local machine:
- OPEN/RUN: CMD.exe
- At the command promt TYPE: <ipconfig /all>
- You will find you local machine IP here.
-------------------------------------------

----------------------
3.4) CONTROLLING THE CPU
----------------------

3.4.1) CPU Afinity 1.0
-----------------------
Type this Command-Line to Mine all CPU cores: setgenerate true -1

If you want to use a specific number of CPU cores,
Or, if you experience lag - use this Command-Line or a variance....
instead of -1, remove the (-) symbol and type number of core(s): setgenerate true 4
(if you have an 8 core CPU, this will generally use 0-3, or 50% of CPU cores)

NOTE: Helps for lag issues
-------------------------------------------------------------------------------

3.4.2) CPU Afinity 2.0
-----------------------
You can also use the Task-Manager to set CPU Afinity
OPEN: Task-Manager
CLICK: Processes (tab)
LOCATE: darkcoin-qt.exe*32
RIGHT-CLICK: darkcoin-qt.exe*32
- Small Menu pops up.
CLICK: Set Afinity
CLICK: Check-mark the CPU core(s) you wish to use
CLICK: OK

DarkCoin -Qt Wallet will only use the CPU core(s) you have assigned
-------------------------------------------------------------------

3.4.3) CPU Afinity 3.0
--------------------
With CPU Afinity, you use a combination of both forms.

100%
Console Command-Line to use all CPU cores: setgenerate true -1
Leave the Task-Manager as it is.

50% with 6 CPU cores
Console Command-Line to use (3) CPU cores: setgenerate true 3
Leave the Task-Manager as it is, or
OPEN: Task-Manager and assign (3) of the (6) cores to be used by -Qt Wallet.

I'm sure you can be very creative with CPU Afinity 3.0
------------------------------------------------------

3.4.4) CPU - SET PRIORITY
-----------------------
When setting the Priority of the CPU,
-Remember to set all -Qt Wallets the same or,
--The -Qt Wallet with the highest priority will dominate the CPU usage.
-Only set CPU Priority: LOW to HIGH - never use realtime

OPEN: Task-Manager
CLICK: Processes (tab)
LOCATE: darkcoin-qt.exe*32
RIGHT-CLICK: darkcoin-qt.exe*32
- Small Menu pops up.
CLICK: Set Priority
-Remember to set all -Qt Wallets the same: LOW to HIGH - never use realtime
--The -Qt Wallet with the highest priority will dominate the CPU usage.

NOTE: CPU Priority can also assist with lag issues


--------------------------------------------------
BEWARE - Do not forget your Encryption PSW

BEWARE - Do not delete your wallet.dat file

***AND BACK-UP wallet.dat FILE OFTEN***
---------------------------------------------------
If this has helped you in any way...
...donations accepted but not required.
XwSfYNDFwjkYPmWtiW14oWbiS3GF8ssD19
-------------------------------------------------------
STEP OUT OF THE LITE AND INTO THE DRK
-------------------------------------------------------
Click to expand...
Very cool... How come you never showed this thread to anyone? Nobody else has ever seen this! :p
 
I know right? I really believe we should get this put into the GUI at some point. If you've got the CPU for it, why not use it?
 
you should post that under "Guides"!
I had no idea this worked !
 
Nice guide, I was solo mining throughout june 2014 and earned about 20 DRK. It was tough though when net hash rate is over 100 gig you need patience.... For weeks i had nothing....
 
Thx for the feedback :)
Means a lot.

Anybody want to help me finish my Dummies Guide to MasterNodes? :-D
 
I just get RPC call failed and it never connects with the same settings, I even tried setting up a differn't port in the config and minner... same thing
 
Since v12 wallet merged updated with bitcoin core, rpc/getwork is not available on wallet anymore. For solo miner, please use mining application which support rpc/getblocktemplate or create own mining pool or p2pool for support rpc/getwork to mining application.
 
Yes - I should up date this - sorry
nobody realty knew about it for a long time....

Might give me some thing to do one day soon :-D
 
Gnah... Have been hacking in my shell for like 4 days now to get solo mining working. Just to find out it does not work at all. *hahaha*
Will have a look at p2pool. :)
 
frederik said:
Gnah... Have been hacking in my shell for like 4 days now to get solo mining working. Just to find out it does not work at all. *hahaha*
Will have a look at p2pool. :)
Click to expand...

actually it does work


dash-cli setgenerate true -1
[all cpu cores]

dash-cli setgenerate true 1
[1 cpu core]

dash-cli getmininginfo
[to get mining status]

dash-cli setgenerate false
[stop mining]

OR - use the CMD-line, in the wallet, by dropping the <dash-cli>
 
My i5 just generates at like 178khash/s.
I would like to use my nvidia gtx970. But ccminer can't connect to the local server.
 
Dash Core version v0.12.0.55-c30a0aa (64-bit) on Xubuntu 15.04

dash.conf
server=1
rpcuser=frederik
rpcpassword=randompa55
rpcallow=localhost as ip (sneaky url)
rpcport=9998

Curling localhost on that port tells me:
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}


ccminer jells
[2015-10-20 16:37:17] Hypertext Transfer Protocol (sneaky URL) request failed: The requested URL returned error: 401
[2015-10-20 16:37:17] json_rpc_call failed, retry after 30 seconds
 
frederik said:
Dash Core version v0.12.0.55-c30a0aa (64-bit) on Xubuntu 15.04

dash.conf
server=1
rpcuser=frederik
rpcpassword=randompa55
rpcallow=localhost as ip (sneaky url)
rpcport=9998

Curling localhost on that port tells me:
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}


ccminer jells
[2015-10-20 16:37:17] Hypertext Transfer Protocol (sneaky URL) request failed: The requested URL returned error: 401
[2015-10-20 16:37:17] json_rpc_call failed, retry after 30 seconds
Click to expand...

1. check your curl command
2. 401 means "unauthorized" - check username/password
 
You must log in or register to reply here.
Back
Top