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

[BlueDragon747]

here is a paper on the HAsh Iterative FrAmework (HAIFA) and explains the improvements over the Merkle–Damgård construction method
http://eprint.iacr.org/2007/278

some of the multi hash algo's like x11, x13 are unproven in security terms as there is very little if any research on them, still lots of algo's in crypto coins just claim to be more secure or more efficient without any sort of proof or independent research I think it is very misleading yet they do get away with it  

it is also funny with some of the coin algo's when they use the 512bit+ size hash but just pad the data or trim the result which is known to be insecure to some attacks  

fast, simple, efficient while maintaining the same security as Bitcoin is the way to go imho I guess time will tell  

I am glad to have other people who are involved or supporters of the project that also appreciate and understand the technical merits  

[1714045662]

1714045662

[1714045662]

1714045662

[1714045662]

1714045662

[1714045662]

1714045662

[teknohog]

some of the multi hash algo's like x11, x13 are unproven in security terms as there is very little if any research on them, still lots of algo's in crypto coins just claim to be more secure or more efficient without any sort of proof or independent research I think it is very misleading yet they do get away with it  

it is also funny with some of the coin algo's when they use the 512bit+ size hash but just pad the data or trim the result which is known to be insecure to some attacks  

fast, simple, efficient while maintaining the same security as Bitcoin is the way to go imho I guess time will tell  

There doesn't seem to be any cryptographic design behind X11 etc., they just wanted a new PoW function for a temporary monopoly. While PoW isn't about exact collisions, they probably go hand in hand -- you're looking for a partial collision with that row of zeros.

(Temporary ASIC resistance is often mentioned. If X11 is truly ASIC resistant, then surely there's no need to develop X13 and the like. OTOH, if there's an X11 ASIC, then it won't be that hard to make an X13 ASIC.)

Hence I think most coins with new hashes are just a waste of resources. Making hashes particularly slow like Scrypt and Cryptonight is just annoying when updating a wallet. This is one area where Blake wins.

As for papers on hashes, here's a less mathematical one: Boolberry's fast but memory-hard algo.

[teknohog]

So for those who think x11 x13 x23 x55 x99 is better see here please

http://ai.stanford.edu/~xb/crypto06b/blackboxhash.pdf

Nice. I only skimmed through the paper, but even without thorough analysis you can guess that X11 wasn't exactly designed for cryptographic security

The way I see it intuitively is that each of the 11 functions is a non-injective mapping (many-to-fewer), basically by the definition of a hash. So when you feed one hash to the next function, you get a many-to-very-few mapping, i.e. much more potential for collisions.

Also, if you find a collision for the first function, it just carries over to the end. So if you want to hedge your bets, you need some other combination besides this linear chain.

[dreamwatcher]

The explorer at blc.cryptocoinexplorer.com has been updated to the latest build.

Features Added:

Market information is now on the home page where the ticker used to be.

Address ownership claim system is now in place. Access with the "Address Claim" button. Address ownership information is available on the top 1000 balances only.


Next build plans:

Charting page (tx, difficulty,blocks - 24 hrs,Week, Month)

Country ID and flag for the IP addresses on the peers page.

Address ownership information available as a tool-tip anywhere on site.


Your suggestions for features or statistics you would like to see are welcome!!!!

[gaalx]

was a lot of rejections. all right?

[BlueDragon747]

was a lot of rejections. all right?

I reset eu3 but I dont see any issue on the server I also checked with one of my miners all accepted and no rejections so far maybe you changed some settings?

[gaalx]

was a lot of rejections. all right?

I reset eu3 but I dont see any issue on the server I also checked with one of my miners all accepted and no rejections so far maybe you changed some settings?

itself I was surprised. I test. thanks.

[cinnamon_carter]

update to blake coin with bugfix as reported by a gitpull (same one on photon also now fixed) fixes an issue with signatures

i built this

https://drive.google.com/file/d/0Bz8503hoyr74QU5vZzRrTmNsTHc/edit?usp=sharing

from this

https://github.com/photonproject/Blakecoin

NOTE, Bluedragon asked me to test and update this , he will merge the gitpull when he has time......

Thanks to all supporters of the blake 256 system

[BlueDragon747]

update to blake coin with bugfix as reported by a gitpull (same one on photon also now fixed) fixes an issue with signatures

i built this

https://drive.google.com/file/d/0Bz8503hoyr74QU5vZzRrTmNsTHc/edit?usp=sharing

from this

https://github.com/photonproject/Blakecoin

NOTE, Bluedragon asked me to test and update this , he will merge the gitpull when he has time......

Thanks to all supporters of the blake 256 system

Thanks Cinnamon will merge when I get more time 

[cinnamon_carter]

No problem, it works well too , i tested it, with blake coin and photon (but i don't think cce has updated the code yet for Pho)

I will get the patch applied to electron and blake bitcoin in a day or so,

I know Chigulator the dev of UMO likes to do his own updating !!

On Dirac I never did any updates since it's 'developer' is so much more talented than anyone on this team he can handle things himself.

update to blake coin with bugfix as reported by a gitpull (same one on photon also now fixed) fixes an issue with signatures

i built this

https://drive.google.com/file/d/0Bz8503hoyr74QU5vZzRrTmNsTHc/edit?usp=sharing

from this

https://github.com/photonproject/Blakecoin

NOTE, Bluedragon asked me to test and update this , he will merge the gitpull when he has time......

Thanks to all supporters of the blake 256 system

Thanks Cinnamon will merge when I get more time  

[dreamwatcher]

No problem, it works well too , i tested it, with blake coin and photon (but i don't think cce has updated the code yet for Pho)

I will get the patch applied to electron and blake bitcoin in a day or so,

I know Chigulator the dev of UMO likes to do his own updating !!

On Dirac I never did any updates since it's 'developer' is so much more talented than anyone on this team he can handle things himself.

update to blake coin with bugfix as reported by a gitpull (same one on photon also now fixed) fixes an issue with signatures

i built this

https://drive.google.com/file/d/0Bz8503hoyr74QU5vZzRrTmNsTHc/edit?usp=sharing

from this

https://github.com/photonproject/Blakecoin

NOTE, Bluedragon asked me to test and update this , he will merge the gitpull when he has time......

Thanks to all supporters of the blake 256 system

Thanks Cinnamon will merge when I get more time  

CCE should have all the Blake based coins updated, after all it was my patch. If I missed something let me know.

[rupy]

I'm just going to throw this out there, so don't cut my head off!

I think what I meant with the whole CryptoNote idea, was that it would be powerful with a coin that uses this solution to all "Bitcoin" altcoins pseudonym problem AND uses the FPGA for power efficiency = blake hashing algo.

I realize that it's a huuuuge project, but if anyone could do it it would be you guys! And I think with two improvements that coin would probably be far more successful than the current blakecoin?

[BlueDragon747]

I'm just going to throw this out there, so don't cut my head off!

I think what I meant with the whole CryptoNote idea, was that it would be powerful with a coin that uses this solution to all "Bitcoin" altcoins pseudonym problem AND uses the FPGA for power efficiency = blake hashing algo.

I realize that it's a huuuuge project, but if anyone could do it it would be you guys! And I think with two improvements that coin would probably be far more successful than the current blakecoin?

Go talk with the CryptoNote devs rupy or do it yourself this is not the right thread to talk about CryptoNote development  

it is not going to work well on FPGA as you have been informed try it for yourself dont take my word for it

Maybe you dont get the fact its not using the same hashing even though it has blake hash its not the same!!!

your ztex board being ported to Blakecoin and working on the merge pools just not good enough for you  

as far as I am concerned Blakecoin is already very successful as it has met its primary goals of CPU/GPU/FPGA, Merge Mining and use within our MMO games

Bitcoin took years to even get this far(how many pools you know mine Bitcoin and 5 other coins at same time?) so Blakecoin imho is still in its early days it will be 1 year old on 6th October 2014 and I have no plans to stop working on it, many years ahead for adding more features, services and fixing bugs in code maybe this does not make you rich overnight but long term for a working system its fundamental!

I have no plans to ever work on Cryptonote its not going to be easy and I feel sorry for anyone trying to do it as the devs have made it harder for practical FPGA implementations which makes competing with GPU impractical!

I also think kramble made himself quite clear in this post

ok, then it would be interesting if kramble could have a look at just adapting CryptoNote to the zTex?

And why not have world peace and ponies while he's at it? If you refer to the Cryptonight hash that most Cryptonote coins use, it's a combination of a few different hash/encryption functions and it needs a couple of megs of fast cache. It might fit on one of those big-ass FPGAs that cost thousands apiece. Conversely, Blake is a single, relatively simple hash, which is why it's great for practical FPGA implementations. And as BlueDragon747 already pointed out, even that hasn't been quite trivial.

In the software world, it's easy to make bigger and bigger programs for the same CPU/GPU, as long as you have more memory. The CPU is only running a small part of the program at any single time. This is why we've seen crazy PoW solutions like X11/13/15. But when you're doing something in hardware, as in FPGA, you basically have to fit everything on the chip at once. That's why FPGA/ASIC projects run into hard limits more easily than software ones.

Cheers! Couldn't have said it better myself.  

Actually I'm pretty much finished with crypto on FPGA now. It is just not worth the investment of my time (and the frustration, see what Blue said about ISE). I did have a look at a couple of other algos (groestl, keccak) and got initial, rather poorly performing, builds working, but the GPUs perform far better. The only advantage for FPGA is power consumption.

As for X11/X13, I reckon it can be done on a LX150, but only via a soft-CPU optimized for hashing. A huge amount of work for a very poorly performing hasher. So I'm not going there.

Anyway, best of luck rupy.

[gaalx]

No Asik. This will kill the algorithm.

[ahmed_bodi]

Blue could you add any new MM coins to this registry here as and when they're made: https://bitcointalk.org/index.php?topic=769073.msg8668650#msg8668650

Ahmed

[BlueDragon747]

Blue could you add any new MM coins to this registry here as and when they're made: https://bitcointalk.org/index.php?topic=769073.msg8668650#msg8668650

Ahmed

sure no problem will let you know 

[Djinou94]

Whats up ?

[BlueDragon747]

still busy with game dev but I have merged the changes from Cinnamon's fork

hope to have some other news soon 

[jmanak]

Hi, looks like mining transactions for coins other than BLC stopped yesterday.  I'm mining at CG1.  Is there an issue?

[BlueDragon747]

Hi, looks like mining transactions for coins other than BLC stopped yesterday.  I'm mining at CG1.  Is there an issue?

ok will take a look could be an issue with mmp normally dont get much issue with cg1  

Edit:
yeah the mmp had crashed out I did reset it yesterday but it seems to have crashed almost immediately after

I will monitor it a bit better make sure its running for hours