Topic: [ANN] [BBL] BitBlock-World's first X15 coin|Bittrex|Poloniex|Mandatory Update - page 22. (Read 82727 times)
June 27, 2014, 07:19:18 PM
Can you use the gpu miner on suprnova pool?
June 27, 2014, 07:16:04 PM
and.. block explorer is down
not that it ever worked correctly... addresses display was wrong
not that it ever worked correctly... addresses display was wrong
June 27, 2014, 07:12:47 PM
I have downloaded the cpu miner and tried running it on both 32 and 64 bit windows 7 pc's on suprnova pool using .bat file command line 'minerd -a bitblock -o stratum+tcp://bbl.suprnova.cc:3663 -u x -p x -t 3' as shown on pool getting started guide and every time the miner wont start. I've tried different thread settings and no thread setting and still the same.
Can anyone please tell me correct .bat command line.
Can anyone please tell me correct .bat command line.
Try start it with this in the bat to see if it runs and gives you a hashrate:
Code:
minerd -a bitblock --benchmark
Pause
If it still won't run, make sure the miner id not being block by your firewall. Also check the file properties to see if Windows is blocking the file. I know Windows 8.1 will keep some wallets and miners from running until you unblock them.
Thank you very much that's done it
June 27, 2014, 07:08:52 PM
I have downloaded the cpu miner and tried running it on both 32 and 64 bit windows 7 pc's on suprnova pool using .bat file command line 'minerd -a bitblock -o stratum+tcp://bbl.suprnova.cc:3663 -u x -p x -t 3' as shown on pool getting started guide and every time the miner wont start. I've tried different thread settings and no thread setting and still the same.
Can anyone please tell me correct .bat command line.
Can anyone please tell me correct .bat command line.
Try start it with this in the bat to see if it runs and gives you a hashrate:
Code:
minerd -a bitblock --benchmark
Pause
If it still won't run, make sure the miner id not being block by your firewall. Also check the file properties to see if Windows is blocking the file. I know Windows 8.1 will keep some wallets and miners from running until you unblock them.
June 27, 2014, 06:53:23 PM
June 27, 2014, 06:46:56 PM
buy now and thank me later 
Yeah, this is looking pretty explosive.
June 27, 2014, 06:46:09 PM
I have downloaded the cpu miner and tried running it on both 32 and 64 bit windows 7 pc's on suprnova pool using .bat file command line 'minerd -a bitblock -o stratum+tcp://bbl.suprnova.cc:3663 -u x -p x -t 3' as shown on pool getting started guide and every time the miner wont start. I've tried different thread settings and no thread setting and still the same.
Can anyone please tell me correct .bat command line.
Can anyone please tell me correct .bat command line.
June 27, 2014, 06:26:12 PM
buy now and thank me later
June 27, 2014, 06:25:20 PM
That I'll can dump some of them, of course! that is the only difference for me, so cool earning 500$ in 2 hours of cpu mining 
I won't sell any right now, the price is still too low.
June 27, 2014, 06:24:48 PM
And it seems there is no answer about the Darkcoin logo into the BBL wallet tray icon ?
Read between the lines, this is DRK 2.0! just w8!
Exactly, it's DRK 2.0 in at least 1 aspect:
With an even faster instamine 1.8m in 18 hours.
The next 1,8m coins at current block reward (25) will take 125 days.
Interpretation of these facts is up to every individual of course : )
That's not true. It took less than 8 hours for over 1.6M coins to be mined with Darkcoin, which uses the same block reward structure and started at 500 coins per block as well. All without even a Windows wallet available for days.
http://www.devtome.com/doku.php?id=a_massive_investigation_of_instamines_and_fastmines_for_the_top_alt_coins#darkcoin
In comparison the BBL was MUCH more fair an evenly distributed. The wallets, miners, pools and block explorer were all available at launch.
June 27, 2014, 06:16:40 PM
Other than this being the first x15 what else is going for it?
That I'll can dump some of them, of course! that is the only difference for me, so cool earning 500$ in 2 hours of cpu mining
June 27, 2014, 06:11:23 PM
The price now in bittrex
0.00013000
BBL go to the moon
hold dont rush to sell
0.00013000
BBL go to the moon
hold dont rush to sell
June 27, 2014, 06:07:52 PM
bbl to the moon.now so cheap 12000sats
June 27, 2014, 06:04:33 PM
Other than this being the first x15 what else is going for it?
June 27, 2014, 06:00:32 PM
And it seems there is no answer about the Darkcoin logo into the BBL wallet tray icon ?
Read between the lines, this is DRK 2.0! just w8!
Exactly, it's DRK 2.0 in at least 1 aspect:
With an even faster instamine 1.8m in 18 hours.
The next 1,8m coins at current block reward (25) will take 125 days.
Interpretation of these facts is up to every individual of course : )
June 27, 2014, 05:14:35 PM
aznboy84, getting a report in from ystarnaud at sgminer-dec/sgminer
You need to do a pull request and specify the sgminer_v5 tree instead of the master tree. Even though master was pushed up into v5, you're asking it compare against an incorrect tree.
Thanks again if you can close the old pull request and open a new one pointed specifically at the v5_0 tree branch. You may need to select "compare across forks" in the pull request option.
Edit, since your pull is trying to compare master against v5_0, inherently it is already "behind" compared to the modded pre-release-06-25-2014 you have modded and dropped on us
EDIT 2: Big thanks on closing issue 293 buddy, looking forward to when you get the new pull committed shortly.
You need to do a pull request and specify the sgminer_v5 tree instead of the master tree. Even though master was pushed up into v5, you're asking it compare against an incorrect tree.
Thanks again if you can close the old pull request and open a new one pointed specifically at the v5_0 tree branch. You may need to select "compare across forks" in the pull request option.
Edit, since your pull is trying to compare master against v5_0, inherently it is already "behind" compared to the modded pre-release-06-25-2014 you have modded and dropped on us
EDIT 2: Big thanks on closing issue 293 buddy, looking forward to when you get the new pull committed shortly.
Done i guess ... it's way more harder than coding
First day on github and i had to do this lol
No shit, I'm with you on that. It's one thing to be able to code, a whole thing entirely to have to deal with the versioning system on github.
You da man, I'm gonna bug the fuck outta the devs to push that shit in pronto.
June 27, 2014, 05:13:35 PM
Anymore with this... Would like to throw my 7870's on this, but the modded sgminer doesn't work.
Use bitblockold kernel instead of bitblock ...aznboy84, getting a report in from ystarnaud at sgminer-dec/sgminer
You need to do a pull request and specify the sgminer_v5 tree instead of the master tree. Even though master was pushed up into v5, you're asking it compare against an incorrect tree.
Thanks again if you can close the old pull request and open a new one pointed specifically at the v5_0 tree branch. You may need to select "compare across forks" in the pull request option.
Edit, since your pull is trying to compare master against v5_0, inherently it is already "behind" compared to the modded pre-release-06-25-2014 you have modded and dropped on us
EDIT 2: Big thanks on closing issue 293 buddy, looking forward to when you get the new pull committed shortly.
You need to do a pull request and specify the sgminer_v5 tree instead of the master tree. Even though master was pushed up into v5, you're asking it compare against an incorrect tree.
Thanks again if you can close the old pull request and open a new one pointed specifically at the v5_0 tree branch. You may need to select "compare across forks" in the pull request option.
Edit, since your pull is trying to compare master against v5_0, inherently it is already "behind" compared to the modded pre-release-06-25-2014 you have modded and dropped on us
EDIT 2: Big thanks on closing issue 293 buddy, looking forward to when you get the new pull committed shortly.
Done i guess ... it's way more harder than coding
First day on github and i had to do this lol
June 27, 2014, 04:58:44 PM
how should we set the kernel option. kernel:"bitblock" ? i try it with suprvno.cc pool but it's show all reject share on it
use "algorithm" : "bitblock" instead ....
aznboy84, getting a report in from ystarnaud at sgminer-dec/sgminer
You need to do a pull request and specify the sgminer_v5 tree instead of the master tree. Even though master was pushed up into v5, you're asking it compare against an incorrect tree.
Thanks again if you can close the old pull request and open a new one pointed specifically at the v5_0 tree branch. You may need to select "compare across forks" in the pull request option.
Edit, since your pull is trying to compare master against v5_0, inherently it is already "behind" compared to the modded pre-release-06-25-2014 you have modded and dropped on us
We're getting there I think, but I don't think aznboy84 forked off that v5_0 tree, his was a local upload so it won't compare across to sgminer-dev/sgminer. He may need to re-fork and add in his bitblock.cl additions like he did with his local upload. That may be what he's doing now, haven't heard from him in an hour or two.
EDIT 2: Big thanks on closing issue 293 buddy, looking forward to when you get the new pull committed shortly.
Anymore with this... Would like to throw my 7870's on this, but the modded sgminer doesn't work.
Looks like aznboy84 just submitted another pull request 294, we'll see how fast we can get it into the multi-algo with newest commits. About 20 commits already been newer than the 06/25 build.
MUCH APPRECIATED aznboy84
June 27, 2014, 04:35:59 PM
how should we set the kernel option. kernel:"bitblock" ? i try it with suprvno.cc pool but it's show all reject share on it
use "algorithm" : "bitblock" instead ....
aznboy84, getting a report in from ystarnaud at sgminer-dec/sgminer
You need to do a pull request and specify the sgminer_v5 tree instead of the master tree. Even though master was pushed up into v5, you're asking it compare against an incorrect tree.
Thanks again if you can close the old pull request and open a new one pointed specifically at the v5_0 tree branch. You may need to select "compare across forks" in the pull request option.
Edit, since your pull is trying to compare master against v5_0, inherently it is already "behind" compared to the modded pre-release-06-25-2014 you have modded and dropped on us
EDIT 2: Big thanks on closing issue 293 buddy, looking forward to when you get the new pull committed shortly.
Anymore with this... Would like to throw my 7870's on this, but the modded sgminer doesn't work.
June 27, 2014, 03:48:56 PM
how should we set the kernel option. kernel:"bitblock" ? i try it with suprvno.cc pool but it's show all reject share on it
use "algorithm" : "bitblock" instead ....
aznboy84, getting a report in from ystarnaud at sgminer-dec/sgminer
You need to do a pull request and specify the sgminer_v5 tree instead of the master tree. Even though master was pushed up into v5, you're asking it compare against an incorrect tree.
Thanks again if you can close the old pull request and open a new one pointed specifically at the v5_0 tree branch. You may need to select "compare across forks" in the pull request option.
Edit, since your pull is trying to compare master against v5_0, inherently it is already "behind" compared to the modded pre-release-06-25-2014 you have modded and dropped on us
EDIT 2: Big thanks on closing issue 293 buddy, looking forward to when you get the new pull committed shortly.
Jump to: