1 Year Anniversary AnnouncementOn behalf of the Criptoe team, I would like to apologize for my extreme lack of communication regarding taking over KDC development. My team lost a dedicated coder a few months back to real life commitments, and we have been struggling to find a trustworthy replacement ever since. Additionally, we got heavily invested, both with money and time, on other coin projects and have not been able to step away to work on KDC. Now that progress has been made with these other projects, we can dedicate more time to reviving this coin.
Being that it is the 1 year anniversary of KDC, I would like to reiterate my initial intentions of bringing KDC back to life. I have been working on updating the codebase for KDC for the last week or so, and I'm pleased to announce that I am very close to releasing a new wallet version. While this initial update won't be as amazing as what I would have liked to have included with these updates, it will be a solid plan of action to get the KDC blockchain thriving again until we can push forward with the more exciting changes.
These updates include:- An update to the latest stable release of the LTC codebase. This will help keep KDC in line with the latest patch fixes and security patches that are released.
- A move to the Digishield difficulty algorithm.
- A increase in the block time from 60 seconds to 90 seconds.
- Initial block rewards will be increased to 6KDC per block, which decreases by 1% per month for the life of the coin.
- A 5 million KDC increase in the total number of coins.
Additional line items were discussed a few months back with community members and will most likely be implemented over time. For now, my team's focus is on maintaining the codebase, and keeping the blockchain moving in a secure manner for the foreseeable future.
To expand on the above items:
Digishield is paramount to the success of KDC mining, as the current KGW algo has been proven ineffective almost everywhere else. It is susceptible to time warp attacks, even with the patches that are currently in place, and it doesn't stand a chance against the hashrate increases we can possibly see with multipool hopping.
The increase in block time and revision of the payout schedule will extend the mining date substantially, yet still keep transactions fast. Initial projections have the mining time continuing out to around 200+ months, with a total mine-out block value of around 0.25KDC. A slow, gradual decrease so we can ease into diminishing returns, instead of causing market shock with dramatic halvings. The initial code release will probably have around the block values for 6 months hard-coded, and will be replaced with the cummulative percentage code at a later time.
The reason for the increase in total supply is two-fold. First, after a year of life, and a long period of inactivity, there are probably a lot of coins lost due to deleted wallets and such. I fully agree that it probably isn't to the tune of 5 million coins, but with the total mined coins getting closer to 9 million, we're almost half way through the supply. Lets call it a kickstart of sorts to get this revitalization going again. Secondly, and most importantly, it helps extend mining time with the revised payout structure. While some community members might be against an increase due to supply/demand concerns and price shock, let's be honest- KDC is pretty dead right now. My team has been keeping the chain moving with 2 miners for some time now just to keep Cryptsy confirmations going. The community will set the demand, regardless of the supply. I'll go ahead and make a prediction that in the days following this post, KDC will be bought in bulk on Cryptsy. Keep that in mind when the whole supply/demand debate comes up.
Here is where some questions come into play:
- Are the proposed initial changes acceptable with the community? If so, I could probably have a finalized update ready by late this weekend or early next week.
- Should we include a pre-mine block in this update to be stored in a fully transparent and accountable dev/bounty wallet? This pre-mine would be controlled by my team, and would only be used for valid KDC rewards and projects. No pre-mine scam nonsense, just funds to use when we need to pay to have things done or reward community members' efforts.
- Lastly, and this is a big one that would require a lot of discussion, would the community rather scrap the old blockchain and start fresh with a existing balance buyout? This would clean up the code substantially, and possibly allow the use of a different codebase and features. For instance, the Digibyte codebase could be used, and multi-algo mining could be introduced to KDC. Also, it would greatly decrease the blockchain bloat we experienced when we went through the fork issues that my team solved early on. If you resync the wallet from scratch, you will notice a period in the chain where the sync hangs. This is the period of orphans and rejected blocks caused by the fork.
Again though, this is a little more substantial than the changes I noted in the pending update, and would require additional planning. I'm not opposed to doing this, but essentially we would scrap KDC and start new. We could finally move away from the 47 key address scheme and move to 46, aka getting rid of addresses with "L" as the starting letters... I have no idea why that was chosen to begin with.
If there is no major objection to anything, or if there is no community response, we'll probably push forward with the initial update plans. If people want to hold off and discuss this before we move forward, let me know, and we'll pump the brakes.
Here's to a new year, and a new beginning.
Cheers,
Fuse