Separate names with a comma.
Discussion in 'PoW Pools' started by VanQ, Feb 10, 2016.
how do i get the unconfirmed DCR Balance to get confirmed?
it will confirm by itself in 280 block from last block you got reward for. That should be 1 to 1and a half day at current block rate.
I have been mining on the same Pool.mn also. Over a day and I show ~4.8 unconfirmed and 0.000 confirmed. Shouldn't some of that be confirmed?
BTW, @sambiohazard thank you for all your work on this forum. You sure have helped me quite a bit.
Takes a while with current network hash, I figure.
what was the first block you contributed to on the pool? If that block number + 280 is still not reached on mainnet then you have to wait. otherwise you can contact the pool operator. I personally have some confirmed DCR on that pool.
I have a request in to operator. Feel better knowing someone has confirmed there. Thanks again!
My full balance will be confirmed at block 910+. Also i asked same of suprnova op and he said these no of confirms & tx fee are hardcoded in the wallet so he cant do anything to change that.
Click on My Account and then Transactions to see all your block reward shares and how they go from unconfirmed to confirmed block by block.
Minor correction. It's 256 blocks.
That's PoS, but not PoW, right?
The 280 blocks is a pool policy anyway.
EDIT. I just checked suprnova. It's really 256 blocks to go confirmed.
CoinbaseMaturity is for PoW. TicketMaturity is for PoS. They are both 256 blocks though.
I think that is a bit too high considering 5 min block interval. Atmost it should be a few hours.
Well it's not really that different than Bitcoin. In Bitcoin, the coinbase maturity is 100 blocks and the target time is 10 minutes. So that is 1000 minutes ~= 16.67 hours. In Decred it's 256 * 5 = 1280 minutes ~= 21.33 hours.
The reason it's longer is because there isn't anywhere near the hash power securing the Decred network as there is the Bitcoin network and that was fully anticipated. The result is it's easier to create forks with less hash power and thus the coinbase maturity needs to be longer as well.
If you already know the reasoning for a coinbase maturity, feel free to ignore this part, but I figure I'll explain for those who might not know why it even exists.
Typically, when a block is orphaned, all of the transactions in the block are returned to the pool of transactions awaiting inclusion in a block and rebroadcast to the network for miners to pick them up. A coinbase, however, is special and can't simply be rebroadcast because it simply no longer exists. This means if you send somebody coins that spend from a coinbase and that coinbase gets orphaned, not only would the miner of the orphaned block lose out on the coins, but so would everybody else who received coins that spent from it. That could lead to a significant amount of fraud and loss of funds, so it's important for the coinbase maturity to be buried deep enough the chances of it being orphaned are virtually impossible.
I totally understand the reason now. I agree with one pool on 70% & only a few 1000 GPUs hashing this is necessary. If i am right, when a block orphans all later blocks are discarded too. Also can a block orphan after being confirmed multiple times?
Okay, now I am nervous. A day and a half and 0.00 of 8.577809 confirmed.
Oldest (pic): 13331 2016-02-09 14:38:05
Newest: 18646 2016-02-11 01:29:04
620 + 256 = 876
We are now at 868, hence unconfirmed yet for a few more blocks.
Forget the time. The blocks are the heartbeat of the network.
Edit: It's not over 300 blocks yet.
Ah, yes. I confused ID with blocks. I feel way better now. Thanks!
Only if there is a reorg that is sufficiently long. In order for that to happen, you need more hash power working on the other side of a fork than the hash power that is working on the current best chain.
Confirming now; takes a couple days, or so. I recommend dcr.POOL.mn for pool miners. It was the best of the listed pools IMHO.
BTW, 99.xx% efficiency for a couple days straight by using Intensity 14 setting.
Anyone remember how long it took for BTC to get to Decred's 2,000,000 MH/s? Go Decred!
hmm so it seems that even 50 or 100 confs will be enough as it highly unlikely to get a reorg that big. I still think 256 is overkill.