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

[atavacron]

Oh man, wish I had been watching the network about 9 hours ago xD

Looks like difficulty is back on target, climbing....

It was crazy.

I was testing Krambles latest bitstream on 2 x6500 FPGAs.  All a sudden I started getting blocks every 20 seconds.  My display was filling with found blocks so fast that it took up half the screen (I wish I had taken a snapshot).

Got another two bitstreams for you ...

https://www.dropbox.com/s/g7iqzfl4yzmsnk2/X6500-StaticClock-v01-2core-125MHz.bit

https://www.dropbox.com/s/q1f0a1xdmt1olll/X6500-StaticClock-v01-2core-150MHz-bad.bit

The 150Mhz one failed timing so will probably not work. I'll need to do some redesign to get a faster speed as this seems to be the limit with the current configuration.

This morning was something of a shock, as I woke up to my first overnight cgminer run with this ...

Code:

 [2013-11-02 07:58:22] Started at [2013-11-01 23:55:12]
 [2013-11-02 07:58:22] Pool: http://localhost:8772
 [2013-11-02 07:58:22] Runtime: 8 hrs : 3 mins : 10 secs
 [2013-11-02 07:58:22] Average hashrate: 410.4 Megahash/s
 [2013-11-02 07:58:22] Solved blocks: 28
 [2013-11-02 07:58:22] Best share difficulty: 2.92K
 [2013-11-02 07:58:22] Share submissions: 65
 [2013-11-02 07:58:22] Accepted shares: 19
 [2013-11-02 07:58:22] Rejected shares: 46
 [2013-11-02 07:58:22] Accepted difficulty shares: 220
 [2013-11-02 07:58:22] Rejected difficulty shares: 94
 [2013-11-02 07:58:22] Reject ratio: 70.8%
 [2013-11-02 07:58:22] Hardware errors: 2

Unfortunately only six of them actually survived to maturity. Seems blakecoind on raspi just couldn't process the blocks fast enough and I kept getting reorgs for my newly mined blocks But we're back to normal now, 10k diff !!

Sweet!  I'll give the new ones a try.

Heheheh...it was fun to watch the FPGAs solve blocks like wild.  I re-downloaded the blockchain to double-check and to my surprise half of the blocks mined last night survived  

[bzyzny]

atavacron you lucky guy, you must be rolling in the blakecoins now. unfortunately my miner was offline for the low difficulty heyday

so if my estimate is correct there are about 500,000 blakecoins in existence currently, right? ~20,000 blocks times 25 = 500,000. does anyone have a guess of what the worth of 1 blakecoin is or will be in the future? i think adding blakecoin to an exchange site like cryptsy too early would be detrimental, i've seen a lot of alt coins get dumped the minute they are listed and then never recover. i like that blakecoin seems to be taking the slow and steady approach, this is definitely a long term project it is becoming rather difficult to solo mine though...

[mogrith]

Very much looking forward to a pool. only have ~715MH/s

I am also keeping an eye out for a cheap FPGA have not had one before. it looks intersting

[110110101]

Thanks BlueDragon747 for the explanation on todays diff drop.
It's great to get feedback from the developer about the current state of things. Much appreciated!
I'll be looking forward to the coming update.

[mogrith]

Will the fpga code work on a Cairnsmore1?

[BlueDragon747]

Will the fpga code work on a Cairnsmore1?

I have asked kramble to look into a port for Cairnsmore1 and he is already working on a port for the ztex 1.15y so it should not be long before we see a port of both the Blakecoin miner and his Litecoin miner to those boards  

We are very lucky to have kramble working on the FPGA's and I have enjoyed working with all his miners from the Bitcoin miner on the DE0-Nano, Litecoin miner on the Lancelot and now with some excellent results on his Blakecoin miner, I will try my best to help kramble when possible  

I am still working on the pool stuff got the new code on the server and I am mining to find a block candidate then I will see if my new code fixes the block submission bug that I have been stuck on since last weekend  

I will try to get 0.8.7 wallet out within next 12 hours, it will have the patch for the diff 1 bug we have seen yesterday and I have also been looking at reducing the block target time from the current 3 minutes to 30 seconds, the reason for this is to make the re-target from 20 blocks to 120 blocks this will be a network rule from a future block 21000? but I am running some tests before hand to make sure it does not create any new random features

just had my breakfast and a nice cup of tea so will continue to work on this for rest of the day

Edit:
is it just me or is the difficulty quite low today?

[110110101]

Edit:
is it just me or is the difficulty quite low today?

Currently around 1575, so lower than what is has been the past week. Makes for a good opportunity to get a block!

[BlueDragon747]

Edit:
is it just me or is the difficulty quite low today?

Currently around 1575, so lower than what is has been the past week. Makes for a good opportunity to get a block!

yeah I managed to get a few already 

[BlueDragon747]

Blakecoin wallet version 0.8.7 Released

Sync Bug Please use 0.8.8

[bzyzny]

are we stuck on block 19725 or is it an issue related to me updating my wallet? my blakecoin-qt debug window shows its been on the same block for at least 15 minutes

of course as soon as i say something about, the block number goes up

I was also wondering if it is possible to compile the linux wallet with dependencies included? i had to install libdb and several libboost packages before blakecoin-qt would launch. If not having them included in the binary, a list of dependencies at least would be helpful.

[BlueDragon747]

I appreciate the feedback you never know if it is a bug so always best to report weird behavior after an update

I was just about to grab some sleep so any problems backup your wallets, revert to 0.8.6 and post a report of the error, this was a small update and is not supposed to create any issues beyond a few hours while everyone updates  

sync bug fixed in 0.8.8 please update

[bzyzny]

i am curious what the motivation is for switching to 30 second block? Will the block reward change, or stay at 25blc + inflation? also does changing the block target time actually change much, or just make it look faster?

[feeleep]

Blakecoin wallet version 0.8.7 Released

Github updated

Windows
http://blakecoin.org/Blakecoin-0.8.7-WIN.7z

Linux
http://blakecoin.org/Blakecoin-0.8.7-LIN.7z

Please update Your wallets before sending any Blakecoin!

edit:
the wallet might re-sync a few times as everyone updates, if it gets stuck for more than 5 minutes try to close and reopen

windows client dont want to download the blockchain, and link to 8.6 version downloads 8.7 actually

[mogrith]

it loaded under win7 64 for me
v0.8.7.0-g8c5e74e-beta

[feeleep]

it loaded under win7 64 for me
v0.8.7.0-g8c5e74e-beta

i had to redownload the chain and stuck at 19... second client is probably on different chain as I am finding blocks but block height is 19731

[cinnamon_carter]

Same problem here - tried with wallet & without / Tried everything / Now fresh install the blockchain is at 19 of 19762 :-(

[mogrith]

Odd had reloaded and I had green checkmark. Opened debug to info tab and it said Block 19709.
closed window and I'm syncing again 3 hrs behind.

[BlueDragon747]

Sync bug in 0.8.7 fixed in 0.8.8

Blakecoin Wallet Release 0.8.8

Github updated

Windows
http://blakecoin.org/Blakecoin-0.8.8-WIN.7z

Linux
http://blakecoin.org/Blakecoin-0.8.8-LIN.7z

[bzyzny]

(edit) this post was before the 0.8.8 wallet for linux was available, pls update instead of reverting to 0.8.6 (/edit)
after updating to 0.8.7, i had several blocks found but some of which appeared to be orphans. since there was no 0.8.8 for linux yet, i reverted to 0.8.6 and it said all my recent blocks were orphans. however 0.8.6 seemed to sync fine, so when i then switched again to 0.8.7 it showed that none were orphans and each had several confirmations. so perhaps going back to 0.8.6 allowed my blockchain to synchronize properly, but at any rate hopefully the 0.8.8 will clear it all up. if you have gotten orphans after updating to 0.8.7 i would suggest trying going back to 0.8.6 to synchronize, as a possible solution if anyone else is having similar issue

[BlueDragon747]

after updating to 0.8.7, i had several blocks found but some of which appeared to be orphans. since there was no 0.8.8 for linux yet, i reverted to 0.8.6 and it said all my recent blocks were orphans. however 0.8.6 seemed to sync fine, so when i then switched again to 0.8.7 it showed that none were orphans and each had several confirmations. so perhaps going back to 0.8.6 allowed my blockchain to synchronize properly, but at any rate hopefully the 0.8.8 will clear it all up. if you have gotten orphans after updating to 0.8.7 i would suggest trying going back to 0.8.6 to synchronize, as a possible solution if anyone else is having similar issue

try 0.8.8 might need to rebuild your chain