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

[minerjoen]

2014-Jul-20 11:43:45.429697 [P2P1][54.83.92.170:10101 OUT] SYNCHRONIZED OK
2014-Jul-20 11:43:46.337749 [P2P4][202.198.97.236:10101 OUT] COMMAND_HANDSHAKE I
NVOKED OK
2014-Jul-20 11:43:46.341749 [P2P9]Connecting to 2.179.176.194:10101(white=0, las
t_seen: d0.h0.m0.s5)...
2014-Jul-20 11:43:47.329806 [P2P8][2.179.176.194:10101 OUT] COMMAND_HANDSHAKE IN
VOKED OK
2014-Jul-20 11:43:47.333806 [P2P9]Connecting to 195.12.60.154:10101(white=0, las
t_seen: d0.h0.m0.s4)...
2014-Jul-20 11:43:47.428811 [P2P2][195.12.60.154:10101 OUT] COMMAND_HANDSHAKE IN
VOKED OK

for the rest nothing happen? He also say: mining has started with 1 thread, good luck!

i've never had so much problems with start mining, but boolberry want to let my head explode?

I will try 1 hour more, if not i just move to another coin, because this is waste of time (except, it looks like that..)

From problems with ??downloading scratch file?? (wtf i never had to download an scratch file for start mining,), to wallet problems, to mining problems, with pool problems, i only have problems with this coin?

[1715110096]

1715110096

[mbk]

Use

Code:

--mining-threads=5

command line parameter. Moreover read my previous message on multi GPU configurations.

Open source Boolberry OpenCL miner
https://github.com/mbkuperman/boolberry-opencl.git

I'm so new with BBR and I try to SOLO with this Boolberry OpenCL miner.
Does this seem to be OK with my 750Tis?
It seems like only miner0 is working, other 5 cards are not.

[FortuneNVirtue]

Use

Code:

--mining-threads=5

command line parameter. Moreover read my previous message on multi GPU configurations.

Open source Boolberry OpenCL miner
https://github.com/mbkuperman/boolberry-opencl.git

I'm so new with BBR and I try to SOLO with this Boolberry OpenCL miner.
Does this seem to be OK with my 750Tis?
It seems like only miner0 is working, other 5 cards are not.

Actually I already set "--mining-threads=6"

Code:

 "thread_delay": 2000

But your above setting solved the problem, right now all of my 6 gpus (750Ti) are working fine.Thank you very much.

[mbk]

Here is simple calculation what to expect with solo mining:

Current difficulty from http://boolberry.com/state.html - 200GH
It means you need 200*1024 seconds to find a block with 1Mhs mining power (280X).
There are 86400 seconds in a day so expect to find a block on average every 200000/86000 = 2 days 8 hours.
It will take 4 days 16 hours for a 500khs card (6870, 750Ti) and so on.

Don't be afraid to mine few days without any result. I've implemented low difficulty shares (like you do with a pool) so you can check everything works as expected. If you get efficiency about 100% the calculation above is correct. Anyway you cannot get anything for sure with random process like mining. So don't blame me if you get nothing in a week. 

[PVmining]

Code:

 "thread_delay": 2000

But your above setting solved the problem, right now all of my 6 gpus (750Ti) are working fine.Thank you very much.

...how performs the 750ti?

[FortuneNVirtue]

Code:

 "thread_delay": 2000

But your above setting solved the problem, right now all of my 6 gpus (750Ti) are working fine.Thank you very much.

...how performs the 750ti?

470K..Palit 750Ti Dual Stormx
370K..MSI 750Ti Gaming

[mmmaybe]

Code:

 "thread_delay": 2000

But your above setting solved the problem, right now all of my 6 gpus (750Ti) are working fine.Thank you very much.

...how performs the 750ti?

470K..Palit 750Ti Dual Stormx
370K..MSI 750Ti Gaming

Seems about correct, getting ~2,7M on a 6-card 750Ti rig

[sonoIO]

As i'm discovering wonders of the Cryptoland, i was paying with gpg and following crossed my mind. If one doesn't have dedicated wallet box, but rather has the wallet key on multiple boxes (security of which is such that one box is significantly more secure than others), i suppose that it would be better that w.bbr.keys file may never be written to a disk unencrypted (except at the time of its generation - on most secure box). I understand that it is encrypted with its password, but my question is if it is worth to have another layer of encryption. (encapsulation?)

Let's say that one, after generation, encrypts w.bbr.keys with e.g.

Code:

$ gpg -c --cipher-algo AES256 --symmetric w.bbr.keys

with password different from the wallet password itself.
Then on other boxes the simplewallet will return the following, after both passwords are entered:

Code:

$ ./simplewallet --wallet-file $(gpg --decrypt --quiet w.bbr.keys.gpg)
Boolberry wallet v0.2.0.26(d560235)
password: *********************************
A��x�()*��WssB���hs.keys"t: file not found "7܄��|K�U#��i܄USxP���?��G9��j"(����]P�w�E!|er��

But, earlier i noticed that w.bbr.keys file is needed only during the start of the simplewallet, it can be removed afterwards and the wallet will operate normally.

Crypto_Zoidberg, is it's possible to have such functionality of the simplewallet or it is too much pain in the back for small benefit? BTC doesn't have this problem as there ppl are supposed to use a lot of addresses.

[crypto_zoidberg]

2014-Jul-20 11:43:45.429697 [P2P1][54.83.92.170:10101 OUT] SYNCHRONIZED OK
2014-Jul-20 11:43:46.337749 [P2P4][202.198.97.236:10101 OUT] COMMAND_HANDSHAKE I
NVOKED OK
2014-Jul-20 11:43:46.341749 [P2P9]Connecting to 2.179.176.194:10101(white=0, las
t_seen: d0.h0.m0.s5)...
2014-Jul-20 11:43:47.329806 [P2P8][2.179.176.194:10101 OUT] COMMAND_HANDSHAKE IN
VOKED OK
2014-Jul-20 11:43:47.333806 [P2P9]Connecting to 195.12.60.154:10101(white=0, las
t_seen: d0.h0.m0.s4)...
2014-Jul-20 11:43:47.428811 [P2P2][195.12.60.154:10101 OUT] COMMAND_HANDSHAKE IN
VOKED OK

for the rest nothing happen? He also say: mining has started with 1 thread, good luck!

i've never had so much problems with start mining, but boolberry want to let my head explode?

I will try 1 hour more, if not i just move to another coin, because this is waste of time (except, it looks like that..)

From problems with ??downloading scratch file?? (wtf i never had to download an scratch file for start mining,), to wallet problems, to mining problems, with pool problems, i only have problems with this coin?

Dear minerjoen!
Let me know what problem do you have with starting mining, what exect problems do you have with wallet and let me help you and improve this project to avoid this problems in future.

As i could see from your post you started bollberry daemon and started mining there - this means that you started solo mining, that is actually is not very effective with one-two computers(difficulty is pretty high).
To start pool mining you just need to download minerd from boolberry website and follow instructions, scratcad file will downloaded automatically.

[crypto_zoidberg]

Here is simple calculation what to expect with solo mining:

Current difficulty from http://boolberry.com/state.html - 200GH
It means you need 200*1024 seconds to find a block with 1Mhs mining power (280X).
There are 86400 seconds in a day so expect to find a block on average every 200000/86000 = 2 days 8 hours.
It will take 4 days 16 hours for a 500khs card (6870, 750Ti) and so on.

Don't be afraid to mine few days without any result. I've implemented low difficulty shares (like you do with a pool) so you can check everything works as expected. If you get efficiency about 100% the calculation above is correct. Anyway you cannot get anything for sure with random process like mining. So don't blame me if you get nothing in a week. 

I think we need to enable this working in stratum client, i see two different approachs:
1. port  this code to cpuminer-multi
2. port stratum code from bytecoin's simpleminer and forget minerd as a nightmare

Anyway, this technology must be in pool client. I want to notice that current boolberry simpleminer version is not working with last stratum pools.

[crypto_zoidberg]

Hi sonoIO.
You can use as much encryption layer as you want, but i'm not sure what you going to do with that command line:

Code:

$ ./simplewallet --wallet-file $(gpg --decrypt --quiet w.bbr.keys.gpg)

What you actually did is passed as y key's file name parameter a binary output form pgp pipe.
Just store this output to other file, smth like this:

gpg --decrypt --quiet w.bbr.keys.gpg > decrypted.bbr.keys
and then
 ./simplewallet --wallet-file=decrypted.bbr.keys

i may be wrong in syntax since i'm writing from ipad. So let me know, if this what you wanted?

As i'm discovering wonders of the Cryptoland, i was paying with gpg and following crossed my mind. If one doesn't have dedicated wallet box, but rather has the wallet key on multiple boxes (security of which is such that one box is significantly more secure than others), i suppose that it would be better that w.bbr.keys file may never be written to a disk unencrypted (except at the time of its generation - on most secure box). I understand that it is encrypted with its password, but my question is if it is worth to have another layer of encryption. (encapsulation?)

Let's say that one, after generation, encrypts w.bbr.keys with e.g.

Code:

$ gpg -c --cipher-algo AES256 --symmetric w.bbr.keys

with password different from the wallet password itself.
Then on other boxes the simplewallet will return the following, after both passwords are entered:

Code:

$ ./simplewallet --wallet-file $(gpg --decrypt --quiet w.bbr.keys.gpg)
Boolberry wallet v0.2.0.26(d560235)
password: *********************************
A��x�()*��WssB���hs.keys"t: file not found "7܄��|K�U#��i܄USxP���?��G9��j"(����]P�w�E!|er��

But, earlier i noticed that w.bbr.keys file is needed only during the start of the simplewallet, it can be removed afterwards and the wallet will operate normally.

Crypto_Zoidberg, is it's possible to have such functionality of the simplewallet or it is too much pain in the back for small benefit? BTC doesn't have this problem as there ppl are supposed to use a lot of addresses.

[sonoIO]

Hi sonoIO.
You can use as much encryption layer as you want, but i'm not sure what you going to do with that command line:

Code:

$ ./simplewallet --wallet-file $(gpg --decrypt --quiet w.bbr.keys.gpg)

What you actually did is passed as y key's file name parameter a binary output form pgp pipe.
Just store this output to other file, smth like this:

gpg --decrypt --quiet w.bbr.keys.gpg > decrypted.bbr.keys
and then
 ./simplewallet --wallet-file=decrypted.bbr.keys

i may be wrong in syntax since i'm writing from ipad. So let me know, if this what you wanted?

It's exactly what i wanted but without having decrypted.bbr.keys stored on disk at anytime. I'm not sure that it even has benefit as decrypted.bbr.keys are locked with the password of the wallet, maybe just for people that use week passwords as then if someone steels w.bbr.keys.gpg he would have to break two passwords instead of one. And i was hoping that then decrypted.bbr.keys could be piped from hardware key of some sort in the future instead from pgp. Sorry for the noob questions

EDIT: Answer to myself I could have keys on USB and start wallet from there, if w.bbr.keys would have distinct directory from w.bbr wallet file, and take out USB after wallet starts.

[otila]

It's exactly what i wanted but without having decrypted.bbr.keys stored on disk at anytime.

Sounds like you want full-disk encryption.  I have that kind of setup, using LUKS in Linux.  More layers of encryption means more risks for forgetting password, and using the same password for all of the layers isn't going to help.

Or you can put decrypted .keys file at /run/user/$(id -u) and make a symlink from ~/.boolb/ to it, after disabling swap (if you are not using encrypted swap)..

[sonoIO]

It's exactly what i wanted but without having decrypted.bbr.keys stored on disk at anytime.

Sounds like you want full-disk encryption.  I have that kind of setup, using LUKS in Linux.  More layers of encryption means more risks for forgetting password, and using the same password for all of the layers isn't going to help.

Or you can put decrypted .keys file at /run/user/$(id -u) and make a symlink from ~/.boolb/ to it, after disabling swap (if you are not using encrypted swap)..

Tnx for the hint. I was thinking of times when average user will be very inconsiderate if he is putting keys on encrypted or non-encripted partition, so having them on e.g. USB stick would get them less exposed during time - and these are keys that one shouldn't change often.
Atm, w.bbr is reconstructed at the directory at which w.bbr.keys are, regardless of $PWD or directory at which simplewallet is. Would be convenient at least to have w.bbr directory separated from w.bbr.keys directory, as i tried and wallet runs very happily if it sees w.bbr.keys only at the start.

[windblow11]

never do solo mining before, if I stop the card for a while(eg. electricity cut off). When I restart, am I losing all the previous work?

[sonoIO]

never do solo mining before, if I stop the card for a while(eg. electricity cut off). When I restart, am I losing all the previous work?

Its statistics. E.g. if you find 5 blocks in 1 day, than you probably wouldn't find another whole month But on the longer run, you cannot cheat it, it is the time that you've been mining that it counts

[windblow11]

never do solo mining before, if I stop the card for a while(eg. electricity cut off). When I restart, am I losing all the previous work?

Its statistics. If you e.g. find 5 blocks in 1 day, than you probably wouldn't find another whole month But on the longer run, you cannot cheat it, it is the time that you've been mining that it counts

still a little confused.
1. at present,because of the hot days, I usually shut down my machine when I was at home and turn them on when I'm off, let's say 12hours/12hours, is this mean on the long run i'll get half compare to let the machine run 24 hours/day without stop
2. I got 3 machine, which will be better,pointing the 3 machine to one wallet adress or 3 different adresses,   or just the same

[sonoIO]

1. at present,because of the hot days, I usually shut down my machine when I was at home and turn them on when I'm off, let's say 12hours/12hours, is this mean on the long run i'll get half compare to let the machine run 24 hours/day without stop

It would be so if difficulty would not change. If it grows, you'll get less then 50% as your time-average of the mining difficulty would be higher. Yep, no time to waste

2. I got 3 machine, which will be better,pointing the 3 machine to one wallet adress or 3 different adresses,   or just the same

Just the same

[windblow11]

1. at present,because of the hot days, I usually shut down my machine when I was at home and turn them on when I'm off, let's say 12hours/12hours, is this mean on the long run i'll get half compare to let the machine run 24 hours/day without stop

It would be so if difficulty would not change. If it grows, you'll get less then 50% as your time average of mining difficulty would be higher. Yep, no time to waste

2. I got 3 machine, which will be better,pointing the 3 machine to one wallet adress or 3 different adresses,   or just the same

Which ever you find better

now seems clear, thanx

[Zer0Sum]

Man, this whole thread is about GPU mining esoterics...
Hash power is probably the least of BBR's problems.

You have a better coin and network than Monero...
The tx size issue seems under control unlike Monero...
But BBR has now collapsed by 50% relative to XMR and sits at a 7:1 ratio.

You REALLY need to get a journalism type =  a writer...
To spend 10-20 hours/week writing promotional material for BBR...
And send it off regularily to the Alt Coin press.

Doesn't your Ivory Tower university have a Journalism Faculty?