Would it be possible for someone with 2116 Sig to kill the block chain when it gets to proof of stake?
This is not my area of expertise, but if my numbers are within 4-5 orders of magnitude this is a critical issue.
if interest is paid hourly, as has been stated, it must be recorded on the block chain.
Not sure interest will be paid hourly, where did you read that ?This is not my area of expertise, but if my numbers are within 4-5 orders of magnitude this is a critical issue.
if interest is paid hourly, as has been stated, it must be recorded on the block chain.
A 5 minute payout would be 0.0000004756 so 0.02102608 Sig per wallet, but you would only need 15,000. 15,000 * 0.02102608 + 150 = 465.3912
Main.cpp sets
Code:
nSubsidy = nCoinAge * COIN_YEAR_REWARD * 33 / (365 * 33 + 8)
From what I can tell it simplifies to "nCoinAge * 13689" All the math is e-8, but if nCoinAge is the mature coins and it runs every 5 minutes then this is a 1400% return.
Hopefully I am wrong.
Edit: Fixed exponential.
I flipped the nSubsidy calculation around and for 5% return it would be 365.24242424242424242424242424224 payments, so daily payments considering leap year. This would be the second functional error I have found in the white paper.
So 43516 Sig used to create 4320000 addresses with 0.00007305 Sig each could flood the chain with interest transactions?
What can you expect about these guys who only know how to code but doesn't understand the math.
and can only guess whether it's actually a bad luck or a pool is just stealing your rewards.
more for us I guess >.<