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

[crypto_zoidberg]

@crypto_zoidberg
This is a real info about BBR coin?
https://asktom.cf/index.php?topic=5097592.0

Have no idea who are these people, but they definitely have no relation to this project.

[boomboombazookajeff]

Hi folks! Good news!

After a long development process, we are finally ready to announce that Zano is nearing the release stage. Today, our team has prepared a short recap to showcase the project’s features, technical background, and much more, including a detailed explanation of Zano’s connection to our older project, Boolberry.

What is Zano?

Zano is our new blockchain project, primarily aimed at e-commerce related applications. While developing Zano, we have taken our previous experience into account, therefore Zano inherits some of the older technological principles that proved to be effective (e.g. CryptoNote). However, some of the features are developed completely from scratch.
Website: https://zano.org
Github: https://github.com/zano-project/zano

• Hybrid consensus algorithm
  One of the key features which brings next-level security to our network is the PoW/PoS hybrid consensus protocol. The network favors blockchain extensions where PoW and PoS based blocks alternate, therefore minimizing intrusion possibilities, such as eg. the 51% attack.
• Efficient asynchronous core architecture
  As scalability has always been an issue for older blockchain projects, we have put a lot of effort in the core of our project to make it as efficient as possible. As a result, we developed the asynchronous core architecture which allows for multiple transactions to be processed simultaneously.
  
• Multiwallet user-friendly fancy interface.
  To make things easier for the network members, our user interface can now handle multiple wallets at the same time.
  
• Optimized single-file wallet
  Any wallet can now be accessed with just a single file, which can be opened and used in various operation systems. Additionally, the size of this file is significantly optimized.
  
• Multisig
  The multi-signature feature is an important improvement which is now fully integrated in all wallets, as well as in the core of our project.
  
• Contracts & Peer-to-peer transactions
  The P2P transactions are now simple and efficient because of multi-functional contracts. Also, a high level of security is provided by the “Consolidated transactions” feature.
  
• Simplified Alias registration
  Now getting an alias is as simple as regular transaction
  

BBR Coinswap
When Boolberry was initially launched, no pre-mineable coins were made available. We are aware the all BBR supporters and coin holders were interested in the project the way it was at that time. So, to make sure the rules are fair for everyone, we decided to provide all BBR holders with an option to make their own choices in terms of swapping BBR for Zano.

However, the whole ecosystem of modern blockchain projects has massively changed over the past few years. Staying competitive progressively becomes more difficult, requiring highly qualified developers, software architects, marketing specialists, etc. Massive expertise in the field is crucial to provide the customers with a product that is efficient and easy to use for anyone.

We have invested a lot of time and effort into Zano, and user friendliness was one of the main focus points. Switching to Zano is made easy for any Boolberry user, as BBR coins can be exchanged for exactly the same amount of Zano coins. However, the coinswap is not forced in any way, so Boolberry users can keep BBR if they prefer.

Is Zano a hardfork?
It is very important to understand that Zano is not a hardfork of Boolberry. The BBR blockchain with all the past transactions is not copied over to Zano. This is an entirely new project, with its’ own genesis block. In Zano, coins are partially reserved for pre-mining and BBR coinswap.

Why do we burn swapped coins?
We are convinced that hardforks (or cloneforks) like Bitcoin Cash and Bitcoin Gold, where the old blockchain is copied over, do not support the core idea of all cryptocurrencies. This is because hardforks like these create a vacuum that blurs the value of blockchain technology.
In Zano, we offer users an option to upgrade to a more innovative project, while the option to stay on Boolberry remains. The coinswap is executed in a way where the BBR coins that get converted to Zano no longer exist in Boolberry network.

How does coinswap work exactly?
From the user perspective, the coinswap is essentially making a transaction to a special Zano address, which always starts with the letter “Z”. We made the coinswap process as easy and transparent as possible to alleviate any potential confusion. Coinswap transactions can be executed via the normal GUI, simplewallet, or even directly from a coin exchange. In any case, the coinswap works just like a usual transaction.

From the technical perspective, coinswap is a special Boolberry transaction, which includes an encrypted Zano address in the extra data. This Zano address is where the converted coins are sent to. The actual output key of this transaction is zero, so after the coinswap the BBR coins are no longer possible to spend.  

What about Boolberry?
We will continue to maintain and support Boolberry, as well as copy a few minor features from Zano. For example, an updated GUI based on qtWebEngine, an optimized compact wallet, and more. Besides that, we will keep releasing new patches to minimize bugs and vulnerabilities, and generally keep developing Boolberry as a classic PoW project.

What’s next?
As of today, Zano remains in final development stage. Some of the project’s features are still unfinished. In the release version, more will be added, for instance features like Black wallet, market nodes, and other multisig use cases. Stay tuned for more updates!

Bitcointalk announcement post: https://asktom.cf/index.php?topic=5090272

When will this be listed on any exchanges?

[crypto_zoidberg]

Hi folks! Good news!

We finally got a brief history of the Boolberry project for those who have not followed it since 2014:

https://medium.com/@BoolberryBBR/a-brief-history-of-boolberry-c4048d692272

Enjoy!

[l8orre]

Hi folks! Good news!

We finally got a brief history of the Boolberry project for those who have not followed it since 2014:

https://medium.com/@BoolberryBBR/a-brief-history-of-boolberry-c4048d692272

Enjoy!

how about joining the Komodo ecosystem? you know the team and the advantages, so come on board!

[crypto_zoidberg]

Hi folks! Good news!

We finally got a brief history of the Boolberry project for those who have not followed it since 2014:

https://medium.com/@BoolberryBBR/a-brief-history-of-boolberry-c4048d692272

Enjoy!

how about joining the Komodo ecosystem? you know the team and the advantages, so come on board!

Sorry, i'm not really familiar with Komodo ecosystem, can you highlight the advantages of joining it?

[l8orre]

Komodo is the evolution of jl777's Supernet-
you do know jl777, right?

[crypto_zoidberg]

Komodo is the evolution of jl777's Supernet-
you do know jl777, right?

Oh yeah, I can remember him from his appearance in BBR community. We'll check this, but still - if you can remind the advantages to the topic followers would be really great!

[crypto_zoidberg]

FYI: just posted brief description about the draft for new difficulty adjustment: https://asktom.cf/index.php?topic=5090272.msg49633658#msg49633658

[Newton90]

will boolberry's team add coin on any big exchange?

[tbearhere]

FYI: just posted brief description about the draft for new difficulty adjustment: https://asktom.cf/index.php?topic=5090272.msg49633658#msg49633658

Good work crypto_zoidberg. Thank you. 

[crypto_zoidberg]

IMPORTANT NOTICE: Since our team is working on different projects(like pools, block explorers and so on) we renamed github account name from “zano-project” to “hyle-team”(hyle.io is company name), so you have to update all your local repositories links. Sorry for the inconvenience!
This is not related to Boolbery itself, only to zano-related projects.

[sowle]

Hey, guys!
While Zano mainnet is getting ready we keep improving Boolberry, and quite a few changes were made recently.
Here I would like to highlight the most important of them for you:

General:
* log library was updated to the version which supports log channels (taken from Zano)
* added anti-deadlock mechanism, which could track potential traps and save us a lot of time in case of multithreading problems
* fixed a bug with possible http flood (thanks to anonimal for pointing to this)
* implemented secure and compact Boolberry->Zano coinswap mechanism

GUI:
* we ported GUI library from old unsupported QT WebKit to stable and smooth QTWebEngine (special thanks to our contributor Alexandra (aldobryn on github) )
* added Unicode support for wallet file path, now it can easily be located in your favorite folder

CLI wallet (simplewallet):
* simplewallet was greatly improved to be able to work with modern exchanges:
** offline mode implemented for cold wallet support
** exchange API for cold-signing was reviewed and updated
** fixed a bug with incorrect coins handling for watch-only wallets

* simplewallet got new commands:
** viewkey -- shows your view keypair
** spendkey -- shows your spend keypair
** recent_blocks -- prints income/outgo per-block summary for last N block containing your txs (it's useful, try it!)
** show_dust -- as you may expect shows how much dust (tiny unspent outputs) you have
** print_ki -- prints key image info

* sweep_below command and RPC was improved to work better when lots of small outputs are present in the wallet


Today we're releasing a new build: Boolberry 0.3.0.90 containing all these improvements:
https://github.com/cryptozoidberg/boolberry/releases/tag/v0.3.0.90


Thank you for your support and feedback!

Boolberry team

[crypto_zoidberg]

Hey, guys!
While Zano mainnet is getting ready we keep improving Boolberry, and quite a few changes were made recently.
Here I would like to highlight the most important of them for you:

General:
* log library was updated to the version which supports log channels (taken from Zano)
* added anti-deadlock mechanism, which could track potential traps and save us a lot of time in case of multithreading problems
* fixed a bug with possible http flood (thanks to anonimal for pointing to this)
* implemented secure and compact Boolberry->Zano coinswap mechanism

GUI:
* we ported GUI library from old unsupported QT WebKit to stable and smooth QTWebEngine (special thanks to our contributor Alexandra (aldobryn on github) )
* added Unicode support for wallet file path, now it can easily be located in your favorite folder

CLI wallet (simplewallet):
* simplewallet was greatly improved to be able to work with modern exchanges:
** offline mode implemented for cold wallet support
** exchange API for cold-signing was reviewed and updated
** fixed a bug with incorrect coins handling for watch-only wallets

* simplewallet got new commands:
** viewkey -- shows your view keypair
** spendkey -- shows your spend keypair
** recent_blocks -- prints income/outgo per-block summary for last N block containing your txs (it's useful, try it!)
** show_dust -- as you may expect shows how much dust (tiny unspent outputs) you have
** print_ki -- prints key image info

* sweep_below command and RPC was improved to work better when lots of small outputs are present in the wallet


Today we're releasing a new build: Boolberry 0.3.0.90 containing all these improvements:
https://github.com/cryptozoidberg/boolberry/releases/tag/v0.3.0.90


Thank you for your support and feedback!

Boolberry team

👍🤘

[Ohgreatanotherone]

This might come off as a very dumb question, but is the BOOL trading on Hotbit the same as this Boolberry? I know Boolberry trades as BBR according to information on CMC, but when I checked for BOOL, I also got BBR. Just wanted to be sure so as not to buy a brick

[tbearhere]

Hey, guys!
While Zano mainnet is getting ready we keep improving Boolberry, and quite a few changes were made recently.
Here I would like to highlight the most important of them for you:

General:
* log library was updated to the version which supports log channels (taken from Zano)
* added anti-deadlock mechanism, which could track potential traps and save us a lot of time in case of multithreading problems
* fixed a bug with possible http flood (thanks to anonimal for pointing to this)
* implemented secure and compact Boolberry->Zano coinswap mechanism

GUI:
* we ported GUI library from old unsupported QT WebKit to stable and smooth QTWebEngine (special thanks to our contributor Alexandra (aldobryn on github) )
* added Unicode support for wallet file path, now it can easily be located in your favorite folder

CLI wallet (simplewallet):
* simplewallet was greatly improved to be able to work with modern exchanges:
** offline mode implemented for cold wallet support
** exchange API for cold-signing was reviewed and updated
** fixed a bug with incorrect coins handling for watch-only wallets

* simplewallet got new commands:
** viewkey -- shows your view keypair
** spendkey -- shows your spend keypair
** recent_blocks -- prints income/outgo per-block summary for last N block containing your txs (it's useful, try it!)
** show_dust -- as you may expect shows how much dust (tiny unspent outputs) you have
** print_ki -- prints key image info

* sweep_below command and RPC was improved to work better when lots of small outputs are present in the wallet


Today we're releasing a new build: Boolberry 0.3.0.90 containing all these improvements:
https://github.com/cryptozoidberg/boolberry/releases/tag/v0.3.0.90


Thank you for your support and feedback!

Boolberry team

Thank you.    On your next build.. could you make the fonts bigger plz. thx 

[crypto_zoidberg]

Hey, guys!
While Zano mainnet is getting ready we keep improving Boolberry, and quite a few changes were made recently.
Here I would like to highlight the most important of them for you:

General:
* log library was updated to the version which supports log channels (taken from Zano)
* added anti-deadlock mechanism, which could track potential traps and save us a lot of time in case of multithreading problems
* fixed a bug with possible http flood (thanks to anonimal for pointing to this)
* implemented secure and compact Boolberry->Zano coinswap mechanism

GUI:
* we ported GUI library from old unsupported QT WebKit to stable and smooth QTWebEngine (special thanks to our contributor Alexandra (aldobryn on github) )
* added Unicode support for wallet file path, now it can easily be located in your favorite folder

CLI wallet (simplewallet):
* simplewallet was greatly improved to be able to work with modern exchanges:
** offline mode implemented for cold wallet support
** exchange API for cold-signing was reviewed and updated
** fixed a bug with incorrect coins handling for watch-only wallets

* simplewallet got new commands:
** viewkey -- shows your view keypair
** spendkey -- shows your spend keypair
** recent_blocks -- prints income/outgo per-block summary for last N block containing your txs (it's useful, try it!)
** show_dust -- as you may expect shows how much dust (tiny unspent outputs) you have
** print_ki -- prints key image info

* sweep_below command and RPC was improved to work better when lots of small outputs are present in the wallet


Today we're releasing a new build: Boolberry 0.3.0.90 containing all these improvements:
https://github.com/cryptozoidberg/boolberry/releases/tag/v0.3.0.90


Thank you for your support and feedback!

Boolberry team

Thank you.    On your next build.. could you make the fonts bigger plz. thx 

Sure, can you send exact screenshot and point which fonts you would like to see bigger ?
And what platform you have(macos, linux, windows)? And what DPI/resolution?

[tbearhere]

Hey, guys!
While Zano mainnet is getting ready we keep improving Boolberry, and quite a few changes were made recently.
Here I would like to highlight the most important of them for you:

General:
* log library was updated to the version which supports log channels (taken from Zano)
* added anti-deadlock mechanism, which could track potential traps and save us a lot of time in case of multithreading problems
* fixed a bug with possible http flood (thanks to anonimal for pointing to this)
* implemented secure and compact Boolberry->Zano coinswap mechanism

GUI:
* we ported GUI library from old unsupported QT WebKit to stable and smooth QTWebEngine (special thanks to our contributor Alexandra (aldobryn on github) )
* added Unicode support for wallet file path, now it can easily be located in your favorite folder

CLI wallet (simplewallet):
* simplewallet was greatly improved to be able to work with modern exchanges:
** offline mode implemented for cold wallet support
** exchange API for cold-signing was reviewed and updated
** fixed a bug with incorrect coins handling for watch-only wallets

* simplewallet got new commands:
** viewkey -- shows your view keypair
** spendkey -- shows your spend keypair
** recent_blocks -- prints income/outgo per-block summary for last N block containing your txs (it's useful, try it!)
** show_dust -- as you may expect shows how much dust (tiny unspent outputs) you have
** print_ki -- prints key image info

* sweep_below command and RPC was improved to work better when lots of small outputs are present in the wallet


Today we're releasing a new build: Boolberry 0.3.0.90 containing all these improvements:
https://github.com/cryptozoidberg/boolberry/releases/tag/v0.3.0.90


Thank you for your support and feedback!

Boolberry team

Thank you.    On your next build.. could you make the fonts bigger plz. thx  

Sure, can you send exact screenshot and point which fonts you would like to see bigger ?
And what platform you have(macos, linux, windows)? And what DPI/resolution?

Sure     Thx.

[crypto_zoidberg]

Hi Folks!

FYI: https://asktom.cf/index.php?topic=5090272.msg49891307#msg49891307

Zoidberg

[skygonga]

Linking C static library libz.a
make[3]: Leaving directory `/root/boolberry/build/release'
[ 26%] Built target zlibstatic
make[3]: Entering directory `/root/boolberry/build/release'
Scanning dependencies of target common
make[3]: Leaving directory `/root/boolberry/build/release'
make[3]: Entering directory `/root/boolberry/build/release'
[ 26%] Building CXX object src/CMakeFiles/common.dir/common/base58.cpp.o
In file included from /root/boolberry/contrib/epee/include/misc_log_ex.h:54:0,
                 from /root/boolberry/contrib/epee/include/include_base_utils.h:31,
                 from /root/boolberry/src/common/util.h:12,
                 from /root/boolberry/src/common/base58.cpp:14:
/root/boolberry/contrib/epee/include/os_defenitions.h:34:5: warning: "_WIN32" is not defined [-Wundef]
 #if _WIN32 || _WIN64
     ^
/root/boolberry/contrib/epee/include/os_defenitions.h:34:15: warning: "_WIN64" is not defined [-Wundef]
 #if _WIN32 || _WIN64
               ^
In file included from /root/boolberry/contrib/epee/include/misc_log_ex.h:63:0,
                 from /root/boolberry/contrib/epee/include/include_base_utils.h:31,
                 from /root/boolberry/src/common/util.h:12,
                 from /root/boolberry/src/common/base58.cpp:14:
/root/boolberry/contrib/epee/include/misc_os_dependent.h:114:35: fatal error: boost/core/demangle.hpp: No such file or directory
 #include <boost/core/demangle.hpp>
                                   ^
compilation terminated.
make[3]: *** [src/CMakeFiles/common.dir/common/base58.cpp.o] Error 1
make[3]: Leaving directory `/root/boolberry/build/release'
make[2]: *** [src/CMakeFiles/common.dir/all] Error 2
make[2]: Leaving directory `/root/boolberry/build/release'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/boolberry/build/release'
make: *** [build-release] Error 2
root@iZhp3a3slnxeawyllt1n1zZ:~/boolberry#




V0.3.0.90 Compile error! The previous version can be compiled normally!

[crypto_zoidberg]

Linking C static library libz.a
make[3]: Leaving directory `/root/boolberry/build/release'
[ 26%] Built target zlibstatic
make[3]: Entering directory `/root/boolberry/build/release'
Scanning dependencies of target common
make[3]: Leaving directory `/root/boolberry/build/release'
make[3]: Entering directory `/root/boolberry/build/release'
[ 26%] Building CXX object src/CMakeFiles/common.dir/common/base58.cpp.o
In file included from /root/boolberry/contrib/epee/include/misc_log_ex.h:54:0,
                 from /root/boolberry/contrib/epee/include/include_base_utils.h:31,
                 from /root/boolberry/src/common/util.h:12,
                 from /root/boolberry/src/common/base58.cpp:14:
/root/boolberry/contrib/epee/include/os_defenitions.h:34:5: warning: "_WIN32" is not defined [-Wundef]
 #if _WIN32 || _WIN64
     ^
/root/boolberry/contrib/epee/include/os_defenitions.h:34:15: warning: "_WIN64" is not defined [-Wundef]
 #if _WIN32 || _WIN64
               ^
In file included from /root/boolberry/contrib/epee/include/misc_log_ex.h:63:0,
                 from /root/boolberry/contrib/epee/include/include_base_utils.h:31,
                 from /root/boolberry/src/common/util.h:12,
                 from /root/boolberry/src/common/base58.cpp:14:
/root/boolberry/contrib/epee/include/misc_os_dependent.h:114:35: fatal error: boost/core/demangle.hpp: No such file or directory
 #include <boost/core/demangle.hpp>
                                   ^
compilation terminated.
make[3]: *** [src/CMakeFiles/common.dir/common/base58.cpp.o] Error 1
make[3]: Leaving directory `/root/boolberry/build/release'
make[2]: *** [src/CMakeFiles/common.dir/all] Error 2
make[2]: Leaving directory `/root/boolberry/build/release'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/boolberry/build/release'
make: *** [build-release] Error 2
root@iZhp3a3slnxeawyllt1n1zZ:~/boolberry#




V0.3.0.90 Compile error! The previous version can be compiled normally!

What boost version are you using? You probably have to install/build on fresh boost version.