Let me ask you this: did it come from BinaryTriStar?

He was going to build an FPGA for us, and that was exactly his suggestion.

Either way, he completely dissapeared but that's old, dead history.  Just was curious.

I woudn't even consider letting these things out into the wild until viable competing devices show up.

If you folks truly have what you say you have, i hope you have a serious fab contract. 

Negative.  The logic would be radically different between a Litecoin-oriented Salsa20/8 (1024,1,1) implementation and a YACoin-oriented ChaCha20/8 (N,1,1) + Keccak512 implementation.  There is very little similarity between the scrypt variant used in Litecoin and the scrypt variant used in YACoin.  Additionally, YACoin uses variable N while Litecoin has fixed N=1024.  For YACoin, N is currently 32768, and will change to 65536 on 31 May 2014.  Details on the variable N schedule can be found in my post here:

https://bitcointalk.org/index.php?topic=206577.msg2162620#msg2162620

When YACoin launched at N=32, I adapted 4 of our earlier FPGA LTC prototypes (populated with XC7A200T's and a pile of DDR3) to YACoin instead.  It was real easy pickings at N=32.  At N=64, not so much.  At N=128, I stopped and moved back to a different more efficient hardware solution for YACoin mining.

Variable N would make ASIC implementation a real bitch, since you can't optimize the mixing function's logic for a specific value of N like you can with Salsa20/8 (1024,1,1).

Just playing devil's advocate here, but I'd tend to say that a team capable of reverse-engineering an ASIC by selectively etching layers and taping-out a replica, already has the skillset to just develop an scrypt core from scratch.  Given that scrypt's internal workings aren't secret knowledge, and the possible hardware approaches to go about it are generally self-evident and well-documented from scrypt research outside of the cryptocurrency community, I think it would take less time to implement from scratch rather than reverse someone else's design.  If we were talking about replicating, say, Sandy Bridge, or some of AMD and Nvidia's GPU dies, that would be one thing.  But an ASIC implementation of scrypt just isn't that hard to do from scratch.  95% of other cores that end up in various ASIC's across other industries are significantly more complex than an scrypt core.

I'd say any team with the knowledge needed to reverse an ASIC, can probably also easily determine the appropriate TMTO and SRAM size (or external DDR3/GDDR5 size) for the particular silicon process node they're targetting to optimize cost/performance (and, really, there's only 2 choices along the TMTO spectrum that are going to land near the peak cost/performance for an ASIC implementation with on-die SRAM, and only 1 optimal TMTO choice for external DDR3 or GDDR5).  I don't see where there's much to gain in anyone's ASIC development cycle from looking at someone else's scrypt die.

I guess that means the same ways we all use for reverse engineering of ASICs.

That is a cruel world we live in, isn't it?

LMAO! - That is awesome...

Sorry if this has been asked before, but will it work with Scrypt-Jane, such as YaCoin?
Thanks,
Flippyfeet

FPGA scrypt mining was known already. It was less profitable in comparison to GPUs. With Your intention of not selling "scrypt ASIC" one can start being suspicious that at the beginning You will sell expensive shares of actualy GPU farms.

caught my attention! is there an estimate of how much hashing power these will have per unit yet?

I think your right, maybe unthinkingbit needs to assign an official branch. Well when he pushes the walletnotify to the git, which version do you think it best to push to currently?

My version of the code is supposedly not to be the "current" version going forward, so any pushes / patches / etc ought to go to the currently in development version, though I am not even sure who is developing that or even if there is only one candate version for that. (Weren't at least two diferent "new versions" being worked on by different people or teams?)

-MarkM-

There's no support for walletnotify? Where can i push a patch for it?