Post revised because OP is a liar.
Hello Intellect community
I found a bug in the code. Hardfork on Sunday. (Most likely) Testing in testnet
Do you like to tell us what the bug is?
overflow in calculation:
nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;
There is absolutely no way that value, would
ever overflow in this usage.
The arithmetic is wrong.
The Gold Pieces arithmetic is bugged as well, in exactly the same place. You divide by COIN when you want coins and not satoshis. Does it really take 10 forum pages to correctly point this out?
nope, you're wrong, it is not a clone
This bug is with a large annual interests
I'm wrong? And what about the last 10 pages of posts?
What you're saying here, is that the Bitcoin foundation chose int64 because it was to be susceptible to common arithmetic overflows? This is the opposite of why int64 is used instead of a float or double. You have a calculation range of +/- 9223372036854775807 (-1) satoshis, more than you would ever need, without any issue of precision. GP is wrong in the EXACT same place.
This isn't development, it's copy/pasting horribly written code and guessing what it does, then changing numbers. You assumed the code was already correct.
nope, you're wrong, it is not a clone
(GP main.h L41)
static const int64_t MAX_MINT_PROOF_OF_STAKE = 5 * COIN; // 500% annual interest
(GP main.cpp L982)
int64_t nRewardCoinYear;
nRewardCoinYear = MAX_MINT_PROOF_OF_STAKE;
int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;
(ILT main.h L41)
static const int64_t MAX_MINT_PROOF_OF_STAKE = 36.50 * COIN; // 3650% annual interest
(ILT main.cpp L998)
int64_t nRewardCoinYear;
nRewardCoinYear = MAX_MINT_PROOF_OF_STAKE;
int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;
I was going to post a solution, but since you are intent on lying to all of us, I don't think that's wise. Not a complete clone, but it's up the family tree. Anyone with half a brain(in fact math only needs half) could figure out how to simplify this to make overflows practically impossible. What they might not see, is that dividing by COIN
still puts the fuckin return value in non-satoshi format (THE REQUIRED FORMAT). The same thing I posted 11 pages ago. There is a little more to it, though.