Quote from: bitfreak! on January 02, 2017, 08:22:31 AM

Quote from: Blockchain Mechanic on January 01, 2017, 01:10:37 PM

Since the original dev is around, i will be stepping back to let him resolve the issues.

I didn't code Cryptonite, I helped develop the concepts behind it and funded the development of it. If you read the first pages of this thread you will see we had a core dev but he's no longer around. As I've said before, not having a premine makes it hard to attract developers. I made a mistake assuming that open source developers would continue improving Cryptonite. My C++ skills are still fairly limited so it's unlikely I will be able to solve all these issues myself, but I am looking in the sync issues.

Based on some research I did a few days ago many of the bugs in Cryptonite have been carried over from Bitcoin. For example, there are Bitcoin bug reports about wallet corruption submitted around the time Cryptonite was forked from Bitcoin. The bugs are clearly related because even the error numbers and error messages are the same as the ones reported by people using Cryptonite. I think many of the bugs in Cryptonite could be solved simply by applying many of the fixes which have since been applied to Bitcoin.

The version of Bitcoin used to create Cryptonite also lacked several important features it has now. As I said earlier, the networking code was fairly poor and only allowed the blockchain to be downloaded from one peer at a time. Back then, Bitcoin also didn't download the block headers before downloading blocks, so it had to download blocks in order and couldn't do it in parallel.

Cryptonite was actually the first coin to implement the headers first approach, Bitcoin gained that feature shortly after the release of Cryptonite. However our headers first implementation was rushed and is not as robust as the Bitcoin implementation, and without good networking code we cannot download blocks in a parallel fashion from multiple peers at the same time, which is much faster and less error prone.

Once again I think many problems with Cryptonite could be solved by adapting the new networking code and new syncing code from Bitcoin so that the headers first synchronization works more smoothly. I am looking into how I can make some of these upgrades myself but like I said my skills are limited. Also I wont be back home for another day or two and I'm stuck with a slow laptop which doesn't have much of my software on it.

My point is, Cryptonite needs all the developers it can get right now. I know it's not easy to locate these bugs and fix them because it probably would have been done by someone by now. If we had the original dev it would probably be a lot easier to fix these issues but I doubt he will be coming back any time soon so we need other developers to keep Cryptonite alive.

I have been considering the idea of remaking Cryptonite and implementing a pre-mine, then allowing the old coins to be converted to the new coins, but I'm not exactly sure how that would be done in a fair manner. I'm not sure if that would really be a good idea but at least then we could provide a reason for devs to work on the new version of Cryptonite.

Work together guys, looks like you would make a great team collaborating. As for funding, I think a coin swap @ 90% would be accepted by most, that would create 10% for ongoing dev expenses. The other option is donations, but might get a lot less that way.