Project is not going to change name.
We are boolberry and discussion is closed.
just wondering, what's the significance of the name? Boolean - is most simple and fundamental data type in computer scince. At the other hand it's equivalent of "bit". Berries - just because i'm sick of blabla-coin project names. |
|
|
|
btw. don't get why all the attention is at monero while boolberry is much faster and offers quite more things like a gui-wallet
must be promotional stuff or am i missing something?
I agree, BBR is currently better than XMR, but what can you do. Monero has a few big names behind that gives investors (speculators) more confidence + more developers + better name + few guys bashing BBR. If you follow the investors, they are more like P&Ders trying to pump their investment. Real investors don't hang out in troll boxes. So far the higher developer count has not translated into a better product. The name is a matter of opinion. The bashers only have FUD. the project is open minded for rebranding right? could we open a thread about the name again? would have some ideas  Project is not going to change name. We are boolberry and discussion is closed. |
|
|
|
Hi @crypto_zoidberg, there has been optimized updates for the cpuminer(stratum) lately, could you compile and update the miner for windows too?
I've talked with Wolfy, he said to me that windows build is not problem for him, so i expect he gonna make build in next hours. If not - i'll do it this night. |
|
|
|
|
Good News!
We have new build v0.2.0.31(5d85ebf) with very important change - difficulty now 128 bit, so we are not under risk of cumulative_difficulty overflow.
Also fixed bug with periodic crush of GUI (thanks to mrs_snow).
|
|
|
|
btw: build 0.2.0.27 must be updated! can you see red blinking text that says that you have to update it ? Strongly recommend you to update GUI to todays newcoming version!
Updated to build 0.2.0.28 I have a development proposal: Can you add the date in the recent transfer list? Yes, sure, it's in TODO for today (and remove timezone from transfers line). I want to release build with fixed bugs and new 128bit difficulty at first, so this build won't include GUI adjustments, and next for today i have a set of features for GUI, your proposal. |
|
|
|
For some time the GUI wallet exits unexpectedly. Now I've got an error message: snow@orion:~/boolberry/gui$ ./qt-boolb
terminate called after throwing an instance of 'tools::error::daemon_busy'
what(): daemon is busy
Abgebrochen (Speicherabzug geschrieben) self compiled version 0.2.0.27(7460089) Ubuntu 14.04 x64 Thank you for report, i think i found the reason of this bug and will include fix into today's forthcoming release. btw: build 0.2.0.27 must be updated! can you see red blinking text that says that you have to update it ? Strongly recommend you to update GUI to todays newcoming version! Zoidberg |
|
|
|
I've pushed notification since we had critical error for qt-boolb in builds before 28. So, to avoid this message you need to increase build number to 28. |
|
|
|
All pools I checked have 0 hashrate.. It seems BBR is mined only by people with lots of resources. With probability to mine for days until founding a block... there is no point trying extremepool.org address is http://boolberry.extremepool.org/ - it has 180kh/s and had found block 8 days ago... Frankly it seems BBR is mined only from few people with big resources. That alone explains why mid and low-power miners go away or don't even try it. Big fish eats all the food. We working on porting opencl into miner client for pools, i hope this helps. |
|
|
|
Hello dear friends! Want to announce that i've almost finished porting porting difficulty type in boolberry daemon from 64 bit to 128 bit. This is very important since BBR have completely different hashrate compared to CryptoNight hash, to avoid difficulty overflow(mostly cumulative_difficulty) was needed to use 128 bit difficulty type for all daemon operations. At first i want to say many thanks to jahrsg ( https://github.com/jahrsg, https://bitcointalk.org/index.php?action=profile;u=356516) to porting main functions and creating tests, that guarantee that this new versions working exactly the same as old one on 64-bit range. I would like to ask you to test it for one or two days before merge it into master branch. git clone
git checkout difficulty128
make -i I want to get some bugreports here or into email: support@boolberry.com or in bookberry. Good luck!! |
|
|
|
|
!!!! Critical update !!!!
Fixed bug in GUI Wallet! Please update GUI to v0.2.0.28(9fda647) !!!!!
|
|
|
|
I am trying to connect to extremepool but... seems I lack something simpleminer.exe --pool-addr=boolberry.extremepool.org:5555 --login BBR_Address --pass x --mining-threads 1
2014-Jul-21 12:27:49.606545 Connecting boolberry.extremepool.org:5555....
2014-Jul-21 12:27:49.824945 Connected boolberry.extremepool.org:5555 OK
2014-Jul-21 12:28:09.855380 Failed to invoke http request to /json_rpc
2014-Jul-21 12:28:09.855380 Failed to invoke login boolberry.extremepool.org:555
5, disconnect and sleep.... Also, any idea how to mine from different machine to same wallet? Will i need to have blockchain on that machine too :S Try solo mining please, simpleminer is not really effective way to mine at this moment. Cpuminer is effective but it is no supports GPU mining yet. |
|
|
|
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?
Nice poetry  You right, we looking for some PR for our project. Have someone to suggest ? |
|
|
|
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: $ ./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. $ 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: $ ./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. |
|
|
|
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. |
|
|
|
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. |
|
|
|
|
Good news!
I've uploaded new build (v0.2.0.27(7460089)) where fixed issue with not displayed transfers.
|
|
|
|
Stupid question.
If I am running the qt wallet and solo mining. Does the blocks go to the qt wallet or doe I still need to run the simple wallet to get the blocks?
Blocks goes to that address that you pointed at start_mining command. So it is no matter if you use qt wallet or simplewallet, it depends only of address. |
|
|
|
OK. I've just commented the line that caused the exception and updated the release. Now it exits fine. Sure, i'm looking at sources... btw: you also could check executables on https://www.virustotal.com/ to be sure if there are no malware. Today I merged last commits (about a week) from your master branch and now my boolbd.exe gives an exception upon exit (last log record - [SRV_MAIN]Node stopped). It was OK before that. Do you have a clue what commit could cause it? Have no idea..., hard to say without additional info, can you point the place where does it crushes ? Just run it under gdb or visual studio to catch... Also, sometime clean/full rebuild helps. Great Job! I've sent pm to you, please answer |
|
|
|
Sure, i'm looking at sources... btw: you also could check executables on https://www.virustotal.com/ to be sure if there are no malware. Today I merged last commits (about a week) from your master branch and now my boolbd.exe gives an exception upon exit (last log record - [SRV_MAIN]Node stopped). It was OK before that. Do you have a clue what commit could cause it? Have no idea..., hard to say without additional info, can you point the place where does it crushes ? Just run it under gdb or visual studio to catch... Also, sometime clean/full rebuild helps. |
|
|
|
Open source Boolberry OpenCL minerhttps://github.com/mbkuperman/boolberry-opencl.gitRead README.md for details and build instructions. Windows x64 executables: https://github.com/mbkuperman/boolberry-opencl/releases/download/v1.0/BoolberryOCL-20140719.zip2% developer donation (you can change or disable it in the configuration file) Solo version: boolbd.exe (best performance/reliability) Pool (JSON RPC) version: simpleminer.exe (please, use solo version if you can!) Personally, I think it doesn't make any sense to use pools while the block value is about $7. Just give enough time to the solo miner. Tested on AMD GPUs only! Expected performance: 6870, R270x - 500-600 khs 6970, R280X - 900-1000 khs OpenCL code is available under the terms of the GNU Public License version 3. Author: Mikhail Kuperman ( mbk.git@gmail.com) BBR donation address: 1EmWGnwhydr3S2vRWQbbefh1hgDKgMjdMGe43ZgdPhdARhNBRkUMuD4YzLA2nyYG8tg2HKCCBg4aDam JKypRQWW1Ca2kSV8 BTC donation address: 1Lns6UjL3sw77DJ5z1EKJZy6SnqriqvVGK can somebody from devs verify if thats not a virus etc? Sure, i'm looking at sources... btw: you also could check executables on https://www.virustotal.com/ to be sure if there are no malware. |
|
|
|
|
Show Posts
