We are 15k blocks ahead of schedule. This has nothing to do with wanting to hold what we already have. None of us have sold a single Benjamin, and in fact have used most of what we mined for giveaways on Reddit, Twitter, Cryptocointalk, and several other sites
Read what Igotspots quoted above. It explains our decision and gives reasons why a fork would make the situation worse. 10 minute block times are better for security, this is a known issue, as well as the KGW holes recently found, further strengthen our decision not to fork
Coins should not be created to serve the miners, but the consumers who will use them in the end. Benjamins will be one of the most secure blockchains once it has the hashpower to back up the numbers. Security and not losing coins or leaving them vulnerable to attack so vendors, exchanges, or traders don't lose payments is more important to us than making a few coin hopping miners happy. I'm sorry, but that's the truth. The ones that have stuck around mining since the beginning will enjoy having rarer-than-planned coins, but that was definitely not our intention
Sorry to be blunt but you are delusional.
Appealing to miners is
ABSOLUTELY REQUIRED. Without miners transactions cannot be confirmed. No sending coins, no receiving coins, no mining coins.
I'm not saying BEN needs KGW. I'm not saying BEN has to decrease the block time (although, it would be my preference if it did). But the diff adjustment issue has to be addressed. Mark my words, the next diff adjustment will never, ever, ever arrive, BEN will never, ever, ever see anything close to 10-minute block times again if you do not fork this coin.
I can't make it any more clear. If we make difficulty adjust faster, it will go up every block. Every block will get harder than the previous, increasing the time even further than if it jumps every 2000 blocks. The long time in between will let the network catch up. If difficulty is changed more frequently, it will go up more than if we don't fork it before it goes down
You did the math before, so I know you understand how far ahead we are. Surely you realize what I mean?
I do understand what you mean, but I don't think you understand what I mean
Simply changing the diff adjustment to every 1 blocks will not fix the problem. The diff algorithm itself also needs to be changed, and adjusted to take into consideration the current block height.
Current diff algo looks at the current block height, versus the expected block height and adjusts the difficulty up or down based on how close we are to the expected block#.
This algo is no good, BEN will never, ever correct itself using this algorithm (well, maybe eventually, but it will take YEARS).
A new diff adjustment algorithm must be implemented, maybe one that does not look at the expected block height, but looks at the length of time it took to complete the previous X number of blocks and adjusts the diff accordingly (pretty sure this would work, but I'm just shooting from the hip here).
Additionally, the diff adjustment period must also be reduced - otherwise, BEN will simply end up with the same problem again in a couple weeks.