Ninjastic
PostEdited versionsQuotes to this post
Post
Topic
Board Announcements (Altcoins)
Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released
by
b4h4mu7
on 21/10/2017, 17:27:36 UTC
Quote from: rbrunner7 on October 21, 2017, 04:31:04 PM
Quote from: teknohog on October 21, 2017, 04:13:50 PM
Quote from: rbrunner7 on October 21, 2017, 03:35:38 PM
Quote from: b4h4mu7 on October 20, 2017, 11:39:17 PM
The new direction is to do a snapshot of BBR blockchain and import that into the new codebase.

Isn't this simply known as a hard fork in crypto currency space? Where you always have the potential problem that the old chain lives on?
Yes, but if you look at the history of other cryptocoins, the likelihood of such forks living on is quite low.

A centralized coinswap is much worse in this respect, IMHO. I'd certainly be wary of sending all my coins to a "trusted" party, and I'd seriously look into maintaining a "classic" version. In contrast, it is much easier to simply update your software and accept the fact that old clients are no longer compatible.

I am an outsider, and I don't know what is planned the "new" Boolberry of course, but I would also say to hard fork the blockchain as seamlessly as possible is "the way to go", and "they way it's done", and if it's done properly, people will keep faith and mostly migrate to the new chain.

I have a hunch that part of the problem might be a difficulty for the new daemon to read the serialized blockchain of the old daemon, so that you can't just switch at a given block height within a single program, but must orchestrate a "daemon switch" of sort as well. A fascinating problem, if true, that got me thinking and has my head spinning. I currently brainstorm that I would probably try to do this with two hard forks...

There's no 'outsiders' here, if you're a BBR holder then you're part of the community Smiley Our development plans will be made public soon.

You're more than welcome to join the team meeting on Monday, just shoot me a PM. That invitation is also open for anyone else that wants to join our development efforts and provide technical value to the planning session. I want to include as many potential contributors from the community in this process and also after the project reveal. After all, this is a community project.