crypto_zoidberg himself said he recommended upgrading the database to LMDB like Monero did, which would help with the RAM problems (see below). The "Blockchain Development Company" made some minor commits last November but other than that, I see no evidence of this database work. We need real developers on this project with the skills to do this work. If CZ truly returns to active development then perhaps he can accomplish this & maybe Boolberry will survive, otherwise maybe BDC needs to hire developer(s) who can accomplish this, and other tasks which Boolberry desperately needs. If real development is dead, then Boolberry may suffer this fate in its current state, hurting all the newcomers & causing even more frustration for potential investors. Pumping a coin by simply renaming the ticker symbol & re-coloring the GUI will not help with any long term growth potential, but will actually cause more frustration for investors if the core development problems are not resolved, and the price will come crashing back down as seen today.
....
Thanks for your work. Let's continue moving this way. Make commits to your repository so I and everybody else can review them. The most urgent task for me is to merge DB branch from the original repository to master. Daemon needs a lot of memory to run right now. That's not good for a decentralized system. I would prefer you to checkout DB branch and commit on top to make the review process simpler.
DB is really important task, and idea was to quickly implement basic db support in BBR using level_db, but to go forward problem is that level_db doesn't have transactions support, so we need to go with something like LMDB, which means to rewrite current code in db branch.
I guess this gonna take about 1 month of hard work. (but not a hard fork! don't be confused)
So if
1blockologist is about to implement something useful for BBR - implement working daemon with suitable memory consumption using LMDB would be good move.
Zoidberg