Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released

Quote from: rbrunner7 on August 06, 2017, 03:13:51 PM

Quote from: clintar2 on July 07, 2017, 12:10:56 AM

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