So any word on what the problem was? was it a bug that will effect bitcoin as well in a few years? or was it a change made after the fork from bitcoin?
No, it was a bug of my own doing. I believe it is patched, and I'm testing it on an isolated blockchain. I believe everything is ok, But i want to mine more blocks on my testnet before I release the software.
Sorry to bump this from last month, but I have not kept up with the latest events.
What was the bug that allowed more coins to be mined?
Was there a detailed explanation in some post?
Please link of available.
Thanks!
There is some post about it several pages back, the exact location is unknown. The problem appears to exist in all coins. I have tested the anomaly under a number of different parameters and the result is the same. There is a mathematics error in the code where essentially the mining rewards continue to reduce by half even beyond the 8th decimal. IE: even after the mining reward is cut in half down to 0.00000001 it continues to half even though the result cannot be seen. Eventually this causes a script error, and causes the block rewards to start over from the beginning. The easiest fix is a manual entry to tell the network to never produce coins after BLOCK # "X" ("X" will vary based on how the coin is set up.) I believe this error will effect most (if not all) current bitcoin / altcoin forks.
Wow! This is serious!
We need to make sure everybody in the crypto community knows about this, including the fact you/PMC found and fixed it.
I can't be 100% sure that all forks would suffer the same result, but I have enough reason to suspect it. And actually it was a random guy that spotted the error, we might be sitting here under different circumstances if it weren't for him. I merely patched it.
Could you maybe test the Bitcoin code and confirm whenever you have some time?
This would be a huge contribution of PMC if confirmed.
Yes, I have been meaning to do so, I simply haven't had time since things have been progressing so well with PMC. However, I fully intend to try it out of curiosity.
I'm the random guy!
The bug was in the GetBlockValue function. The problem was that the reward amount was determined by cutting by half the initial block reward every 250 blocks and the division was made by shifting the bits to the right. Doing this 64 times resetted the reward to the initial one. (I think using a normal division should solve the problem). I just watched the bitcoin source and it has the exact same problem. The difference is that bitcoin halves the reward every 210000 blocks instead of 250. So the reward will be resetted at block 13440000, when the number of the block divided by 210000 will be 64. I think we should tell them... but we have al lot of time to do it
(we are at block 288372...)You are an amazing person, and I cannot overstate my gratitude.
thanks
ps: I don't wanna seem greedy but in my signature you can find my address
( kidding of course ) 
