Yet we can take some comfort in the fact that a block time even 5x higher than the target 2 minutes is still only 10 minutes, which is reasonable and works for bitcoin, 10x higher is 20 minutes, it is not insufferable.
When you're talking a block at a time, no, 5x longer (10 minutes instead of 2) is not a big deal. But, when you consider that the difficulty won't retarget for 720 blocks, you're looking at 5 days instead of 1. That
is a significant difference.
In
another thread, somebody has commented:
You want to attract miners that believe in the coin and hold it.
This leads me to the question: if the core miners "believe in the coin and hold it", why would 5 days for a retarget be a big issue?
I hope we never see such a thing and want to avoid it too, but the question is valid.I tend to be sensitive on the hash-rape issue, because I've been mining CasinoCoin off and on Since December, and it has been a huge issue for us. (edit:) And keep in mind, most of this is before scrypt asics were even available to the public.
http://www.coinwarz.com/network-hashrate-charts/casinocoin-network-hashrate-chartOriginal coin - Scrypt algo, with 30 second blocks and 720 block retarget:
I think now is the time to start discussing the possibility of altering the difficulty adjustment for CasinoCoin. Currently, the difficulty adjust occurs every 720 blocks. Theoretically, with the 30-second block times, this is adjustment is supposed to occur every 6 hours. But with the multipool effect and swings in hashrates, I've seen it take 15+ hours for the next adjustment to occur. I'm considering cutting down the difficulty adjustment down to 1/6th from 720 blocks to 120 blocks. I will make a separate post in order to propose this change and get others thoughts before proceeding.
After implementing Kimoto Gravity Well:
Argh, didn't find a block for like 34 hours now...
Even with DigiShield:
Difficulty is way off and needs fixing ....
The last 30 days there should have been about: 30 * 24 * 60 * 2 = 86400 blocks. In reallity there where about 48320 from block 488600 to 536920. That is about 60% of what it should be. I get a lot of complaints from miners that they do not get as much coins as the expect to get, not sure what the cause is but this should improve!
Finding blocks is a random event, due to this
randomness a sampling over a longer time period will be more accurate than one over a shorter time period. KGW and DS both show this to be true. Blocks are supposed to be found evenly
on average, not one every x minutes. Your examples show the rationale on why I chose not to use either of these for Bitmark. Thank you.
This is similar to a 51% attack, where a bad actor can acquire more hashing power than the network collectively. Only a strong distributed network of hash power can achieve this. In the future I am less concerned as Bitmark is
configured to encourage hash power distribution.
In the immediate future, the short term, all we can try to do is disincentive this from happening. The block reward maturity being longer than the difficulty change combined with no inflated value.
If there are any other social or technical things we can do to mitigate the risk of this over the first few months, they would be good to know.
We could always increase the block reward maturity further, to be 2 days, or even 7. That would ensure only those who "believe in the coin and hold it" would mine, but may be detrimental on the crashes. Hoarding will occur, there will be big sells in the future, we do not want to drive away miners when this happens, as that would cause a death spiral.
Balance is hard to achieve.