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.