Topic: [ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net - page 174. (Read 409641 times)

yeah I managed to get a few already 

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

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?

Will the fpga code work on a Cairnsmore1?

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.

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

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...

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  

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 ...

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 !!

I managed to mine 17 mature blocks last night

I have 129 unconfirmed blocks. cgminer then lost connection. I have reset both and we will see but my guess is orphans

An export from the blakecoin-qt

https://docs.google.com/spreadsheet/ccc?key=0AoaBQCn_-M5CdDByVHExTVhZLTBxY2piYy1PY1BzM3c&usp=sharing

Me too but they were all orphan!

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).

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

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

BlueDragon747 thanks for the info, i think its important to have some data like that on the forum so new people reading the thread can get a better idea of why blakecoin exists. to me it sounds like a great idea and i plan to continue mining it for now, since i can see how it will have worth. I like the idea of using it in a game, i had a similar idea but do not have the programming skills to implement it. Perhaps think bigger than just using blakecoin in your game, make an api so that it can be integrated into any game. this way a whole ecosystem can develop and it would be easy to transfer value between games. also would be able to have a whole economy of digital goods like game weapons and armor that people could buy/sell in the games auction house.  This would be a great niche for blakecoin to fill because even if it doesnt become a mainstream coin, it would still have value within the gaming community. just imagine if it became a standard platform for a lot of games within a few years

anyways, i also wanted to say that i was having trouble compiling cgminer on 64 bit linux, is it not ported yet or do i have to use a certain ./configure option flag? when i run make it stops with an error saying

Ok I think I now understand why this is happening  

This is a bug and will be patched for 0.8.7

1. this time of year we have many people all over the world adjusting the clocks for daylight saving
2. fast re-target of 1 hour and the small interval of 20 blocks
3. the wallet does allow the mining of a diff 1 block under special circumstances

so what has happened is that the wallet has mistaken the the clocks changing and thought that the 2* retarget time has passed without a block and allowed the mining of a diff 1 block  

normally if an attacker tried this it would get rejected but on a small network like Blakecoin and with many people including myself having daylight saving set to automatic it has resulted in low difficulty because a lot of nodes all changed at once, problem found and I will patch it for 0.8.7 but it is not such a large issue so just enjoy the low difficulty  

Thanks to everyone who let me know about the problem quickly

To bluedragon747 / fyi sent you personal mesg. No hurry i understand you are busy now. No reply necessary :-)

 

not sure why it is doing this I am looking at it now  

edit:
I might need to do a checkpoint but the chain length is getting large

this is not what I want to be working on  

edit2:
I am not going to be able to fix this fast enough for the growth of the network at the current rate so my best bet is to make a network rule to stop this happening again in the future once I find and identify the problem expect 0.8.7 to be out this weekend.

best checkpoint I have is back at block 12249 and we are at 16752 so I dont think it is fair to cut the blocks from the chain and fork it  

edit3:
I see no reason to stop mining the length of the chain is too long to just cut with a old checkpoint and you might miss out on some easy blocks due to this bug/attack and I dont see it going low again  

Uh oh.  All of a sudden the Diff dropped to almost zero 

Not my best though ...

1.6 billion diff share (on a pool), mined with a 12MHash/sec homebrew fpga, and within the first few thousand shares mined too ...



Yowzer indeed (though it only made me a few satoshi). Now if I could only have some useful luck ...