I don't know where you or any others on here get the gall to claim I am involved in a pump and dump. Because I ask one question in this thread you are going to accuse me of that? For the record: I have never owned more than a few thousand bbr (NEVER), and I've never participated in private or public discussion of "pumping" any cryptocurrency. I know how to program Java, hence the name. Never once have I ever claimed to be an expert in C++. I pushed a few updates to the BBR RPC API because I was motivated by CURIOSITY to work on a cryptonote Java API. THIS WAS NEVER ABOUT THE MONEY FOR ME. You people are blame blame blame without any shred of evidence. Knock it off.

Hey Smooth,

I think a lot of what you have planned sounds great; what is your timetable for development? I see the github hasn't seen an update in ages.

That's a great idea. I can do that; thanks for the suggestion!

Bi-weekly update:

https://bitcointalk.org/index.php?topic=1611499.msg17120374#msg17120374

Boolberry Network Address December 8, 2016

Hello all: I am filling in for 1block for this week's bi-weekly update.

We are continuing to make progress on the Boolberry daemon. Much of the work on the RPC API is completed; this will allow continued progress on cooperating web services. Also, a large focus will soon shift towards completing the database conversion of the block chain. The goal is for this part of the project to be a major focus beginning in the middle of December. It is not currently known how long this conversion will take.

The past few weeks have also seen the reemergence of some notable Boolberry enthusiasts. Hopefully this contributes to a gradually reemerging community around the cryptonote coin; a vibrant community and working together will be crucial in order to make Boolberry truly successful.

This is likely occurring because the daemon only has two seed nodes to connect to by default. If these nodes are not online then your node doesn't know who to connect to the first time you run the daemon. Therefore a long term solution to this will be to change the hard-coded seed nodes in the code repository.

A short term solution for you and others would be to specify a seed node manually. This can be done by doing the following:

boolbd --seed-node 5.9.44.154:10101

This command tells your daemon to treat the bbr.mbkpool.info node as a seed node. As a result, your node will connect to it and download its list of active peers. I got this to overcome the error on my end so I hope it works for others as well.