I tried to compile the Boolberry source on Raspberry pi 2 Ubuntu Mate, but no succeed, the error is something about can't find libboost, while I am sure the libboost is already installed.
Anyone who has tried successfully compiled on raspbian care to share ?
I think it would be surely cool thing to run the Boolberry on Raspi.
Topic: [BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 148. (Read 1210749 times)
hooray for random large volume buys :^)
Thought this was dead. Dev still around?
The coin runs on it's own. It functions as it was intended to. I'm sure that if there was an issue crypto zoidberg would show up and take care of it. Cryptonote coins like all other cryptocurrencies are still struggling to find real world usage and a reason to exist.
hooray for random large volume buys :^)
Thought this was dead. Dev still around?
People come and go where the money is. There hasn't been any real money here for a while.
hooray for random large volume buys :^)
Thought this was dead. Dev still around?
hooray for random large volume buys :^)
Thought this was dead. Dev still around?
hooray for random large volume buys :^)
This coin is so deadly deadly dead. Not even a stuipd cat would eat that half rotten dead fish.
Great work Zoidy
Great work Zoidy
All Boolberry users should support this Monero Stack Exchange proposal:
https://area51.stackexchange.com/proposals/98617/monero?referrer=jCNrOlNEkxrmaNghFGZDsA2
Why? Because Stack Exchange will bring exposure to CryptoNote and a great resource for Boolberry related questions that will be considered ON TOPIC!
http://discuss.area51.stackexchange.com/questions/23731/are-questions-about-other-cryptonote-coins-on-topic
https://area51.stackexchange.com/proposals/98617/monero?referrer=jCNrOlNEkxrmaNghFGZDsA2
Why? Because Stack Exchange will bring exposure to CryptoNote and a great resource for Boolberry related questions that will be considered ON TOPIC!
http://discuss.area51.stackexchange.com/questions/23731/are-questions-about-other-cryptonote-coins-on-topic
Lets go zoidberg it is time for new stuff and getting bbr where belongs.
IMO this coin is pretty dead sadly...
tech works well enough. alts are all about hype and volume. maybe the new stuff zoidberg is adding will pique some interest, but don't expect to see much happening til that happens. 
IMO this coin is pretty dead sadly...
I was able to sync the GUI wallet with the blockchain and generate an address, however, after closing the wallet and reopening, it wouldn't connect to the network again. Only way I was able to view my wallet again was to delete the 3 .bin files and then redownload the entire chain again.
I am not quite sure what is causing this issue, its both with the daemon and GUI wallet, I have to repeat the same steps of deleting the 3 .bin files in order for either the daemon or the GUI wallet to connect.
Once those 3 .bin files are deleted the daemon or GUI wallet will connect right to the network and synchronize but then after the GUI is closed, those steps need repeated to connect to the network again. If those .bin files aren't deleted, they both will fail to connect.
In the steps I followed earlier, it mentioned to just delete the p2pstate and poolstate .bin files, however that doesn't work for me and I have to also delete the blockchain each time and as I mentioned, redownload the entire chain anytime I want to open and view my wallet.
I am not quite sure what is causing this issue, its both with the daemon and GUI wallet, I have to repeat the same steps of deleting the 3 .bin files in order for either the daemon or the GUI wallet to connect.
Once those 3 .bin files are deleted the daemon or GUI wallet will connect right to the network and synchronize but then after the GUI is closed, those steps need repeated to connect to the network again. If those .bin files aren't deleted, they both will fail to connect.
In the steps I followed earlier, it mentioned to just delete the p2pstate and poolstate .bin files, however that doesn't work for me and I have to also delete the blockchain each time and as I mentioned, redownload the entire chain anytime I want to open and view my wallet.
Have you issue the command "exit" or "save" in boolbd console before closing the wallet ?
That sure made a world of difference. Thanks
Big things to happen here soon 
Care to elaborate? Yours was the first post in this thread for the best part of a month.
Big things to happen here soon
I tried the miner, it run only couple of hours before crash. I have tried it several times and the result is same, crashed in some hours.
Here is the screenshot.
https://www.sendspace.com/file/335hzt
Hmm, darn. And you did a git pull for the latest? I've been running mine for days without problems... If you do a git checkout master and use that, does it work ok (without the -K option, though)?
Yesterday I run the master at pooltobe, no crash even there are many reconnect and relogin, but after lubuntu 14.04 software update, now I try again at cncoinfarm with keepalive using last pull, I hope it works stable.
Ps. The keepalive branch is stable, I have been mining for 5 days without crash. However the lubuntu 14.04 screen resolution must be keep default, setting screen DPI to 96x96 will make it crash after some hours.
Ok, thanks for the report!
I tried the miner, it run only couple of hours before crash. I have tried it several times and the result is same, crashed in some hours.
Here is the screenshot.
https://www.sendspace.com/file/335hzt
Hmm, darn. And you did a git pull for the latest? I've been running mine for days without problems... If you do a git checkout master and use that, does it work ok (without the -K option, though)?
Yesterday I run the master at pooltobe, no crash even there are many reconnect and relogin, but after lubuntu 14.04 software update, now I try again at cncoinfarm with keepalive using last pull, I hope it works stable.
Ps. The keepalive branch is stable, I have been mining for 5 days without crash. However the lubuntu 14.04 screen resolution must be keep default, setting screen DPI to 96x96 will make it crash after some hours.
I was able to sync the GUI wallet with the blockchain and generate an address, however, after closing the wallet and reopening, it wouldn't connect to the network again. Only way I was able to view my wallet again was to delete the 3 .bin files and then redownload the entire chain again.
I am not quite sure what is causing this issue, its both with the daemon and GUI wallet, I have to repeat the same steps of deleting the 3 .bin files in order for either the daemon or the GUI wallet to connect.
Once those 3 .bin files are deleted the daemon or GUI wallet will connect right to the network and synchronize but then after the GUI is closed, those steps need repeated to connect to the network again. If those .bin files aren't deleted, they both will fail to connect.
In the steps I followed earlier, it mentioned to just delete the p2pstate and poolstate .bin files, however that doesn't work for me and I have to also delete the blockchain each time and as I mentioned, redownload the entire chain anytime I want to open and view my wallet.
I am not quite sure what is causing this issue, its both with the daemon and GUI wallet, I have to repeat the same steps of deleting the 3 .bin files in order for either the daemon or the GUI wallet to connect.
Once those 3 .bin files are deleted the daemon or GUI wallet will connect right to the network and synchronize but then after the GUI is closed, those steps need repeated to connect to the network again. If those .bin files aren't deleted, they both will fail to connect.
In the steps I followed earlier, it mentioned to just delete the p2pstate and poolstate .bin files, however that doesn't work for me and I have to also delete the blockchain each time and as I mentioned, redownload the entire chain anytime I want to open and view my wallet.
Have you issue the command "exit" or "save" in boolbd console before closing the wallet ?
Don't worry, we're paying the jewish space lobster 1% of all coins ever generated, I'm sure he'll fix it soon 
I was able to sync the GUI wallet with the blockchain and generate an address, however, after closing the wallet and reopening, it wouldn't connect to the network again. Only way I was able to view my wallet again was to delete the 3 .bin files and then redownload the entire chain again.
I am not quite sure what is causing this issue, its both with the daemon and GUI wallet, I have to repeat the same steps of deleting the 3 .bin files in order for either the daemon or the GUI wallet to connect.
Once those 3 .bin files are deleted the daemon or GUI wallet will connect right to the network and synchronize but then after the GUI is closed, those steps need repeated to connect to the network again. If those .bin files aren't deleted, they both will fail to connect.
In the steps I followed earlier, it mentioned to just delete the p2pstate and poolstate .bin files, however that doesn't work for me and I have to also delete the blockchain each time and as I mentioned, redownload the entire chain anytime I want to open and view my wallet.
I am not quite sure what is causing this issue, its both with the daemon and GUI wallet, I have to repeat the same steps of deleting the 3 .bin files in order for either the daemon or the GUI wallet to connect.
Once those 3 .bin files are deleted the daemon or GUI wallet will connect right to the network and synchronize but then after the GUI is closed, those steps need repeated to connect to the network again. If those .bin files aren't deleted, they both will fail to connect.
In the steps I followed earlier, it mentioned to just delete the p2pstate and poolstate .bin files, however that doesn't work for me and I have to also delete the blockchain each time and as I mentioned, redownload the entire chain anytime I want to open and view my wallet.
deleted the blockchain.bin file.. Seems to be working now.
Code:
2016-Apr-28 19:47:59.921632 [P2P9]Connecting to 128.199.196.65:10101(white=1, last_seen: never)...
2016-Apr-28 19:48:01.746655 [P2P9]Connect failed to 128.199.196.65:10101
2016-Apr-28 19:48:01.751158 [P2P9]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:48:06.757277 [P2P9]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:48:06.760931 [P2P9]Connecting to 107.170.97.197:10101(white=1, last_seen: never)...
2016-Apr-28 19:48:06.944111 [P2P8]Fresh maintainers info recieved(timestamp: 1409856855)
2016-Apr-28 19:48:06.949451 [P2P8][107.170.97.197:10101 OUT] COMMAND_HANDSHAKE(AND CLOSE) INVOKED OK
2016-Apr-28 19:48:06.970970 [P2P9]Connecting to 46.72.189.197:10101(white=0, last_seen: d37.h10.m44.s28)...
2016-Apr-28 19:48:11.979006 [P2P9]Connect failed to 46.72.189.197:10101
2016-Apr-28 19:48:11.983012 [P2P9]Connecting to 46.246.47.132:10101(white=0, last_seen: d34.h14.m32.s35)...
2016-Apr-28 19:48:13.566339 [P2P9]Connect failed to 46.246.47.132:10101
2016-Apr-28 19:48:13.570844 [P2P9]Connecting to 91.155.234.25:10101(white=0, last_seen: d0.h0.m0.s57)...
2016-Apr-28 19:48:14.147749 [P2P3][91.155.234.25:10101 OUT]Sync data returned unknown top block: 1 -> 508706 [508705 blocks (706 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:48:14.156677 [P2P3][91.155.234.25:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:48:14.161141 [P2P9]Connecting to 81.39.124.195:10101(white=0, last_seen: d28.h5.m31.s44)...
2016-Apr-28 19:48:16.151964 [P2P7]CHECKPOINT PASSED FOR HEIGHT 1 <0d6f94ae7e565c6d90ee0087d2feaad4617cd3038c4f8853f26756a6b6d535f3>
2016-Apr-28 19:48:16.172444 [P2P7]CHECKPOINT PASSED FOR HEIGHT 100 <4a3783222d3f241bcfb8cec6803b5c5dbea73ddcd35c8f6f8b3320c90ad56c05>
2016-Apr-28 19:48:19.166938 [P2P9]Connect failed to 81.39.124.195:10101
2016-Apr-28 19:48:19.170817 [P2P9]Connecting to 128.204.214.119:10101(white=0, last_seen: d0.h0.m1.s5)...
2016-Apr-28 19:48:19.582859 [P2P7][128.204.214.119:10101 OUT]Sync data returned unknown top block: 801 -> 508706 [507905 blocks (705 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:48:19.591993 [P2P7][128.204.214.119:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:48:19.595996 [P2P9]Connecting to 46.246.62.147:10101(white=0, last_seen: d34.h1.m13.s1)...
2016-Apr-28 19:48:19.873843 [P2P1]CHECKPOINT PASSED FOR HEIGHT 1000 <60200d3f6405a2a338c47aae868128395856d6982dff114b98b04f3187e37fa0>
2016-Apr-28 19:48:22.530236 [P2P5]CHECKPOINT PASSED FOR HEIGHT 2000 <66e8cd560748e41a3aeb4d0dc9a071c5d5145929aa6dc0df98baac5b43e584a6>
2016-Apr-28 19:48:24.601820 [P2P9]Connect failed to 46.246.62.147:10101
2016-Apr-28 19:48:24.605823 [P2P9]Connecting to 122.54.174.141:10101(white=0, last_seen: d0.h11.m37.s4)...
2016-Apr-28 19:48:26.095144 [P2P0]CHECKPOINT PASSED FOR HEIGHT 3000 <0a24811b48634fdd205a7fc9cc594b8fc485ec886be84d546bbbe0a2ff6662e3>
2016-Apr-28 19:48:29.611783 [P2P9]Connect failed to 122.54.174.141:10101
2016-Apr-28 19:48:29.615286 [P2P9]Connecting to 146.185.143.37:10101(white=0, last_seen: d26.h10.m56.s33)...
2016-Apr-28 19:48:33.905349 [P2P1]CHECKPOINT PASSED FOR HEIGHT 5000 <01a1a9fc533196000143b918ee5a47a5c49d2a19cad812d04e3a16fdcee97fbb>
2016-Apr-28 19:48:34.620937 [P2P9]Connect failed to 146.185.143.37:10101
2016-Apr-28 19:48:34.625440 [P2P9]Connecting to 46.72.253.73:10101(white=0, last_seen: d12.h8.m41.s47)...
2016-Apr-28 19:48:39.631282 [P2P9]Connect failed to 46.72.253.73:10101
2016-Apr-28 19:48:39.634781 [P2P9]Connecting to 59.120.166.36:10101(white=0, last_seen: d0.h0.m0.s40)...
2016-Apr-28 19:48:40.593071 [P2P2][59.120.166.36:10101 OUT]Sync data returned unknown top block: 7104 -> 508706 [501603 blocks (696 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:48:40.601077 [P2P2][59.120.166.36:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:48:40.605079 [P2P9]Connecting to 66.228.33.249:10101(white=0, last_seen: d0.h5.m40.s32)...
2016-Apr-28 19:48:40.829770 [P2P7][66.228.33.249:10101 OUT]Sync data returned unknown top block: 7201 -> 508706 [501505 blocks (696 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:48:40.837377 [P2P7][66.228.33.249:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:48:40.841381 [P2P9]Connecting to 186.92.188.140:10101(white=0, last_seen: d35.h21.m9.s58)...
2016-Apr-28 19:48:45.849696 [P2P9]Connect failed to 186.92.188.140:10101
2016-Apr-28 19:48:45.853197 [P2P9]Connecting to 106.185.46.152:10101(white=0, last_seen: d0.h1.m9.s11)...
2016-Apr-28 19:48:46.476507 [P2P7][106.185.46.152:10101 OUT]Sync data returned unknown top block: 9801 -> 508706 [498905 blocks (692 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:48:46.484314 [P2P7][106.185.46.152:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:48:46.487815 [P2P9]Connecting to 176.9.147.178:7180(white=0, last_seen: d0.h0.m0.s27)...
2016-Apr-28 19:48:46.955824 [P2P6][176.9.147.178:7180 OUT]Sync data returned unknown top block: 10001 -> 508706 [498705 blocks (692 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:48:46.963333 [P2P6][176.9.147.178:7180 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:48:46.967837 [P2P9]Connecting to 46.72.242.120:10101(white=0, last_seen: d44.h10.m4.s5)...
2016-Apr-28 19:48:51.974255 [P2P9]Connect failed to 46.72.242.120:10101
2016-Apr-28 19:48:51.977757 [P2P9]Connecting to 188.226.215.102:10101(white=0, last_seen: d0.h5.m41.s31)...
2016-Apr-28 19:48:52.399132 [P2P4][188.226.215.102:10101 OUT]Sync data returned unknown top block: 12001 -> 508706 [496705 blocks (689 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:48:52.411145 [P2P4][188.226.215.102:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:48:52.417648 [P2P9]Connecting to 5.9.38.137:10101(white=0, last_seen: d0.h0.m0.s33)...
2016-Apr-28 19:48:52.871936 [P2P5][5.9.38.137:10101 OUT]Sync data returned unknown top block: 12001 -> 508706 [496705 blocks (689 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:48:52.880124 [P2P5][5.9.38.137:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
Jump to: