Topic: [BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 427. (Read 1210753 times)
Up Up!
No 32-bit version for windows..?
Boolbery needs some market support, in Bittrex there are 1-2 buys per several hours....
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://bitcointalksearch.org/topic/m.7212956
Have a look at how Qora user set up a Qora asset today:
https://bitcointalksearch.org/topic/m.7212956
boolberry is moving in the right direction 
- good to see
funny that there is so little liquidity in the markets
- good to seefunny that there is so little liquidity in the markets
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.
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... 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..)
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.
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.
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.
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.
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.
you did a great job on fastrie (riecoin,) used it for a while with success, now attacking cryptonight coins.. thanks for all your contributions! (not to mention cudaminer work.. and speed up you have achieved.. that was phenomenal...)
cpuminer-multi cannot mine Boolberry yet.
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.
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.
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.
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.
will this beat performance wise cpuminer-multi ? thanks
https://github.com/LucasJones/cpuminer-multi
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.
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.
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.
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.
great work! i will test shortly.
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.
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.
You can help these pools to find blocks
but the difficulty level is crazy high.. I do however LOVE what you did with network graphshttp://boolberry.com/state.html
sub-word berry is cool too, I don't think raspberry will mind.. maybe it can be connected somehow (client for raspberry)
too bad on the difficulty level, impossible to mine on my rig.. and it is quite powerful rig (CPU wise) AMD's low watts lots of power
it is not just me.. block finding problem can be bad for the coin unfortunately...
"Does anyone know what is up with #Boolberry ? Was mining for 12 hours with no blocks found. Back to mining bla bla"
https://twitter.com/intent/retweet?tweet_id=474309773416869888
You can help these pools to find blocks
I don't know how yo all are doin' , Difficulty: 66640425354, Block Found: Never pretty funny
Which pool do you mean? pretty funnyI don't know how yo all are doin' , Difficulty: 66640425354, Block Found: Never pretty funny
Which pool do you mean? pretty funnyJump to: