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

[b4h4mu7]

If someone from the community wants to setup and maintain a block explorer, I'll compensate them with a bounty. 500XBB seems reasonable.

Thanks for the interest everyone. Bounty is being claimed. We should have an explorer up soon.

[tljenson]

Does anybody want some free Boolberry? I'm trying to clean out my wallets on Bittrex and can't sell it. I only have 0.98910000, but would be happy to send it to you. Just leave you Boolberry address.

[cherry11800]

What is the new development for this coin?

[mmo4me.2016]

Dear all
I see Boolberry on Waves plateform!
It great for Boolberry
http://www.wavesgo.com/assets.html?3DH9QD9kzoUiDzHaFRos58WRW7zvg54ZTgUAcz7tSi1K

[crypjunkie]

If someone from the community wants to setup and maintain a block explorer, I'll compensate them with a bounty. 500XBB seems reasonable.

Thanks for the interest everyone. Bounty is being claimed. We should have an explorer up soon.

Can you contact me plz.

[crypjunkie]

both chainradar and minergate are down again

this shit again? are there any actual diagnostics on the network?

what are your daemons saying

1Block ya gonna help out again? You did say if the liquidity was there you would come back! If b4h4mu7 is serious about technical developments and has an active developer helping out we can bring some additional help and benefits for everyone.

[clintar2]

I have my block explorer up and running at http://explorer.mining.blue/en. It's still in development so don't trust it to be giving accurate info, but I figure it's something at least for now. Please help by letting me know of anything that seems off so I can fix it. It's based on code written for Karbowanec and I've attempted to make equivalent rpc calls in boolberry to get it working here, but unsure about how I've translated some of that.

[b4h4mu7]

I have my block explorer up and running at http://explorer.mining.blue. It's still in development so don't trust it to be giving accurate info, but I figure it's something at least for now. Please help by letting me know of anything that seems off so I can fix it. It's based on code written for Karbowanec and I've attempted to make equivalent rpc calls in boolberry to get it working here, but unsure about how I've translated some of that.

[cherry11800]

Dear all
I see Boolberry on Waves plateform!
It great for Boolberry
http://www.wavesgo.com/assets.html?3DH9QD9kzoUiDzHaFRos58WRW7zvg54ZTgUAcz7tSi1K

Thank you for this information,Do you know what information is there for DEV? :)After Delist on polo ,The community is not very active

[1blockologist]

both chainradar and minergate are down again

this shit again? are there any actual diagnostics on the network?

what are your daemons saying

1Block ya gonna help out again? You did say if the liquidity was there you would come back! If b4h4mu7 is serious about technical developments and has an active developer helping out we can bring some additional help and benefits for everyone.

exactly, its not out of the question! for now I'll just provide infrastructure where I can

[clintar2]

Ok, just an update on the explorer http://explorer.mining.blue/en. I got most things working now. I removed things we don't keep track of for this coin. Again, let me know of anything that looks to be wrong., but It should be pretty useful now. Have a great day!

[rbrunner7]

I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)

It seems to run alright. I could sync the blockchain in less than a day, using the 5.9.44.154:10101 seed node that I found on the boolberry subreddit. I get new blocks and new transactions, and everything like current height is in agreement with the new blockchain explorer that went up yesterday (great work, by the way, congrats). Finally, other nodes can connect to my daemon; currently I have 4 incoming connections.

But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.

What is happening here? Boolberry nodes running outdated software versions getting rejected from my (hopefully) up-to-date daemon? Daemons of another Cryptonote currency trying to connect to my Boolberry node? Or other programs altogether that just happen to use the same ports as Boolberry?

Or still something not quite right with my new node?

[clintar2]

I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)

It seems to run alright. I could sync the blockchain in less than a day, using the 5.9.44.154:10101 seed node that I found on the boolberry subreddit. I get new blocks and new transactions, and everything like current height is in agreement with the new blockchain explorer that went up yesterday (great work, by the way, congrats). Finally, other nodes can connect to my daemon; currently I have 4 incoming connections.

But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.

What is happening here? Boolberry nodes running outdated software versions getting rejected from my (hopefully) up-to-date daemon? Daemons of another Cryptonote currency trying to connect to my Boolberry node? Or other programs altogether that just happen to use the same ports as Boolberry?

Or still something not quite right with my new node?

Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now.

[rbrunner7]

I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)

...

But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.

...

Or still something not quite right with my new node?

Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now.

Well, thanks for the fast repo update! I will have time to compile a new version from it and test probably this coming weekend.

But anyway: Yesterday I was running the daemon in a quick-and-dirty way on the non-standard port 50001, because of problems with port forwarding / NAT; today I switched to the standard 10101 port, and presto, no more "wrong network agent connected" messages. Maybe there is still a small bug somewhere that triggers when using --p2p-bind-port ...

By the way, is this forum here the right place to discuss such rather technical matters and problems? Maybe better to open issues on your GitHub repo for such things? Would be no problem for me.

[clintar2]

I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)

...

But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.

...

Or still something not quite right with my new node?

Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now.

Well, thanks for the fast repo update! I will have time to compile a new version from it and test probably this coming weekend.

But anyway: Yesterday I was running the daemon in a quick-and-dirty way on the non-standard port 50001, because of problems with port forwarding / NAT; today I switched to the standard 10101 port, and presto, no more "wrong network agent connected" messages. Maybe there is still a small bug somewhere that triggers when using --p2p-bind-port ...

By the way, is this forum here the right place to discuss such rather technical matters and problems? Maybe better to open issues on your GitHub repo for such things? Would be no problem for me.

No, here is fine.

[b3da]

I have my block explorer up and running at http://explorer.mining.blue/en.
...

its great to have working block explorer again. thank you!

[rbrunner7]

If anyone wants to test out my latest db code, I have it at https://github.com/clintar/boolberry/tree/lmdb_scratch

you can get the branch with

Code:

git clone -b lmdb_scratch https://github.com/clintar/boolberry.git

then

Code:

mkdir -p build/release; cd build/release
cmake -DDATABASE=lmdb ../..
make -j4 daemon

should compile it, at least in linux. Let me know if it compiles or not at least!

I tried this branch. It compiled without problems. The produced binary started and created an initial db file of about 1 GB.

There is no file conversion yet from the "old" .bin format to lmdb format, so it wants to sync the blockchain from start, even with a blockchain file within reach, right? At least that was what it did on my system.

Sync immediately ran into problems however. I had repeated messages as follows:

Code:

2017-Aug-06 13:37:10.273809 [P2P3][193.70.85.9:10101 OUT]Block verification failed, dropping connection

These messages come from currency_protocol_handler.inl, line #377 (as checked out from GitHub today):

Code:

        if(bvc.m_verifivation_failed)
        {
          LOG_PRINT_CCONTEXT_L0("Block verification failed, dropping connection");
          m_p2p->drop_connection(context);
          m_p2p->add_ip_fail(context.m_remote_ip);
          return 1;
        }

Sync stuck forever at block 3 with repeated messages like this one:

Code:

2017-Aug-06 13:37:09.362602 [P2P7][193.70.85.9:10101 OUT]Sync data returned unknown top block: 3 -> 840955 [840952 blocks (1167 days) behind]

Is it supposed to be able to sync with "conventional" Boolberry nodes?

[clintar2]

If anyone wants to test out my latest db code, I have it at https://github.com/clintar/boolberry/tree/lmdb_scratch

you can get the branch with

Code:

git clone -b lmdb_scratch https://github.com/clintar/boolberry.git

then

Code:

mkdir -p build/release; cd build/release
cmake -DDATABASE=lmdb ../..
make -j4 daemon

should compile it, at least in linux. Let me know if it compiles or not at least!

I tried this branch. It compiled without problems. The produced binary started and created an initial db file of about 1 GB.

There is no file conversion yet from the "old" .bin format to lmdb format, so it wants to sync the blockchain from start, even with a blockchain file within reach, right? At least that was what it did on my system.

Sync immediately ran into problems however. I had repeated messages as follows:

Code:

2017-Aug-06 13:37:10.273809 [P2P3][193.70.85.9:10101 OUT]Block verification failed, dropping connection

These messages come from currency_protocol_handler.inl, line #377 (as checked out from GitHub today):

Code:

        if(bvc.m_verifivation_failed)
        {
          LOG_PRINT_CCONTEXT_L0("Block verification failed, dropping connection");
          m_p2p->drop_connection(context);
          m_p2p->add_ip_fail(context.m_remote_ip);
          return 1;
        }

Sync stuck forever at block 3 with repeated messages like this one:

Code:

2017-Aug-06 13:37:09.362602 [P2P7][193.70.85.9:10101 OUT]Sync data returned unknown top block: 3 -> 840955 [840952 blocks (1167 days) behind]

Is it supposed to be able to sync with "conventional" Boolberry nodes?

It should, but it's not in a good state. I have some fixes, but it will fall if there is an alt chain. I haven't had a lot of time to debug the problems. You should probably create a different folder for it to keep it's files in and use --data-dir= to point it to that folder. It should at least sync, but don't trust it for anything yet. Hopefully this week I can look more into it.

BTW, did everyone notice the scratchpad got too large again for current miner software? Time to increase those buffers

[Molenta]

Any chance to reveal what can be done in miner to accept bigger scratchpad would be honored or can give me address for 10BBR, am a small miner

[clintar2]

Any chance to reveal what can be done in miner to accept bigger scratchpad would be honored or can give me address for 10BBR, am a small miner

Usually if you are compiling from source, the git repo will get updates, so you can just run

Code:

git pull 

to get the changes and run make again, but if you are just using a binary, you'll have to wait for someone to compile a new one. Which miner are you using?