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

[q327K091]

will this beat performance wise cpuminer-multi ? thanks

https://github.com/LucasJones/cpuminer-multi

cpuminer-multi cannot mine Boolberry yet.

Once it can, it will probably be better.  There are a few things left to fix in simpleminer to improve efficiency -- mostly about the % time spent mining vs waiting for work from the network.  Some of this can be fixed with the current protocol and some wants something like Stratum support.

They're a bit more work than what I did already - I'll try to fix some of them next weekend or so if time permits and lucasjones doesn't add boolberry to cpuminer-multi first.

great! it is fun, this coin (design/name) is fun.. not even would mine it for a profit.. as said.. Raspberry PI or Beagle, blinking lights and all  thanks again...

[1713897472]

1713897472

[1713897472]

1713897472

[dga]

will this beat performance wise cpuminer-multi ? thanks

https://github.com/LucasJones/cpuminer-multi

cpuminer-multi cannot mine Boolberry yet.

unfortunately not finding blocks was not because of that.. used straight out minerd, I love your coin.. such a shame on the difficulty (people must have rented CPU farms..)

There is no minerd that can handle boolberry... you have to either mine from the daemon (boolbd) or using simpleminer.

And re difficulty - it's finally gotten to a stable point, and it's not that bad.  A good i7 CPU can get something like 300kh/sec now, solo, which should produce:

   300000 * 86400 / 69481323602 = 0.37 = one block every three days, or about 6 BBR per day on average.  That's .003 BTC/day, which is an amazing return for a CPU coin. It's also the same return as mining XMR, approximately, which suggests that it's still hard enough to mine cryptonote that  less technically-clueful people are not doing so.

[nakaone]

boolberry is moving in the right direction - good to see

funny that there is so little liquidity in the markets

[devphp]

Boolberries should trade on the NXT decentralized Asset Exchange. This will create more demand for them from NXTers. BBR/NXT is about 4.25 right now. Somebody trustworthy in the Boolberry community and who cares that the price of boolberries is sliding needs to create a Boolberry asset and sell it, redeemable to real boolberries on demand.

Have a look at how Qora user set up a Qora asset today:
https://bitcointalk.org/index.php?topic=522102.msg7212956#msg7212956

[aikklond]

Boolbery needs some market support, in Bittrex there are 1-2 buys per several hours....

[Kn_os]

No 32-bit version for windows..?

[crypto_zoidberg]

I've added preliminary multithreading support to simpleminer.  It's annoying launching all of those processes manually.

I've just now sent it as a pull request to crypto_zoidberg, but if anyone wants to test it, this is my test repository:

https://github.com/dave-andersen/boolberry

(For the paranoid, the only files that are changed are simpleminer.h and simpleminer.cpp, so you can copy those into your own checkout from the official release).

Note:  That repository is going to go away if and when the changes are merged.

This is now merged into the main boolberry source, please update.

As a warning, it's still suboptimal.  It spends too much time waiting for jobs from the servers. The starting diff for the pools will need to be adjusted for multithreaded clients, at minimum.  Better would, of course, be adding stratum support and a better miner architecture, but this is a start in the right direction.

a)  If you use it, be sure to connect to the highest starting difficulty port available on your pool.

b)  Latency is important.  Make sure you find a pool that responds fast to your job requests!  Look at the log output and see the time between "Getting next job" and the report of starting work (either job didn't change or applying scratchpad diff).

c)  The new arg is --mining-threads #

Testing comments appreciated.  This is alpha-quality -- I've run it on my own machine but that's it.

from bbr.extremehash.com:

Last Share Submitted: less than a minute ago
 Hash Rate: 256.71 KH/sec
 Total Hashes Submitted: 182280000

that's running 8 threads on an i7-4770.  It's still slower than solo mining, but it's getting better.

dga, thank you for this update!
New simpleminer uploaded to web: http://boolberry.com/downloads.html

Good "luck"!

[joewills]

Up  Up!

[eddywise]

Great,we have the GUI now
next,I think should be the GPU miner

[aloney]

what happend??  over more than an hour, not even one block was found on the network??

[BoscoMurray]

I have a few of these:

2014-Jun-10 07:18:20.634615 [P2P6]Blockchain stored OK.
2014-Jun-10 08:11:32.679787 [miner 7]Found block for difficulty: 79798370751
2014-Jun-10 08:11:32.683788 [miner 7]Block with id: <9e634e9cc3677301977e7fc114f2353bb1b9f341d72b214612b031b16cf40d48>
have not enough proof of work: <b4aa8012fb75a1d48646d64278afc3a0f7c7c83bc4e4e179479ff9c5a85063b7>
nexpected difficulty: 79798370751
2014-Jun-10 08:11:32.698789 [miner 7]ERROR ..\..\src\currency_core\currency_core.cpp:384[currency::core::handle_block_found]mined block failed verification

Not enough proof? Anything I can do to prevent this in the future?

[dga]

I have a few of these:

2014-Jun-10 07:18:20.634615 [P2P6]Blockchain stored OK.
2014-Jun-10 08:11:32.679787 [miner 7]Found block for difficulty: 79798370751
2014-Jun-10 08:11:32.683788 [miner 7]Block with id: <9e634e9cc3677301977e7fc114f2353bb1b9f341d72b214612b031b16cf40d48>
have not enough proof of work: <b4aa8012fb75a1d48646d64278afc3a0f7c7c83bc4e4e179479ff9c5a85063b7>
nexpected difficulty: 79798370751
2014-Jun-10 08:11:32.698789 [miner 7]ERROR ..\..\src\currency_core\currency_core.cpp:384[currency::core::handle_block_found]mined block failed verification

Not enough proof? Anything I can do to prevent this in the future?

I think there's a bug - I've been seeing this during some of the big "no block for an hour" things as well.  My hypothesis is that it's related to the block timestamp getting thrown off by a miner with a bad clock, but I'll try to investigate more in the morning if nobody else figures it out before then.

[crypto_zoidberg]

I have a few of these:

2014-Jun-10 07:18:20.634615 [P2P6]Blockchain stored OK.
2014-Jun-10 08:11:32.679787 [miner 7]Found block for difficulty: 79798370751
2014-Jun-10 08:11:32.683788 [miner 7]Block with id: <9e634e9cc3677301977e7fc114f2353bb1b9f341d72b214612b031b16cf40d48>
have not enough proof of work: <b4aa8012fb75a1d48646d64278afc3a0f7c7c83bc4e4e179479ff9c5a85063b7>
nexpected difficulty: 79798370751
2014-Jun-10 08:11:32.698789 [miner 7]ERROR ..\..\src\currency_core\currency_core.cpp:384[currency::core::handle_block_found]mined block failed verification

Not enough proof? Anything I can do to prevent this in the future?

Can you send full log file, or at least about last 100 screens. I'll try to figure out what happend.
btw: at the moment when blocks stopped to appear you can also see connections count decreased.
http://boolberry.com/munin/localdomain/localhost.localdomain/incoming_connections_count.html

[crypto_zoidberg]

I have a few of these:

2014-Jun-10 07:18:20.634615 [P2P6]Blockchain stored OK.
2014-Jun-10 08:11:32.679787 [miner 7]Found block for difficulty: 79798370751
2014-Jun-10 08:11:32.683788 [miner 7]Block with id: <9e634e9cc3677301977e7fc114f2353bb1b9f341d72b214612b031b16cf40d48>
have not enough proof of work: <b4aa8012fb75a1d48646d64278afc3a0f7c7c83bc4e4e179479ff9c5a85063b7>
nexpected difficulty: 79798370751
2014-Jun-10 08:11:32.698789 [miner 7]ERROR ..\..\src\currency_core\currency_core.cpp:384[currency::core::handle_block_found]mined block failed verification

Not enough proof? Anything I can do to prevent this in the future?

I think there's a bug - I've been seeing this during some of the big "no block for an hour" things as well.  My hypothesis is that it's related to the block timestamp getting thrown off by a miner with a bad clock, but I'll try to investigate more in the morning if nobody else figures it out before then.

I guess timestamp is not related, since expected difficulty is seems right.
Probably miner have a bug in reorganize when alternative chain is loaded. I'll do hot fix today that reloads scratchpad from blockchain in case of such errors with mined blocks.

[dga]

I have a few of these:

2014-Jun-10 07:18:20.634615 [P2P6]Blockchain stored OK.
2014-Jun-10 08:11:32.679787 [miner 7]Found block for difficulty: 79798370751
2014-Jun-10 08:11:32.683788 [miner 7]Block with id: <9e634e9cc3677301977e7fc114f2353bb1b9f341d72b214612b031b16cf40d48>
have not enough proof of work: <b4aa8012fb75a1d48646d64278afc3a0f7c7c83bc4e4e179479ff9c5a85063b7>
nexpected difficulty: 79798370751
2014-Jun-10 08:11:32.698789 [miner 7]ERROR ..\..\src\currency_core\currency_core.cpp:384[currency::core::handle_block_found]mined block failed verification

Not enough proof? Anything I can do to prevent this in the future?

Can you send full log file, or at least about last 100 screens. I'll try to figure out what happend.
btw: at the moment when blocks stopped to appear you can also see connections count decreased.
http://boolberry.com/munin/localdomain/localhost.localdomain/incoming_connections_count.html

A bit more logging info from my computer, which also had one last night:

2014-Jun-10 00:58:03.741695 [P2P1][sock 66] ip denied 117.131.169.12, shutdowning connection
2014-Jun-10 01:31:34.736434 [P2P3][85.25.196.210:10101 OUT] SYNCHRONIZED OK
2014-Jun-10 01:39:53.998850 [P2P6]ERROR /home/dga/coin/bool/shared/boolberry/trunk/contrib/epee/include/net/lev
in_protocol_handler_async.h:429[bool epee::levin::async_protocol_handler<t_connection_context>::handle_recv(con
st void*, size_t) [with t_connection_context = nodetool::p2p_connection_context_t<currency::currency_connection
_context>; size_t = long unsigned int]][222.223.122.5:52394 INC]Signature mismatch, connection will be closed
2014-Jun-10 01:43:06.791363 [P2P4]ERROR /home/dga/coin/bool/shared/boolberry/trunk/src/currency_core/tx_pool.cp
p:70[bool currency::tx_memory_pool::add_tx(const currency::transaction&, const crypto::hash&, size_t, currency:
:tx_verification_context&, bool)]Transaction with id= <fc7a87b05621362bcb3bf35597a953934227bc39f81d4a6a28cca450
bedb3104> used already spent key images
2014-Jun-10 01:43:06.791416 [P2P4]Transaction verification failed: <fc7a87b05621362bcb3bf35597a953934227bc39f81d4a6a28cca450bedb3104>
2014-Jun-10 01:43:06.791442 [P2P4][221.0.76.119:53601 INC]Tx verification failed, dropping connection
2014-Jun-10 01:58:05.595791 [P2P7][sock 59] ip denied 117.131.169.12, shutdowning connection
2014-Jun-10 02:58:32.387880 [P2P5][sock 49] ip denied 117.131.169.12, shutdowning connection
2014-Jun-10 03:03:07.173040 [P2P9]Connecting to 117.218.46.97:10101(white=0, last_seen: d0.h18.m45.s50)...
2014-Jun-10 03:03:08.217350 [P2P3][117.218.46.97:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-10 03:08:48.386494 [miner 0]Found block for difficulty: 79798370751
2014-Jun-10 03:08:48.386729 [miner 0]Block with id: <ff1f5e5490f53e98a5e635cc8b295ea40f6ad0220642b91a48d7306b78d9ba44>
have not enough proof of work: <d769c737a1ae7caa5e6a0d444992c355f473f18e098a56aada10ac2266fe93be>
nexpected difficulty: 79798370751
2014-Jun-10 03:08:48.400420 [miner 0]ERROR /home/dga/coin/bool/shared/boolberry/trunk/src/currency_core/currency_core.cpp:394[virtual bool currency::core::handle_block_found(currency::block&)]mined block failed verification

[cubydu]

With last updated simpleminer I get strange picture.
Sometimes simpleminer can't get new job for a long time. Until the network found new block
Pool runs on server with 24 threads and has enough resources.

Code:

2014-Jun-10 15:23:18.289738 Job didn't change
2014-Jun-10 15:23:26.201698 Share found: nonce=10771210 for job=351806463976390, diff: 3350000
, PoW:<d9ddba8289f45dbc810c79d114c9a64baf0235085d630bbb1604119186000000>, height:16546, submitting...
2014-Jun-10 15:23:26.243949 Share submitted successfully!
2014-Jun-10 15:23:26.243991 Getting next job...
2014-Jun-10 15:23:26.282002 Job didn't change
2014-Jun-10 15:23:31.322204 Share found: nonce=13224449 for job=351806463976390, diff: 3350000
, PoW:<ecbb756c7a455398ad9ab263b85f3e38035d24a810c68b45aedf717d08000000>, height:16546, submitting...
2014-Jun-10 15:23:31.363280 Share submitted successfully!
2014-Jun-10 15:23:31.363339 Getting next job...
2014-Jun-10 15:23:31.402001 Job didn't change
2014-Jun-10 15:23:51.431627 Getting next job...
2014-Jun-10 15:23:51.470557 Job didn't change
2014-Jun-10 15:24:11.581892 Getting next job...
2014-Jun-10 15:24:11.619042 Job didn't change
2014-Jun-10 15:24:31.723488 Getting next job...
2014-Jun-10 15:24:31.763493 Job didn't change
2014-Jun-10 15:24:51.967757 Getting next job...
2014-Jun-10 15:24:52.007851 Job didn't change
2014-Jun-10 15:25:12.029291 Getting next job...
2014-Jun-10 15:25:12.068339 Job didn't change
2014-Jun-10 15:25:32.271406 Getting next job...
2014-Jun-10 15:25:32.308764 Job didn't change
2014-Jun-10 15:25:52.462629 Getting next job...
2014-Jun-10 15:25:52.501255 Job didn't change
2014-Jun-10 15:26:12.638873 Getting next job...
2014-Jun-10 15:26:12.677568 Job didn't change
2014-Jun-10 15:26:12.638873 Getting next job...
2014-Jun-10 15:26:12.677568 Job didn't change
2014-Jun-10 15:26:32.714673 Getting next job...
2014-Jun-10 15:26:32.756398 Job didn't change
2014-Jun-10 15:26:52.765889 Getting next job...
2014-Jun-10 15:26:52.806491 Job didn't change
2014-Jun-10 15:27:12.889515 Getting next job...
2014-Jun-10 15:27:12.926968 Job didn't change
2014-Jun-10 15:27:33.138448 Getting next job...
2014-Jun-10 15:27:41.544436 Numbers of blocks added to scratchpad: 1
2014-Jun-10 15:27:46.205116 Share found: nonce=2259201 for job=926625466300174, diff: 3350000
, PoW:<d04d25aab4181777f0b9593ab1d9099c31f7cd845e109ba5462de12be9010000>, height:16546, submitting...
2014-Jun-10 15:27:46.207270 Share submitted successfully!
2014-Jun-10 15:27:46.207330 Getting next job...
2014-Jun-10 15:27:46.247430 Job didn't change

[dga]

With last updated simpleminer I get strange picture.
Sometimes simpleminer can't get new job for a long time. Until the network found new block
Pool runs on server with 24 threads and has enough resources.

Thank you - this might be a bug I hadn't spotted.  I'm not entirely sure if it's the same thing,  I've submitted a pull request for a fix, but if you want to rebuild for yourself, this is the patch:

Code:

--- a/src/miner/simpleminer.cpp
+++ b/src/miner/simpleminer.cpp
@@ -235,6 +235,9 @@ namespace mining
          threads.push_back(boost::thread(&simpleminer::worker_thread, this, start_nonce, nonce_offset, &results[i]
          nonce_offset += attempts_per_loop;
        }
+       (*reinterpret_cast<uint64_t*>(&m_job.blob[1])) = (start_nonce + nonce_offset);
+       
+
        BOOST_FOREACH(boost::thread& th, threads)
        {
          th.join();
@@ -281,6 +284,8 @@ namespace mining
              }
              LOG_PRINT_GREEN("Share submitted successfully!", LOG_LEVEL_0);
              new_job_needed = true;
+             (*reinterpret_cast<uint64_t*>(&m_job.blob[1])) = (start_nonce + nonce_offset);
+
              break;
            }
          }

[crypto_zoidberg]

With last updated simpleminer I get strange picture.
Sometimes simpleminer can't get new job for a long time. Until the network found new block
Pool runs on server with 24 threads and has enough resources.

Thank you - this might be a bug I hadn't spotted.  I'm not entirely sure if it's the same thing,  I've submitted a pull request for a fix, but if you want to rebuild for yourself, this is the patch:

Code:

--- a/src/miner/simpleminer.cpp
+++ b/src/miner/simpleminer.cpp
@@ -235,6 +235,9 @@ namespace mining
          threads.push_back(boost::thread(&simpleminer::worker_thread, this, start_nonce, nonce_offset, &results[i]
          nonce_offset += attempts_per_loop;
        }
+       (*reinterpret_cast<uint64_t*>(&m_job.blob[1])) = (start_nonce + nonce_offset);
+       
+
        BOOST_FOREACH(boost::thread& th, threads)
        {
          th.join();
@@ -281,6 +284,8 @@ namespace mining
              }
              LOG_PRINT_GREEN("Share submitted successfully!", LOG_LEVEL_0);
              new_job_needed = true;
+             (*reinterpret_cast<uint64_t*>(&m_job.blob[1])) = (start_nonce + nonce_offset);
+
              break;
            }
          }

Merged, thank you.

[cubydu]

With last updated simpleminer I get strange picture.
Sometimes simpleminer can't get new job for a long time. Until the network found new block
Pool runs on server with 24 threads and has enough resources.

Thank you - this might be a bug I hadn't spotted.  I'm not entirely sure if it's the same thing,  I've submitted a pull request for a fix, but if you want to rebuild for yourself, this is the patch:

Code:

--- a/src/miner/simpleminer.cpp
+++ b/src/miner/simpleminer.cpp
@@ -235,6 +235,9 @@ namespace mining
          threads.push_back(boost::thread(&simpleminer::worker_thread, this, start_nonce, nonce_offset, &results[i]
          nonce_offset += attempts_per_loop;
        }
+       (*reinterpret_cast<uint64_t*>(&m_job.blob[1])) = (start_nonce + nonce_offset);
+       
+
        BOOST_FOREACH(boost::thread& th, threads)
        {
          th.join();
@@ -281,6 +284,8 @@ namespace mining
              }
              LOG_PRINT_GREEN("Share submitted successfully!", LOG_LEVEL_0);
              new_job_needed = true;
+             (*reinterpret_cast<uint64_t*>(&m_job.blob[1])) = (start_nonce + nonce_offset);
+
              break;
            }
          }

Thanks!
Yes, it is seems.
I'm testing  simpleminer 15 minutes.

[btc-mike]

With last updated simpleminer I get strange picture.
Sometimes simpleminer can't get new job for a long time. Until the network found new block
Pool runs on server with 24 threads and has enough resources.

Thank you - this might be a bug I hadn't spotted.  I'm not entirely sure if it's the same thing,  I've submitted a pull request for a fix, but if you want to rebuild for yourself, this is the patch:

Code:

--- a/src/miner/simpleminer.cpp
+++ b/src/miner/simpleminer.cpp
@@ -235,6 +235,9 @@ namespace mining
          threads.push_back(boost::thread(&simpleminer::worker_thread, this, start_nonce, nonce_offset, &results[i]
          nonce_offset += attempts_per_loop;
        }
+       (*reinterpret_cast<uint64_t*>(&m_job.blob[1])) = (start_nonce + nonce_offset);
+       
+
        BOOST_FOREACH(boost::thread& th, threads)
        {
          th.join();
@@ -281,6 +284,8 @@ namespace mining
              }
              LOG_PRINT_GREEN("Share submitted successfully!", LOG_LEVEL_0);
              new_job_needed = true;
+             (*reinterpret_cast<uint64_t*>(&m_job.blob[1])) = (start_nonce + nonce_offset);
+
              break;
            }
          }

I am testing to see if this resolves the error.