[BBR] Boolberry: Privacy and Security - Guaranteed Since 2014

[versprichnix]

... If he wants to contribute the door will always be open for him.

Better do not use this door.

The new direction is to do a snapshot of BBR blockchain and import that into the new codebase...

I like this idea.

[1714846681]

1714846681

[1714846681]

1714846681

[b4h4mu7]

... If he wants to contribute the door will always be open for him.

Better do not use this door.

If you're going to make a statement like that without even knowing the specifics of what we're working on or who is working on it, then you should justify it with some logic. No offense, but it just looks ignorant. Somehow you think its better for Zoidberg to work alone, than with a team of researchers and developers sharing a common goal? Also without real compensation? We all know where that got this project, if you want to repeat past mistakes then more power to you. It's 2017, almost 2018.. a project needs a full team to compete with top tier market caps. One person can't do it alone. The workload is too much and the competition is too stiff.

Remember, I wouldn't of had to build a team if there was already one here. I'll let Zoidberg decide for himself if he wants to contribute to new codebase after we do project reveal. Like I said, the door will always be open to him. Regardless of his decision, I've had positive interactions with him since starting this endeavor and regard him as a friend.

[rbrunner7]

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?

[versprichnix]

... a project needs a full team to compete with top tier market caps. ...

This sentence alone contradicts with humanity. I never would enter your room, but nevertheless you can count with me.

[teknohog]

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.

[rbrunner7]

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...

[b4h4mu7]

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 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.

[rbrunner7]

There's no 'outsiders' here, if you're a BBR holder then you're part of the community 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.

Thanks for the openness ... sounds interesting ... if only time would not be in such short supply ...

But for what it's worth, I write down a sketch of the result of my brainstorming. (Don't trust a random poster with less than a dozen posts too much, however.)

As I wrote already, it is based on my assumption (which may be false, who knows) that the technological differences between current and future Boolberry are simply too great to introduce it in the form of a single program that is able to "smoothly sail over a hard fork block height", so to say.

For the following let's call current Boolberry Boolberry Classic. A first hard fork brings to life its successor, Boolberry Intermediate, and the second hard fork introduces the real destination, Boolberry NT (for "new technology", of course).

Boolberry Intermediate is a true hard fork: A new version for transactions forces people to decide whether they follow and install it, which is a "Yes" vote for the whole endeavor, or whether they reject it and want to stay Boolberry as it is - a "No" vote.

Boolberry Intermediate is basically the current codebase, fully compatible, but with some crucial code added to manage the switchover to the new, incompatible blockchain: It is programmed to flat-out refuse adding any more transactions at and above the height for the second hard fork, so that basically the old chain can be "stopped" in an orderly way.

Furthermore, some yet-to-design mechanism would make it highly improbable that there will any competing chains in the last few blocks before the second hard fork height, of all things. Maybe be a single, temporary and single-purpose Boolberry masternode that is the only one with the power to mine the last few blocks, to really minimize the danger that the old chain ends in disagreement?

With the old chain "stopped", Boolberry NT can pick everything up and continue.

So that's my two-hardfork idea. If the introduction of Boolberry Intermediate fails, it's clear already rather early on that the project in the planned form does not fly, which I see as positive because it allows adjustments. If it succeeds, you have installed the necessary mechanisms for the switchover.

[tranzactionezlive]

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...

Hardfork is not the best way. I think the best way is to make it as it was in the past - better than the competition and without relinquishing its roots.

[soldat13]

where i can find a working BBR wallet or/and an exchange ? Thanks

No offical exchange at this times, You can add node to wallet!
It can sync your wallet!
Thanks

Ok thanks , can you send me a list to add node ?

[Mathgamain]

Hi everyone,

From where can I download wallet for windows ? Thanks !

- Tomi

[soldat13]

List of Node ? Thanks

[hashappliance]

List of Node ? Thanks

--seed-node 5.9.44.154:10101 --seed-node 66.228.33.249:10101 --seed-node 59.120.166.36:10101 --seed-node 62.201.213.25:10101 --seed-node 95.85.21.33:10101 --seed-node 107.170.97.197:10101

[clintar2]

Hi everyone,

From where can I download wallet for windows ? Thanks !

- Tomi

https://github.com/clintar/boolberry/releases/tag/v0.3a

[greatk]

Hardfork may not the best as it creates unnecessary competition, however when it becomes difficult for an agreement to be reached on the way forward it may be better to allow the different ideas to walk side by side. I will love to buy more BBR, wait and watch as events unfold.

[gigabyted]

Im still looking to buy some BBR, if you have some let me know!

Thanks!

[b4h4mu7]

Exchange Update

"Kucoin.com will list Boolberry(BBR) on 31st, October. The upcoming markets includes BBR/BTC and BBR/ETH. Users can start depositing BBR to Kucoin at 12:00, 28th, October (UTC+8), and trading at 20:00, 31st, October (UTC+8)." - https://news.kucoin.com/en/kucoin-will-list-boolberrybbr-on-31st-october/

Show some love and retweet!
https://twitter.com/kucoincom/status/922840284420915200

[dwarf0]

and what about stocks.exchange ? is it still an option?
PS   Much appreciate, b4h4mu7 ! Thank you for your great effort!

[cryptohunter]

Great to see BBR on an exchange again.

I tried to install clintars latest bbr wallet

I guess I need to add some seed nodes to get it to connect?

Also it does not seem bbr keeps everything in the appdata dir?

How to add seed nodes and back up the wallet?

thanks

[crypjunkie]

Any sellers? Hit me up!