Author

Topic: [BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 211. (Read 1210779 times)

legendary
Activity: 1526
Merit: 1002
Bulletproof VPS/VPN/Email @ BadAss.Sx
I'm trying to install Boolberry wallet headless in Ubuntu. As far as i know it needs libboost1.55-all-dev which can be downloaded from repo ppa:boost-latest/ppa.

But if i do  sudo apt-get -y install gcc-4.8 g++-4.8 libboost1.55-all-dev git cmake, i get this:

Quote
$ sudo apt-get -y install gcc-4.8 g++-4.8 libboost1.55-all-dev git cmake
Reading package lists... Done
Building dependency tree      
Reading state information... Done
cmake is already the newest version.
g++-4.8 is already the newest version.
g++-4.8 set to manually installed.
gcc-4.8 is already the newest version.
gcc-4.8 set to manually installed.
git is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libboost1.55-all-dev : Depends: libboost1.55-dev but it is not going to be installed
                        Depends: libboost1.55-tools-dev
                        Depends: libboost-atomic1.55-dev but it is not going to be installed
                        Depends: libboost-chrono1.55-dev but it is not going to be installed
                        Depends: libboost-context1.55-dev but it is not going to be installed
                        Depends: libboost-coroutine1.55-dev but it is not going to be installed
                        Depends: libboost-date-time1.55-dev but it is not going to be installed
                        Depends: libboost-exception1.55-dev but it is not going to be installed
                        Depends: libboost-filesystem1.55-dev but it is not going to be installed
                        Depends: libboost-graph1.55-dev but it is not going to be installed
                        Depends: libboost-graph-parallel1.55-dev but it is not going to be installed
                        Depends: libboost-iostreams1.55-dev but it is not going to be installed
                        Depends: libboost-locale1.55-dev but it is not going to be installed
                        Depends: libboost-log1.55-dev but it is not going to be installed
                        Depends: libboost-math1.55-dev but it is not going to be installed
                        Depends: libboost-mpi1.55-dev but it is not going to be installed
                        Depends: libboost-mpi-python1.55-dev but it is not going to be installed
                        Depends: libboost-program-options1.55-dev but it is not going to be installed
                        Depends: libboost-python1.55-dev but it is not going to be installed
                        Depends: libboost-random1.55-dev but it is not going to be installed
                        Depends: libboost-regex1.55-dev but it is not going to be installed
                        Depends: libboost-serialization1.55-dev but it is not going to be installed
                        Depends: libboost-signals1.55-dev but it is not going to be installed
                        Depends: libboost-system1.55-dev but it is not going to be installed
                        Depends: libboost-test1.55-dev but it is not going to be installed
                        Depends: libboost-thread1.55-dev but it is not going to be installed
                        Depends: libboost-timer1.55-dev but it is not going to be installed
                        Depends: libboost-wave1.55-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Anyone an idea how to solve this?

EDIT: i had to install libboost1.55-dev first

But now i got this:

Quote
$ cd boolberry; make -j
mkdir -p build/release
cd build/release && cmake -D CMAKE_BUILD_TYPE=Release ../..
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   thread
--   date_time
--   chrono
--   regex
--   serialization
--   atomic
--   program_options
-- Found Git: /usr/bin/git
-- Configuring done
-- Generating done
-- Build files have been written to: /home/badass/boolberry/build/release
cd build/release && make
make[1]: Entering directory `/home/badass/boolberry/build/release'
make[2]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[  1%] [ 14%] [ 15%] make[3]: Leaving directory `/home/badass/boolberry/build/release'
Building CXX object src/CMakeFiles/common.dir/common/util.cpp.o
Built target upnpc-static
[ 27%] Building CXX object src/CMakeFiles/common.dir/common/base58.cpp.o
[ 27%] [ 33%] Built target crypto
Built target version
Built target crypto-tests
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
Scanning dependencies of target hash-tests
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 34%] make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 35%] make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 36%] [ 37%] Built target gtest
[ 38%] [ 39%] make[3]: Entering directory `/home/badass/boolberry/build/release'
Building CXX object src/CMakeFiles/currency_core.dir/currency_core/tx_pool.cpp.o
[ 40%] Building CXX object src/CMakeFiles/currency_core.dir/currency_core/currency_format_utils.cpp.o
Building CXX object src/CMakeFiles/rpc.dir/rpc/core_rpc_server.cpp.o
Building CXX object src/CMakeFiles/wallet.dir/wallet/wallet_rpc_server.cpp.o
Scanning dependencies of target gtest_main
Building CXX object tests/CMakeFiles/hash-tests.dir/hash/main.cpp.o
Building CXX object src/CMakeFiles/wallet.dir/wallet/wallet2.cpp.o
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 41%] Building CXX object tests/gtest/CMakeFiles/gtest_main.dir/src/gtest_main.cc.o
Linking CXX executable hash-tests
Linking CXX static library libgtest_main.a
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 41%] Built target gtest_main
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 41%] Built target hash-tests
Linking CXX static library libcommon.a
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 41%] Built target common
Linking CXX static library libcurrency_core.a
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 48%] Built target currency_core
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target connectivity_tool
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target simpleminer
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target core_proxy
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target coretests
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target difficulty-tests
Scanning dependencies of target net_load_tests_clt
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
Scanning dependencies of target hash-target-tests
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 49%] make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target net_load_tests_srv
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 50%] make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target performance_tests
make[3]: Leaving directory `/home/badass/boolberry/build/release'
Building CXX object tests/CMakeFiles/core_proxy.dir/core_proxy/core_proxy.cpp.o
[ 51%] [ 52%] make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 53%] make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 54%] Building CXX object src/CMakeFiles/connectivity_tool.dir/connectivity_tool/conn_tool.cpp.o
Building CXX object tests/CMakeFiles/difficulty-tests.dir/difficulty/difficulty.cpp.o
make[3]: Entering directory `/home/badass/boolberry/build/release'
Building CXX object src/CMakeFiles/simpleminer.dir/miner/simpleminer.cpp.o
[ 55%] Building CXX object tests/CMakeFiles/hash-target-tests.dir/hash-target.cpp.o
Building CXX object tests/CMakeFiles/net_load_tests_srv.dir/net_load_tests/srv.cpp.o
[ 56%] Building CXX object tests/CMakeFiles/net_load_tests_clt.dir/net_load_tests/clt.cpp.o
Building CXX object tests/CMakeFiles/performance_tests.dir/performance_tests/main.cpp.o
Linking CXX executable core_proxy
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 57%] [ 58%] [ 59%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/pruning_ring_signatures.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/double_spend.cpp.o
[ 60%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/block_reward.cpp.o
[ 61%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/block_validation.cpp.o
[ 62%] [ 63%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/tx_validation.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chain_switch_1.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/integer_overflow.cpp.o
[ 64%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chaingen_main.cpp.o
[ 65%] [ 66%] [ 67%] make[3]: Leaving directory `/home/badass/boolberry/build/release'
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chaingen001.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/mixin_attr.cpp.o
[ 67%] [ 68%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/ring_signature_1.cpp.o
Built target core_proxy
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/alias_tests.cpp.o
[ 69%] [ 70%] [ 71%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/get_random_outs.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/transaction_tests.cpp.o
[ 72%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chaingen.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chain_split_1.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [src/CMakeFiles/rpc.dir/rpc/core_rpc_server.cpp.o] Error 4
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[2]: *** [src/CMakeFiles/rpc.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chaingen001.cpp.o] Error 4
make[3]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [src/CMakeFiles/wallet.dir/wallet/wallet2.cpp.o] Error 4
make[3]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chaingen_main.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [tests/CMakeFiles/net_load_tests_clt.dir/net_load_tests/clt.cpp.o] Error 4
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[2]: *** [tests/CMakeFiles/net_load_tests_clt.dir/all] Error 2
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [tests/CMakeFiles/hash-target-tests.dir/hash-target.cpp.o] Error 4
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[2]: *** [tests/CMakeFiles/hash-target-tests.dir/all] Error 2
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chain_switch_1.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/block_reward.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chain_split_1.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [src/CMakeFiles/wallet.dir/wallet/wallet_rpc_server.cpp.o] Error 4
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[2]: *** [src/CMakeFiles/wallet.dir/all] Error 2
Linking CXX executable difficulty-tests
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chaingen.cpp.o] Error 4
Connection to 89.248.X.X closed by remote host.
Connection to 89.248.X.X closed.

It also shuts down my VPS all of a sudden....did it twice. Anyone has an idea?
full member
Activity: 127
Merit: 100
Again pool http://cncoin.farm/ not work.
I cant connect to this address stratum+tcp://bbr.cncoin.farm:8888
upd: when I write it, my miner connected to pool Smiley
hero member
Activity: 732
Merit: 500
Can someone share some experience with solo mining compared with pool? Thanks!

You are better off going solo. The difficulty is low and you won't get server disconnects.

All the pools are bad.
Has cncoin.farm been bad lately? I thought it was doing ok. Anyone else have any experiences good or bad?

Only reason not to do solo would be if there are a lot of orphans, but I don't think there are many orphans at all. You can register your own alias that way, too.

Speaking of which, thanks to those that have registered aliases at my pool. I'm just glad it got tested. Seems to work ok.

Edit: Of course the pool goes down right after I send this...

too low eff. for me at your pool and losing connection much times. only EU pools working fine here.
full member
Activity: 212
Merit: 100
Can someone share some experience with solo mining compared with pool? Thanks!

You are better off going solo. The difficulty is low and you won't get server disconnects.

All the pools are bad.
Has cncoin.farm been bad lately? I thought it was doing ok. Anyone else have any experiences good or bad?

Only reason not to do solo would be if there are a lot of orphans, but I don't think there are many orphans at all. You can register your own alias that way, too.

Speaking of which, thanks to those that have registered aliases at my pool. I'm just glad it got tested. Seems to work ok.

Edit: Of course the pool goes down right after I send this...
legendary
Activity: 3808
Merit: 1723
Can someone share some experience with solo mining compared with pool? Thanks!

You are better off going solo. The difficulty is low and you won't get server disconnects.

All the pools are bad.
hero member
Activity: 732
Merit: 500
Can someone share some experience with solo mining compared with pool? Thanks!
legendary
Activity: 896
Merit: 1001
Are you sure that's a BBR wallet address?  I plugged in one of my addresses in and it worked fine.  Create a new address and try it.  What's the -d switch for?  You should use a different pool and spread the hashrate. 

Or better yet solomine with MBK's open_cl miner:

https://github.com/mbkuperman/boolberry-opencl

Windows build:
https://github.com/mbkuperman/boolberry-opencl/releases


All works. Thx

Glad you got things resolved.
full member
Activity: 127
Merit: 100
Are you sure that's a BBR wallet address?  I plugged in one of my addresses in and it worked fine.  Create a new address and try it.  What's the -d switch for?  You should use a different pool and spread the hashrate. 

Or better yet solomine with MBK's open_cl miner:

https://github.com/mbkuperman/boolberry-opencl

Windows build:
https://github.com/mbkuperman/boolberry-opencl/releases


All works. Thx
legendary
Activity: 896
Merit: 1001
Today I tried to run the miner, and he there gave me an error and didn't work. Here's the line start:
Quote
minerd.exe -d 0 -a wildkeccak_ocl -o stratum+tcp://bbr.cncoin.farm:9999 -u 1BucJ63i8W3fJpgM7JHhq2euaJST5uR7XNvjpG4YmBhERzYiz9bdDx8QччciGJ8uGPLod7vgT9KCUQimx26xHEvFF1E74Tb -p U_2#8nMa0f$ -k http://cdn.cncoin.farm/scratchpad.bin -l scratchpad.bin
Here's the line start what could be the problem? Pool works.


Are you sure that's a BBR wallet address?  I plugged in one of my addresses in and it worked fine.  Create a new address and try it.  What's the -d switch for?  You should use a different pool and spread the hashrate. 

Or better yet solomine with MBK's open_cl miner:

https://github.com/mbkuperman/boolberry-opencl

Windows build:
https://github.com/mbkuperman/boolberry-opencl/releases

full member
Activity: 127
Merit: 100
Today I tried to run the miner, and he there gave me an error and didn't work. Here's the line start:
Quote
minerd.exe -d 0 -a wildkeccak_ocl -o stratum+tcp://bbr.cncoin.farm:9999 -u 1BucJ63i8W3fJpgM7JHhq2euaJST5uR7XNvjpG4YmBhERzYiz9bdDx8QччciGJ8uGPLod7vgT9KCUQimx26xHEvFF1E74Tb -p U_2#8nMa0f$ -k http://cdn.cncoin.farm/scratchpad.bin -l scratchpad.bin
Here's the line start what could be the problem? Pool works.
legendary
Activity: 1792
Merit: 1010
I'm fixing several issues in new version. It is almost ready, but one of the issues requires some time to debug.


nice to see new developer onboard ! and thank you
newbie
Activity: 39
Merit: 0
I'm fixing several issues in new version. It is almost ready, but one of the issues requires some time to debug.
hero member
Activity: 686
Merit: 500
Any updates from the dev team?

Thanks in advance!
legendary
Activity: 3808
Merit: 1723
Yes both of the pools for Boolberry are messed up.

Hard to calculate daily profit under these conditions because the pools keep disconnecting. And also the dropping price isn't helping.
sr. member
Activity: 450
Merit: 250
Something up with cncoin.farm?
legendary
Activity: 1792
Merit: 1010


Quote from: bitLeap link=topic=577267.msg9863944#msg9863944
Btw any real reason why the price for bbr still falling?
lack of interest mostly. an unfortunate trend in alt markets is that anything that isn't going up is usually going down; the volume only affecting the volatility of these trends.



Coinmarketcap is a sea of red today. Everything's crashing together with bitcoin. There are very few coins going up in price.

perfect time to accumulate actually I don't see this technology going anywhere it is here to stay

people might be selling BTC to re-purchase on super low that and also selling alt coins to "ready" BTC on triggers , it is a risky operation in my opinion I don't play this game but know that many do
hero member
Activity: 976
Merit: 646
Hey guys!

Boostrap nodes was offline for some time due to hoster's problems (nodes was restarted).
Now everything is fine!


Zoidberg
legendary
Activity: 826
Merit: 1002
amarha
For people who want full anonymity right down to the network level Teleport(network level anonymity) and BBR(unlinkable inputs and outputs) is the solution. And the only way to use those two technologies together is via SuperNET. So BBR is a critical piece of the privacy puzzle.

And SuperNET itself is a massive project to increase adoption of currencies. In fact ~$100k was just budgeted for marketing to start off 2015. BBR being a core part of SuperNET is a big deal. I myself am working on a SuperNET related project that will target real world use and I hope to be able to include BBR in my plans as well.

SuperNET intends to grow a large user base and as a result of that BBR should gain users as well since it is quite good itself.
i understand how BBR will be implemented in superNET; my (and i think others') question is "why hold onto BBR now?" - since it seems to me like the price of any individual constituent of superNET is irrelevant when they can change between different types. i suppose the price of something would depend entirely on its utility and use?

it's all very interesting and i look forward to its official release. but i just don't understand my part in it as a supporter of BBR.


Well the price will reflect the demand of BBR. If enough people are using it then the price should rise. To the end user the price will be irrelevant yes, but to people who invest in BBR anything that increases demand should be good. At this point it's pretty clear that the market is not pricing in any sort of future demand. Or at least very little future demand.

It's still going to take time to really increase adoption, but if you believe that there will be a lot of demand for privacy then BBR is probably one of the better choices one can make in terms of an investment. The technology is there, and if the demand is there then it's mostly going to be matter of packaging it in an easy to use way for people. Which is one of the main goals of SuperNET.
sr. member
Activity: 719
Merit: 250


Quote from: bitLeap link=topic=577267.msg9863944#msg9863944
Btw any real reason why the price for bbr still falling?
lack of interest mostly. an unfortunate trend in alt markets is that anything that isn't going up is usually going down; the volume only affecting the volatility of these trends.



Coinmarketcap is a sea of red today. Everything's crashing together with bitcoin. There are very few coins going up in price.
member
Activity: 117
Merit: 100
For people who want full anonymity right down to the network level Teleport(network level anonymity) and BBR(unlinkable inputs and outputs) is the solution. And the only way to use those two technologies together is via SuperNET. So BBR is a critical piece of the privacy puzzle.

And SuperNET itself is a massive project to increase adoption of currencies. In fact ~$100k was just budgeted for marketing to start off 2015. BBR being a core part of SuperNET is a big deal. I myself am working on a SuperNET related project that will target real world use and I hope to be able to include BBR in my plans as well.

SuperNET intends to grow a large user base and as a result of that BBR should gain users as well since it is quite good itself.
i understand how BBR will be implemented in superNET; my (and i think others') question is "why hold onto BBR now?" - since it seems to me like the price of any individual constituent of superNET is irrelevant when they can change between different types. i suppose the price of something would depend entirely on its utility and use?

it's all very interesting and i look forward to its official release. but i just don't understand my part in it as a supporter of BBR.

Quote from: bitLeap link=topic=577267.msg9863944#msg9863944
Btw any real reason why the price for bbr still falling?
lack of interest mostly. an unfortunate trend in alt markets is that anything that isn't going up is usually going down; the volume only affecting the volatility of these trends.

i was pretty amazed that my 1 BTC buy at .0001 was filled within 10 minutes of my putting it up yesterday. someone is selling at a heavy loss right now, since i doubt it's profitable to mine and dump at these prices...
Jump to: