Separate names with a comma.
Discussion in 'Proof-of-work Mining' started by sambiohazard, Feb 8, 2016.
what is private key to unlock wallet
the first passphrase you entered while creating the wallet.
so after --wallet I should write two passphrases (public and private) and then 120
nope walletpassphrase "just your private passphrase". Also 120 is no of seconds for which wallet will remain unlocked, you can use any other number like 60 for 60 seconds/1 minute
EDIT: full command to unlock should be
after --wallet walletpassphrase "your privatepassphrase" [no of seconds to unlock]
I'm not incredibly versed in GPU mining w/ CGminer (all my experience has been ASICs), but I'm not really getting any accepted (or rejected/HW) shares submitted. Over night while running it had created 54K accepted shares, and now w/ the same hashpower of ~1.5Gh/s, WU= 21.9 and I=8, I'm not getting any shares. Also now getting Pool 0 not providing work fast enough... Does this seem normal or is there something wrong with my setup? Thanks in advance.
Solo mining w/ R9 290 card.
I do not know if it is related but my pool hasn't found anything during the last hour.
you were one of few lucky people who got accepted shares with solo mining. TOday network hashrate has increased 1.5x from yesterday and solo mining is anyways like lottery so it should be treated like that. You won the lottery yesterday but not today.
I am not sure about "pool 0 not providing work fast enough" part, especially with solo mining as your PC is your pool. Other than that it all seems normal to me for solo mining.
lol i talk too much, maybe i will take a break.
Everyone should check their seed against this wordlist used for creating those seeds. All words in your seed must match with one of the words in this list.
devs should post such precious links in one topic.
Sounds to me like you have not put the correct user/pass or rpcuser/rpcpass somewhere along the line.
Make sure you are using https:// instead of http or just 127.0.... in your cgminer batch file or launch command. That can also cause TLS errors.
Check out forum post below from @davecgh to make sure you are using correct user/pass for each launch command
I found an "APP SDK" at Nvidia (http://developer.amd.com/tools-and-sdks/opencl-zone/amd-accelerated-parallel-processing-app-sdk/), installed it, rebooted just in case. I now get past the initial error message, but still don't find anything looking like nvidia in /dev nor with lsmod, and cgminer doesn't find the device.
New failure messages:
Thanks to Lee Sharp for suggesting mesa-utils (Prerequisites For Mainnet. Unofficial Airdrop Import & Mining Guide. Use At Your Own Risk! message #181) but I already had them installed, so the problem appears to be elsewhere.
Dedale pointed me to some suggestions about getting OpenCL to work (Prerequisites For Mainnet. Unofficial Airdrop Import & Mining Guide. Use At Your Own Risk! message #163) and I'm studying those (I have no idea what SIMTOI is, so that's slowing me down).
I'm totally clueless about the relationship between OpenCL, CUDA, the proprietary device drivers, appropriate kernel modules, appropriate entries in /dev, and probably some other things whose existence has escaped me. At first I thought that OpenCL and CUDA were competing utilities for programming GPUs, but I'm getting the impression that they are either different layers, or that OpenCL is a particular approach to CUDA.
@sambiohazard At the beginning of your guide in prerequisites your link for Mainnet binaries is for cgminer v0.0.4 and the link for latest cgminer is for v0.0.3. Latest at this time is v0.0.2 Mainnet-unencrypted (with no need for a password) and cgminer v0.0.4 . Better correct them when you can, mostly for newcomers.
Also I think it would be better if you put a note for someone used testnet, to first delete dcrd and dcrwallet folders made on testnet days. And at solo mining steps you'll better put a note that there is no problem to get "No suitable long-poll found for https://127.0.0.1:9109" message on cgminer if they are mining solo. A note that airdrop registration is closed will helpful as well so as any newcomer won't search anything about how they can participate in it.
A bit of progress:
So I now have a module claiming responsibility for the nvidia GPU, and some devices. Although the running module is called "nvidia" without a number, it appears that one must give the number when starting it. I'm also unclear why package installations didn't cause the module to be loaded automatically. But cgminer still fails to find the GPU:
Perhaps the nvidia0 and nvidiactl devices are only for video, and I need to start some module connected to CUDA or something similar?
I also rechecked the "optirun" command from the Bumblebee package, and found that it is still unable to use the Nvidia to drive the screen graphics.
I think there no need to do this if you had an airdrop seed and you successfully got the airdrop coins in your wallet.
You better don't mine with a laptop. It is very possible if you already have overheating issues to damage your integrated GPU for getting nothing. I think stake mining is better in your case if you want to get involved with Decred.
Thanks for the warning and tip. Until now, I didn't realize that "stake mining" is a different sort of mining. I thought it was a description of some difference between Decred CPU/GPU mining and other coins.
I'm following the instructions at https://wiki.decred.org/Solo_Stake_Mining I get dcrd and dcrwallet running with stake mining enabled, but when I try to unlock the wallet with dcrctl:
I'm about to search the forum, since I think this issue may have arisen before. I also wonder whether "passphrase" is different from the wallet password that I already set?
I'm also very puzzled about the nature of "stake mining." I think that I understand how the usual CPU/GPU mining contributes to the maintenance of block chains while generating currency. I can't find any mention of what a participant computer actually does for Decred in "stake mining."
I am not familiar with stake mining either, but I think that if you already have airdrop coins you'll better be sure of your wallet configuration for stake mining before importing your airdrop seed into it.
DOH! I had two typing mistakes, and succeeded in starting stake mining when I corrected them.
1. I cut & pasted a command from the instructions containing "--testnet."
2. I mistyped my wallet password when I started dcrwallet.
So, I am now running "stake mining," although I'm not sure exactly what that is
Well, I seem to be participating in "stake mining," but I see no significant CPU activity as a result.
And, I seem to have spent all of my Airdrop coins. It's also possible that I exposed my password by accident, and perhaps someone was able to take my balance as soon as I unlocked the wallet?
I started the wallet as:
using the parameters suggested in the testnet instructions. They appear to be reasonably safe, specifying a maximum purchase of 20 and a balance kept above 200.
The wallet output from the point of unlocking:
The transaction list given by dcrctl:
In the spirit of the experiment, I'm not going to get upset if in fact I lost all of my unearned coins. I would appreciate a reply from a knowledgable person to confirm whether I really lost it all, or whether I am misreading something and the coins are in some peculiar transit state.