[ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net

[bzyzny]

before i posted my last message it said "currently building linux wallet", and by the time i posted you had the link for the linux 0.8.8 up. so i have switched to that and so far it seems to be working fine. thanks for the update perhaps my previous post will still be useful if anyone else had some blocks show up as orphans while using 0.8.7; i think they just showed up as orphans due to the sync error and not due to actually being orphans.

[1714775992]

1714775992

[1714775992]

1714775992

[1714775992]

1714775992

[BlueDragon747]

before i posted my last message it said "currently building linux wallet", and by the time i posted you had the link for the linux 0.8.8 up. so i have switched to that and so far it seems to be working fine. thanks for the update perhaps my previous post will still be useful if anyone else had some blocks show up as orphans while using 0.8.7; i think they just showed up as orphans due to the sync error and not due to actually being orphans.

I do both x64 and x86 for Linux so it just takes me a little longer to compile, I could not get to sleep thinking about a possible bug and it was a bug in the way I was trying to increase the interval to 120 blocks

In the future I will have to write an if statement in each function that calls the interval and do a block height check but for now I will leave it working rather than add more random features

Sorry about the issues in 0.8.7 it did not show up in my testing I will make some additions to how I am testing to try and avoid this happening  

Ref:
Reason for wanting the change to 30 seconds is to lower the overall difficulty and help the average it is using for the re-target

the TargetSpacing (this is what I was changing from 3mins - 30secs) this is the target time that the wallet uses to calculate the difficulty in relation to the TargetTimespan and the Interval is the amount of blocks between re-targets.

Edit:
always feel free to post errors, issues, solutions or just to check everyone else is getting similar results I do appreciate the feedback
and like you said the info might be useful to others  

  

[Wubbllez]

http://imgur.com/DEcOktK
It might be just me guys....but I dont think I'm getting 200Mh/S

(Wont let me put a strait image link. That blows.)

[bzyzny]

It might be just me guys....but I dont think I'm getting 200Mh/S

more info would help. what graphics card are you using? and what settings for reaper?
I am using a AMD 7950 @ 1000Mhz/ 600Mhz and my blakecoin.conf for reaper currently has these settings:

worksize 256
aggression 26
threads_per_gpu 1
cpu_mining_threads 0
vectors 1
worksize 32

With this card and configuration I'm getting ~1.98Gh/s

[edit]LOL i didnt look at your pic closely enough, I see now that its an Nvidia 550. Don't know what hashrate should be expected from it but i'm not surprised its much less since Nvidia cards just aren't designed for hashing   [/edit]

[BlueDragon747]

http://imgur.com/DEcOktK
It might be just me guys....but I dont think I'm getting 200Mh/S

(Wont let me put a strait image link. That blows.)

Thank you for testing not a lot of miners are using Nvidia cards due to the need to write specific Cuda code rather than the OpenCL code 

I would like to see more from Nvidia they are powerful cards but it takes some specific optimisation to be able to tap into that hashing power 

[mogrith]

Well I should have a Enterpoint Cairnsmore1 Bitcoin miner later this week just to play around with. I'll use it for fireflycoin and cubits until we are ready for testing on Blake.

[Eli0t]

http://imgur.com/DEcOktK
It might be just me guys....but I dont think I'm getting 200Mh/S

(Wont let me put a strait image link. That blows.)

your doing better than the cgminer port. 40 MH on a 560ti

[cinnamon_carter]

new client ver 8.8 working well after taking a day off mining with a single diamond saphire 7970 although i got lucky & hit a block of feathercoin :-)
getting 2.8 ghs with cg miner
--shaders 2048 --blake256 --gpu-engine 1175 --gpu-memclock 700 --threadconcurrency 22392 -w 264 -s 1 - E 3 -I 14

other settings i had used with reaper i mentioned in this post on another forum
https://cryptocointalk.com/topic/1446-if-you-want-to-mine-blake-coin-with-a-gpu-here-is-some-information/
thanks Blue for such a fast fix. I like blake coin !

Appears difficulty is lower tonight at 960 so hopefully I hit a few blocks !

[bzyzny]

if anyone has some useful links on how to run a pool or blockchain explorer, i'd be happy to try. or also if anyone knows how to do this but just needs hosting, let me know, I have a server that I could dedicate to it.

[cinnamon_carter]

Google 'abe'

check for it on github
https://github.com/bitcoin-abe/bitcoin-abe

if anyone has some useful links on how to run a pool or blockchain explorer, i'd be happy to try. or also if anyone knows how to do this but just needs hosting, let me know, I have a server that I could dedicate to it.

[maxsolnc]

Guys, what about pool? So much time after release - and no pool, it discourages many people (me too) from solomining it b\c of very low block rate

[feeleep]

Guys, what about pool? So much time after release - and no pool, it discourages many people (me too) from solomining it b\c of very low block rate

I was working few days on pool code but there is a problem with merkleroot calculation on stratum server and even if shares are accepted and server recognize correctly block candidate it fails to build correct information for blakecoin client.

[Wirel]

Yay i would love to have a pool for BLC mining !

[meta.p02]

I'm working on a p2pool fork for Blakecoin.

Right now I can't get the blake hash to work properly... for some reason...

Code:

ProcessMessages(version, 128 bytes) : CHECKSUM ERROR nChecksum=916c82af hdr.nChecksum=4bc57200

Trying now to check whether it is an endianness error...

(BlueDragon747... why oh why did you use blake hash for the checksum... D:)

[BlueDragon747]

I'm working on a p2pool fork for Blakecoin.

Right now I can't get the blake hash to work properly... for some reason...

Code:

ProcessMessages(version, 128 bytes) : CHECKSUM ERROR nChecksum=916c82af hdr.nChecksum=4bc57200

Trying now to check whether it is an endianness error...

(BlueDragon747... why oh why did you use blake hash for the checksum... D:)

at the time it made sense to use a faster hash for as much of the wallet hashing as possible  

in Blakecoin you get about three blake256(checksum) per sha256(sha256(checksum)) so it makes sense to use it but the cost is compatibility with the Bitcoin/Litecoin software 

are you using pure python blake8.py that kramble has modded or the python pow module?

[cinnamon_carter]

A few thoughts on those fustrated because there is no pool to join.

From a mathematical standpoint you will make exactly the same amount of coins solo mining as you will in a mining pool. Sometimes more. If you donate to a pool or it has a fee you earn less than on your own.
Some coins (not Blake Coin to my knowledge) pay transaction fees to the person who finds a block. Not all pools pass these on to miners.

If you were mining something with a very high difficulty like how litecoin is now I can understand you being unwilling to go at it alone since the chance of a block is so low.

Right now unless you are using a cpu Blake Coin is well within the reach to hit some blocks & get some coins.
Difficulty goes up and down but not so bad that you cannot mine a block.

I am running one gpu and if I can hit blocks so can you !

It is also a little more exciting to solve a block than watch shares tick by.

You get 25 at once plus the subsidy !

Let's relax a little here.

In time someone will solve this problem and you shall have your pool.

Difficulty will probably go up a lot higher.

Not mining because there is no pool is something I can't agree with or understand.

This is valid for any coin unless your hash rate would only produce a block once a week or one a month depending on your patience. 

[mogrith]

Well I should have a Enterpoint Cairnsmore1 Bitcoin miner later this week just to play around with. I'll use it for fireflycoin and cubits until we are ready for testing on Blake.

Shipping delayed hope to have it by 15NOV13 no biggie since there is no blakecoin code for this yet.

[bzyzny]

cinnamon_carter you make some very good points. This is a good coin which offers something novel unlike many other alt-coins. Blake algorithm seems like an excellent one to use for crypto currency, and it is worth supporting Blakecoin even though its off to a slow start. Anyone developing projects like this should take the time to make sure it works well, rather than just slap it together and focus on "marketing". Keep up the good work guys, I really look forward to seeing where Blakecoin is in a year or two

[kramble]

Well I should have a Enterpoint Cairnsmore1 Bitcoin miner later this week just to play around with. I'll use it for fireflycoin and cubits until we are ready for testing on Blake.

Shipping delayed hope to have it by 15NOV13 no biggie since there is no blakecoin code for this yet.

I now have a CM1 on loan from BlueDragon so I hope to get started on a port in the next couple of days. I'm currently working on the Ztex port but this is turning out rather more difficult than I'd hoped. I've just about got it working with cgminer but the hardware error rate is way too high and only three of the four fpgas (seemingly randomly) will load the bitstream. By contrast the bitcoin bitstreams load and run perfectly, so I suspect there is something going wrong in the xilinx build process as the verilog is identical other than the hashing core. It seems I must go deeper into this rabbit hole.

[mogrith]

Well I should have a Enterpoint Cairnsmore1 Bitcoin miner later this week just to play around with. I'll use it for fireflycoin and cubits until we are ready for testing on Blake.

Shipping delayed hope to have it by 15NOV13 no biggie since there is no blakecoin code for this yet.

I now have a CM1 on loan from BlueDragon so I hope to get started on a port in the next couple of days. I'm currently working on the Ztex port but this is turning out rather more difficult than I'd hoped. I've just about got it working with cgminer but the hardware error rate is way too high and only three of the four fpgas (seemingly randomly) will load the bitstream. By contrast the bitcoin bitstreams load and run perfectly, so I suspect there is something going wrong in the xilinx build process as the verilog is identical other than the hashing core. It seems I must go deeper into this rabbit hole.

Wee!

I have an ATX PSU available any special connectors needed?