clintar2 and occasionally another dev is adding improvements to Boolberry's code base. Whether it is accessibility functions for being added to exchanges or the LMDB improvements
while b4h4mu7 is working with a parallel set of developers on a private repository that forks off of bytecoin, with the possibility of a coinswap to make this compatible, instead of merging the code base with Boolberry's existing code
[1]am I understanding this correctly? These are two parallel things?
Bytecoin uses RocksDB IIRC, while Monero went with the LMDB direction.[2] Since these can be stark differences, amongst others, is there intended to be any cross drift in the commits being done between repositories?
[1]Somewhat.
Clintar is no longer working on his LMDB code. At this point it doesn't make any sense to commit resources to the old codebase given the amount of work we're putting into the new one. The other developer you're speaking of, face, only took a break from the new codebase to make necessary API requirements so trading could resume for Boolberry. In hindsight, part of that effort turned out to be a waste of dev time since Hitbtc attempted to extort us for more funds. On the bright side Bisq.io will be adding BBR soon as a result of more recent improvements.
Since the developers are being paid in BBR it makes sense they have access to liquidity if they need to pay bills. I've been supplying them with BTC as they need it to manage the situation.
Regarding LMDB and RocksDB: We're doing extensive profiling between the two concepts and at the moment RocksDB is outperforming LMDB. We're still making optimizations to see if LMDB is worth making the switch. There are also other potential candidates for future profiling, most notably NuDB used by Ripple and SimDB. Ironically, Ripple was using RocksDB until they ran into scaling issues that made them create NuDB. The drawback is that its SSD only so users without SSD would need to revert back to RocksDB as is the case with Ripple or LMDB if that optimization proves otherwise.
https://github.com/vinniefalco/NuDB
https://github.com/LiveAsynchronousVisualizedArchitecture/simdb
[2] Cryptonote 2.0 codebase has been completely refactored from the original Bytecoin 1.0 (AEON, BBR, XMR, etc). So bringing in commits cross stream is no trivial task since essentially they are two separate projects. It's doable, but it doesn't make a lot of sense.
So, what do you want to do?
All of the aliased addresses on Boolberry's chain will be gone, do you want to import that feature? It has kind of half baked tying an alias to a block.
Do you want to import the dev tax?
The peculiarities around Boolberry's scaling "solution"?
or just relaunch a new cryptonote fork and do the swap, and start developing more from there
There are still bunches of things a cryptonote coin can do that others are not doing, to make it stand out