Quote from: FiniteRed on June 08, 2017, 10:33:56 AM

Hey all

Master nodes may work for CBX, however I would first focus on fixing the current blockchain so it downloads / synchronises in a reasonable amount of time / at all - the bootstrap file is a nice work around but it makes everything look somewhat broken / un-managed if you have to do anything but install it and leave it to sync.

Connectivity is an issue for sure; master nodes will help here but the amount of CPU churn the wallet imparts on the hosting machine is crazy high - especially as the CBX network is currently processing a tiny fraction of the total number of transactions that it may one day be processed if CBX's profile raises considerably.

I would highly recommend:

Snapshot the current chain, hard fork, re-start the block index from zero, adapt the code base of one of the other POS coins in existence that synchronise correctly end to end (headers first certainly improved the bitcoin blockchain download) and re-implement PoSV2 on top. You will consolidate the source, gain all of the various security fixes and start fresh from a known good state.

After all that we will have a fast, efficient syncing coin - supported by master nodes that anyone can download and synchronise without additional support

FR

Memory issue is still a big problem that I am working on.
During these last few months I have been a bit unavailable and I am sorry about that.

Anyway, CBX development will start back soon.
Of course CBX use some CPU and RAM and it gonna be fix with updates of masternode because I plan to change the whole code base of CBX and keep it compatible with old blockchain.

I am personnaly against a re-start to the block zero, that's against the blockchain philosophy