Hi,

I've just updated my miner repositories on Github with increased scratchpad buffer size.

https://github.com/mbkuperman/cpuminer-multi-opencl
https://github.com/mbkuperman/boolberry-opencl

You can compile it yourself or grab a binary release for Windows x64
https://github.com/mbkuperman/cpuminer-multi-opencl/releases/latest

Scratchpad is getting close to 256 MB limit so don't be late in case you are using my miners (and check the size if you are mining with something else too).

My pool is down. It was under constant attacks since last pump began. Somehow I got blacklisted by Spamhaus. I'm really sorry but I cannot fix it immediately. It is sad there are people in crypto lacking moral values. More troubling is that they operate its critical infrastructure.

Edit: Just fixed the problem. Pool works again.

Thanks for your work. Let's continue moving this way. Make commits to your repository so I and everybody else can review them. The most urgent task for me is to merge DB branch from the original repository to master. Daemon needs a lot of memory to run right now. That's not good for a decentralized system. I would prefer you to checkout DB branch and commit on top to make the review process simpler.

Hi all,

I've got a number of private messages lately. I don't like private chats. It's better to give all answers here in public.

I'm trying to keep my pool online all the time cause I use it myself a bit. All pending payments are sent in all case. The only real DDOS attack was this August. It finished about a week ago. All connection issues should be resolved.

If you have problems with pool/miner apps post it here so you can get help from other guys who mine as well.

Regarding new development activities. You can count on me if some updates need to be deployed on the pool. Just keep development open so everybody can evaluate your proposals/code and give a feedback. Have any ideas how to handle possible forks? Post it here. Let's keep this discussion as open as possible.

I'm not going to actively participate in current discussion but I'll read all feedback.

My pool bbr.mbkpool.info experienced major connection problems due to boolberry daemon overload. There were 2 threads to serve RPC requests from the pool hardcoded in the source regardless of CPU cores available. I had to increase the count and recompile the daemon. The problem solved. I'll be watching pool performance more closely next few days.

Boolberry OpenCL solo/pool miner mandatory update

There is a hardcoded 64M scratchpad size in my OpenCL miners. We are getting close to the limit. There are 2-3 weeks before we reach it. I increased the size to 256M in the update. It should not be a problem for any modern GPU.

https://github.com/mbkuperman/boolberry-opencl
https://github.com/mbkuperman/cpuminer-multi-opencl

Windows x64 binary
https://github.com/mbkuperman/boolberry-opencl/releases
https://github.com/mbkuperman/cpuminer-multi-opencl/releases

My pool bbr.mbkpool.info had problems with payments lately. It was due to wallet getting out of sync like many times before. All miner payments for last few days have been sent. I rescheduled the wallet restart script to prevent such problems in the future.
Just noticed - cncoin.farm has 97% of total hash rate. It's a reliable pool but it doesn't look good for the coin. Please, use solo miner or some other pool if you can.

For pool miner: use -d (start with Nth device instead of 0) and -t (use N devices) command line parameters.
Examples:
-d 1 -t 1 (use second GPU only)
-t 2 (use 2 GPUs only)

For solo miner:
"device_index" option in miner_conf.json file (it's like -d option above)
--mining-threads command line parameter (like -t above)

Boolberry OpenCL solo miner update
Synced to the main branch (version 0.3.0.41)
https://github.com/mbkuperman/boolberry-opencl

Windows x64 binary
https://github.com/mbkuperman/boolberry-opencl/releases

I had some problems with the miner terminating for no reason some time ago. I don't get it with last versions so I suppose it was some core daemon problem. Check you run version 3.0.38. The GPU miner itself is very stable (at least on Windows). It runs for weeks on various AMD cards in 3-card configurations without any problems if you don't overclock it too much.

Changing intensity won't fix your problem. What's your accepted ratio? If it's high you definitely have some network issues with the pool.

Boolberry OpenCL solo miner update
Synced to the main branch
https://github.com/mbkuperman/boolberry-opencl

Windows x64 binary
https://github.com/mbkuperman/boolberry-opencl/releases

MBK's Boolberry Mining Pool

I've spend a lot of time optimizing OpenCL miner so later I looked at how pools work too. Clintar fixed the problems so pools work much better now if updated. Anyway I have some ideas how to tune the pool to get more blocks on the same hardware. I tested it for a week with my GPU farm, rented a decent server and now you can give my pool a try.

http://bbr.mbkpool.info

Usage with my OpenCL miner:
Windows
Linux

Changes:

• 100ms boolbd daemon polling interval - to get new blocks as soon as possible (later I could make it even less)
  
• 1 minute difficulty targeting - it's better to make shares rarer and more valuable in current miner implementation (starting diff is 150 millions on port 9999 for multi-GPUs)

Options to try:
-i x (intensity) - default value is 18, try lower values if it doesn't lower your hashrate as it will improve efficiency (we cannot exit GPU calculation cycle so the shorter cycle means less time we lose when new block arrives)

I'm not talking about large improvement but the miners should be close to 100% efficiency. You can try it and make decision yourself. Look at miner's output and compare. In the real example below the miner calculates 1112 kh/s and every hash works to make a share on the pool.

You can run them both. Just set different data directories with --data-dir command line option like:

If you exit the boolbd it saves miner_conf.js. It's the wrong file if you cannot find the parameter or you ran cpu version after opencl one (look at %appdata%\boolb on windows).  Try all platform_indexes: 0,1,2.

Try changing platform_index in miner_conf.js file.

Boolberry OpenCL miner update
https://github.com/mbkuperman/boolberry-opencl

Windows x64 binary
https://github.com/mbkuperman/boolberry-opencl/releases

Boolberry OpenCL miner update
https://github.com/mbkuperman/boolberry-opencl

Windows x64 binary
https://github.com/mbkuperman/boolberry-opencl/releases

Try erasing blockchain data to start from the scratch:
and delete blockchain.bin (or just delete or rename the whole directory)

It looks like you use solo miner. I'll update the solo miner a bit later. Maybe on the weekend. Anyway it's just a notification the new version is out. You can use the current version for the time being.