dcrd gives your miner work to do. Your miner proves it has done the work by submitting the shares he found. IF you are lucky enough sometime a share will solve with the required difficulty and also a block will be found. If you find a block solo mining it will say Block Found (not share)
Sorry I just copy/paste it and forget to remove --testnet. I just wanted to help. The correct is: dcrctl -u username -P password --wallet listtransactions I also fixed it and on the post before.
mainnet is probably running nicely. its just that there was such huge interest in mining & due to lots of people able to mine from start small miners like us didn't get any blocks. This only means that launch was a success with 2+ PH/s of mining power on the net from very first blocks.
Let's hope so. I should be happy with airdrop coins then if Decred is only for big shark miners from day 0.
Ok, so in theory, what if over half of all the miners are using the same pool right now, then chances of solo miners finding a block is zero? how does that work like bitcoin with that 51% rule?
Yes it was the exact same thing on testnet. The miner would show shares found AND sometime Block found. Although it was a lot easier to find blocks on testnet. In fact at the moment it's about 36 times harder to find blocks on mainnet than it was on testnet But if you use a pool you don't have to be big to find block you just combine your work with others and get your share. For example if you have ~ 1GH/s on the network since launch using a pool, you could have raised a pool reward of 1 DCR already.
2PH/s amounts to roughly 1 million high-end GPUs, which I question equates to the number of miners. More likely a giant farm.
The chance of a miner finding a block is exactly the same whether he is in a pool or not. The pool is only a method to mitigate luck and share a small reward frequently (when the pool find a block) rather than keeping a big reward for yourself on really rare occasions. The 51% problems doesn't affect Decred, because when a block is found by miners it must also go through a second "type" of confirmation based on luck. so Stake miners (those who purchased tickets) are choosen at random and can vote on the block. So even if someone has 70% of the mining power he can still see his block voted down because of random votes.
In testnet everything worked fine but in mainnet I see block found but it's not accepted or rejected What can be wrong here ?
Two things. Found blocks for pool 0 means it found block for local diff on your machine but not good enough for mainnet diff. This might be because of a bug in cgminer 0.0.3 which shows wrong diff. This is now fixed in latest release 0.0.4. Try it i havent seen any block found message since i switched to latest release. Although i am just speculating here. https://github.com/decred/cgminer/releases/tag/v0.0.4 EDIT: and other things is that testnet coins were worthless so there was no competition for it. These mainnet coins could be worth lots of dollars potentially so more people & even big farms are interested and thus more competition. Best way for small miner in such situation is to either use a pool or just miner other coins & buy decred on exchange.
So, who exactly makes these cgminer releases? How do you know they are actually good/working? I've also switched to 0.0.4 So do you think the 0.0.3 version was telling you that you have found a share or block while in fact the real network difficulty was higher thus being rejected or ignored? I haven't seen any message regarding share found for pool 0 since switching
people were getting nervous not getting there coins while mining so even display bugs can cause anxiety. its probably a good idea to update
cgminer maxing out the CPU, no matter if one or four instances Everything default, no custom parameters.
For anyone reading this thread, there's some info in the What Are You Doing With Your Airdrop Coins? thread about how to check on the airdrop transaction. I expect, @sambiohazard, you know this already but here's a link for others.
Yeah it uses a lot of CPU resources, at least on Windows, for example on FX-8350 it uses 28% of all 8 cores and it always keeps busy (about 85%) 1 core (at least it pass this ~85% load from core to core, every second so it doesn't cause any other issues). Someone with FX-8370 said it has about the same utilization. If you are on Windows you can check if it faulty started on multiple instances. Quit from it and check if any of it's instances maybe still running at task manager, if so end it from there and start it again.