Latest wallet additions are Booltiful ! 
Keep up the good work.
Keep up the good work.
Don't get too attached to the name BitcoinFX
Topic: [BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 336. (Read 1210752 times)
August 15, 2014, 07:39:42 PM
Don't get too attached to the name BitcoinFX
August 15, 2014, 07:26:09 PM
Latest wallet additions are Booltiful !
Keep up the good work.
Keep up the good work.
August 15, 2014, 03:42:22 PM
Built qt-wallet using new source. For anyone running into problem building with Qt 5.3 (Qt5Gui_EGL_LIBRARY-NOTFOUND), please install package libegl1-mesa-dev http://qt-project.org/forums/viewthread/44605
zoidberg, there are some minor changes needed to make the linux build script better https://github.com/cryptozoidberg/boolberry/blob/master/utils/build_script_linux.sh
Also thanks for the tip received 
zoidberg, there are some minor changes needed to make the linux build script better https://github.com/cryptozoidberg/boolberry/blob/master/utils/build_script_linux.sh
Also thanks for the tip
received 
August 15, 2014, 10:47:45 AM
Good news!
We have new release 0.2.0.32(b91e9ab) with some improvements, mostly on GUI:
1. Implemented recent transfers history. Now after reopening your wallet you see your recent transfers, even with addresses that you used to transfer (or alias if address was registered).
Notice: This will start work from new build only, transfers that was made in older GUI version won't be seen. Also, if you gonna lost your wallet data file (some_wallet.bbr) recent transfers recipient addresses will be lost.
2. Implemented unconfirmed transaction state. Now, when you sent your transaction, you could see it as "unconfirmed" in recent transfers list:
Even is you close your wallet, and reopen it again, unconfirmed transfer won't be lost - so now you cold track your transaction confirmation.
Also made a lot of cosmetic improvement on appearance based on Bitcrea design adjustments.
Wellcome to try new version: http://boolberry.com/downloads.html
We have new release 0.2.0.32(b91e9ab) with some improvements, mostly on GUI:
1. Implemented recent transfers history. Now after reopening your wallet you see your recent transfers, even with addresses that you used to transfer (or alias if address was registered).
Notice: This will start work from new build only, transfers that was made in older GUI version won't be seen. Also, if you gonna lost your wallet data file (some_wallet.bbr) recent transfers recipient addresses will be lost.
2. Implemented unconfirmed transaction state. Now, when you sent your transaction, you could see it as "unconfirmed" in recent transfers list:
Even is you close your wallet, and reopen it again, unconfirmed transfer won't be lost - so now you cold track your transaction confirmation.
Also made a lot of cosmetic improvement on appearance based on Bitcrea design adjustments.
Wellcome to try new version: http://boolberry.com/downloads.html
August 15, 2014, 06:19:16 AM
It looks like your pool is sending updates now but they are about 8 seconds late. The miner works with wrong data, gets boo and reconnects if it finds a share. It considerably decreases mining efficiency. The pool I setup from the repository send updates in less then 100ms but it looks there is other bug anyway. Shares submitted right after the block/scratchpad update are rejected by the test pool. The pool_warn.log is:
Looks like the pool validates the share with the old scratchpad.
P.S. Checked the source - that's the case. Pool's scratchpad is updated through getFullScratchpad RPC call. It takes 3 seconds on my system. At the same time miner's scratchpad updated instantly by ADDENDUM in new block data. So valid shares are rejected by the pool if sent in less then 3 seconds after the new block.
Code:
Bad hash from miner [email protected]
scratchpadHeight.height=63856, job.height=63858
P.S. Checked the source - that's the case. Pool's scratchpad is updated through getFullScratchpad RPC call. It takes 3 seconds on my system. At the same time miner's scratchpad updated instantly by ADDENDUM in new block data. So valid shares are rejected by the pool if sent in less then 3 seconds after the new block.
Still the same problems. I setup a pool from your repository https://github.com/clintar/node-cryptonote-pool in virtualbox and it works perfectly. Moreover with blockRefreshInterval set to 100 it should give the performance close to solo miner and cpu load would be still very low.
Hmm, pool should using the same code. Block refresh was set to 1000, though. I better check my config against that in the repoIt's still the same. The pool doesn't send neither block nor scratchpad update when the new block arrives. On high difficulty performance is very poor.
Ok, got it now. It was a bug in the pool code that kept track of whether the connected port was stratum/tcp or http. Been a long standing bug I guess. Glad to finally fix that. Pool should be doing much better now! Thank you for helping me test it out!
August 15, 2014, 05:33:44 AM
Connected to bbr.farm (54.255.165.99) port 5555 seems to be dead for last few days.. 
Feckers changed the scratchpad location..grrr
August 15, 2014, 04:37:52 AM
Mining issues is killing the coin..
what issues?
August 15, 2014, 03:58:38 AM
Mining issues is killing the coin..
August 15, 2014, 03:17:38 AM
2014-Aug-15 15:06:25.035440 [RPC1]Failed to store scratchpad, error: basic_ios::clear
rpc store scatchpad failed,what can i do.
rpc return:
{ status: 'BUSY' }
resolved
rpc store scatchpad failed,what can i do.
rpc return:
{ status: 'BUSY' }
resolved
August 14, 2014, 11:40:55 PM
Connected to bbr.farm (54.255.165.99) port 5555 seems to be dead for last few days..
August 14, 2014, 06:04:18 PM
Still the same problems. I setup a pool from your repository https://github.com/clintar/node-cryptonote-pool in virtualbox and it works perfectly. Moreover with blockRefreshInterval set to 100 it should give the performance close to solo miner and cpu load would be still very low.
Hmm, pool should using the same code. Block refresh was set to 1000, though. I better check my config against that in the repo It's still the same. The pool doesn't send neither block nor scratchpad update when the new block arrives. On high difficulty performance is very poor.
Ok, got it now. It was a bug in the pool code that kept track of whether the connected port was stratum/tcp or http. Been a long standing bug I guess. Glad to finally fix that. Pool should be doing much better now! Thank you for helping me test it out! August 14, 2014, 05:26:33 PM
Still the same problems. I setup a pool from your repository https://github.com/clintar/node-cryptonote-pool in virtualbox and it works perfectly. Moreover with blockRefreshInterval set to 100 it should give the performance close to solo miner and cpu load would be still very low.
It's still the same. The pool doesn't send neither block nor scratchpad update when the new block arrives. On high difficulty performance is very poor.
Ok, got it now. It was a bug in the pool code that kept track of whether the connected port was stratum/tcp or http. Been a long standing bug I guess. Glad to finally fix that. Pool should be doing much better now! Thank you for helping me test it out! August 14, 2014, 05:10:48 PM
There are some issues with disconnects on different pools - every 20-40 seconds i get
I use GPU stratum miner, latest one - 1.0.1
Code:
[2014-08-14 23:55:56.143] Re-login, disconnecting...
[2014-08-14 23:55:56.144] Re-connect... and relogin...
I use GPU stratum miner, latest one - 1.0.1
August 14, 2014, 11:23:56 AM
It's still the same. The pool doesn't send neither block nor scratchpad update when the new block arrives. On high difficulty performance is very poor.
Ok, got it now. It was a bug in the pool code that kept track of whether the connected port was stratum/tcp or http. Been a long standing bug I guess. Glad to finally fix that. Pool should be doing much better now! Thank you for helping me test it out! August 14, 2014, 06:56:25 AM
OpenCL stratum miner
Windows x64 binary release is compatible with older CPUs now
https://github.com/mbkuperman/cpuminer-multi-opencl/releases
Windows x64 binary release is compatible with older CPUs now
https://github.com/mbkuperman/cpuminer-multi-opencl/releases
August 14, 2014, 06:06:22 AM
It's still the same. The pool doesn't send neither block nor scratchpad update when the new block arrives. On high difficulty performance is very poor.
I watched daemon and pool miner side by side. New block doesn't force anything on the stratum miner. It calculates hashes for the last job until it finds a share and the pool rejects it. It could take a lot of time. Miner reconnects, gets scratchpad updates and new job and it works fine again. Stratum makes no sense this way.
Can you test if my server is doing better now? Looked ok to me, but I couldn't test much and I have to go. Thanks!To pool owners:
Pool difficulties are too low for OpenCL stratum miner. Increase it at to 5M and 10M for multi-gpu configurations.
Check your pool sends scratchpad update messages in time. I tested 2 pools - bbr.farm sends it, cncoin.farm doesn't. It's inefficient without instant scratchpad updates.
I'll look into it. I don't get why var diff doesn't work with stratum cpuminer. It works with the opencl simpleminer...Pool difficulties are too low for OpenCL stratum miner. Increase it at to 5M and 10M for multi-gpu configurations.
Check your pool sends scratchpad update messages in time. I tested 2 pools - bbr.farm sends it, cncoin.farm doesn't. It's inefficient without instant scratchpad updates.
August 14, 2014, 05:55:08 AM
OpenCL stratum miner
https://github.com/mbkuperman/cpuminer-multi-opencl
Windows x64 build
https://github.com/mbkuperman/cpuminer-multi-opencl/releases
To mine on all available GPUs:
OpenCL specific options:
To mine on 2nd GPU only and to set higher intensity:
To mine on CPU (algorithm from original fork):
Discussion thread
https://bitcointalksearch.org/topic/m.8339439
https://github.com/mbkuperman/cpuminer-multi-opencl
Windows x64 build
https://github.com/mbkuperman/cpuminer-multi-opencl/releases
To mine on all available GPUs:
Code:
minerd.exe -a wildkeccak_ocl -o stratum+tcp://bbr.farm:7777 -u 1EmWGnwhydr3S2vRWQbbefh1hgDKgMjdMGe43ZgdPhdARhNBRkUMuD4YzLA2nyYG8tg2HKCCBg4aDamJKypRQWW1Ca2kSV8 -p X -l scratchpad.bin -k http://bbr.farm/download/scratchpad.bin
OpenCL specific options:
Code:
-d N - start OpenCL device to use (default: 0)
-i N - OpenCL work intensity (default: 18)
To mine on 2nd GPU only and to set higher intensity:
Code:
minerd.exe -a wildkeccak_ocl -d 1 -t 1 -i 22 ...
To mine on CPU (algorithm from original fork):
Code:
minerd.exe -a wildkeccak ...
Discussion thread
https://bitcointalksearch.org/topic/m.8339439
GREAT!
I am very glad to have the poolminer
August 13, 2014, 09:47:15 PM
I watched daemon and pool miner side by side. New block doesn't force anything on the stratum miner. It calculates hashes for the last job until it finds a share and the pool rejects it. It could take a lot of time. Miner reconnects, gets scratchpad updates and new job and it works fine again. Stratum makes no sense this way.
Can you test if my server is doing better now? Looked ok to me, but I couldn't test much and I have to go. Thanks! To pool owners:
Pool difficulties are too low for OpenCL stratum miner. Increase it at to 5M and 10M for multi-gpu configurations.
Check your pool sends scratchpad update messages in time. I tested 2 pools - bbr.farm sends it, cncoin.farm doesn't. It's inefficient without instant scratchpad updates.
I'll look into it. I don't get why var diff doesn't work with stratum cpuminer. It works with the opencl simpleminer...Pool difficulties are too low for OpenCL stratum miner. Increase it at to 5M and 10M for multi-gpu configurations.
Check your pool sends scratchpad update messages in time. I tested 2 pools - bbr.farm sends it, cncoin.farm doesn't. It's inefficient without instant scratchpad updates.
August 13, 2014, 08:40:38 PM
I watched daemon and pool miner side by side. New block doesn't force anything on the stratum miner. It calculates hashes for the last job until it finds a share and the pool rejects it. It could take a lot of time. Miner reconnects, gets scratchpad updates and new job and it works fine again. Stratum makes no sense this way.
To pool owners:
Pool difficulties are too low for OpenCL stratum miner. Increase it at to 5M and 10M for multi-gpu configurations.
Check your pool sends scratchpad update messages in time. I tested 2 pools - bbr.farm sends it, cncoin.farm doesn't. It's inefficient without instant scratchpad updates.
I'll look into it. I don't get why var diff doesn't work with stratum cpuminer. It works with the opencl simpleminer...Pool difficulties are too low for OpenCL stratum miner. Increase it at to 5M and 10M for multi-gpu configurations.
Check your pool sends scratchpad update messages in time. I tested 2 pools - bbr.farm sends it, cncoin.farm doesn't. It's inefficient without instant scratchpad updates.
August 13, 2014, 08:12:45 PM
To pool owners:
Pool difficulties are too low for OpenCL stratum miner. Increase it at to 5M and 10M for multi-gpu configurations.
Check your pool sends scratchpad update messages in time. I tested 2 pools - bbr.farm sends it, cncoin.farm doesn't. It's inefficient without instant scratchpad updates.
I'll look into it. I don't get why var diff doesn't work with stratum cpuminer. It works with the opencl simpleminer... Pool difficulties are too low for OpenCL stratum miner. Increase it at to 5M and 10M for multi-gpu configurations.
Check your pool sends scratchpad update messages in time. I tested 2 pools - bbr.farm sends it, cncoin.farm doesn't. It's inefficient without instant scratchpad updates.
Jump to: