Bitcoin Forum

5000 YAC to whoever implements scrypt-jane on cgminer. Donations are welcome, even better for the donators coz we get to "test drive it for a few days to "make sure its bug free FOR THE COMMUNITY"  ;D ;D ;D ;D ;D

I bet it's already been done, why would anyone want to release that? 5000YAC is a joke of bounty compared to what they could be pulling in every day. It should be trivial to accomplish, I'd have done it ages ago if I didn't have a bunch of final exams next week to study for.

My skills are lacking in the coding section, and i am also not a rich man. ergo i made it a community request. Though if you really were capable of such a feat , i believe you would have done so already due to what you would "rake in".

You should probably offer a coin that's actually worth something ::) Specially since if this became available to the general public, the whole premise of YAC would be defeated, and it would become even more worthless

if i had more of any other coin i'd gladly pay to get first crack at it  :( :( :(

Its not so trivial if you don't have any experience coding OpenCL kernels

Probably people without OpenCL development experience aren't going to be "in the running" for a bounty of this type.



The bounty amount is a bit of a joke, considering the actual number of hours needed to port scrypt+chacha/keccak(N,1,1) to the cgminer kernel and the resulting profitability using it for mining rather than releasing it.  Now, make it a 50 BTC bounty and we'll just see what springs forth..

Is that a bounty (of whatever amount, 5000 YAC is just too low) to whoever implements it in a provable way, or actually releases it?  :)

Pointed here by my buddy. I could do this; but at .0006 BTC per YAC.... is it really worth it?

The problem here is i dont think that OpenCL code for scrypt-jane exists out there. IIRC the kernels for sha256 and litecoin type scrypt was based on pre-existing code developed for other purposes then adapted for mining...

So if someone were to write from scratch, maybe have some influence from litecoin-scrypt, id assume it easily taking up 10 - 20 hours minimum for an experienced OpenCL developer.

1) Now if said developer is into mining, 5k YAC is pocketchange compared to what they get by not sharing.
2) If said developer is not a miner, then ud need to pay a lot more... maybe like  10 - 20 BTC easily. Thats assuming their time to be worth 1 BTC/hour.

So, find person that fits category 1 and cares more about community than personal goal... Then theyd not care much about the bounty anyways.

Having said that i can add in 2k YAC to the cause, to be in your "donators" category... i am not that proficient in C/C++, but i can help with testing early code.

This project needs to be split into 2 tasks:-

1) The cgminer side of things. The side that validates the nonce returned by the kernel. This should be fairly easy, given that the c code for it exists.
2) The OpenCL kernel... this would probably be a lot more complec. Way over my pay grade. Would need some sample test cases to help with development, especially if the developer is non-miner.

BTW - scrypt-jane isn't a hashing algorithm.  It's a software library that supports several different scrypt-based hashing algorithms, including scrypt+Salsa20/8 as used in Litecoin and scrypt+ChaCha20/8 as used in Yacoin.  The library is here:

https://github.com/floodyberry/scrypt-jane (https://github.com/floodyberry/scrypt-jane)

Assuming the OP wants cgminer for Yacoin specifically, a change in the title of the thread is probably warranted, as "scrypt-jane" doesn't refer to the hashing algorithm in Yacoin.  It's ambiguous which scrypt-derived algorithm one is referring to if you say "scrypt-jane".

There is already GPU miners running Yak. It's just such a derpy diff that it's not worth it even running GPU mining when you can just throw together a AWS instance and 51% it for a few $1.000.

Do you have any ideas about the difference from CPU to GPU?

The difference is significant.  Unless you're using a 4-processor Xeon E5-2670 server as the point of comparison.

With AWS instances, it would take way more than a few grand to launch a 51% attack.

Interesting, i assumed scrypt-jane was the algo. </n00bmode>

https://github.com/ckolivas/cgminer/blob/master/scrypt130511.cl#L712

By the way is Yacoin mining with OpenCL almost as simple as swaping out salsa with chacha20?

That's what I was thinking, and also a SHA2 hash needs to be changed to SHA3 i believe. The code in that scrypt cl file is tedious to write, but technically trivial code. It's just mathematical operators to follow the algorithms.

But where is the "N" going in scrypt130511.cl ? I know for litecoin its something static.

I see this many times in scrypt_core

Is 1024 the N of litecoin and thats being hardcoded in there?

Yes, N is hard-coded in the OpenCL source for scrypt(1024,1,1) for Litecoin.  N changes so slowly for Yacoin that you might as well hard-code it as well.  Or #define N to be 32 at the top of the OpenCL file so you can change it to 64 tomorrow with a single line tweak when N=64.  In the long run, to automate this, I'd just modify the cgminer source to read in the .cl file, modify the #define line with the appropriate value of N, write it back out to another .cl file, and use that .cl file as the source for compiling the OpenCL program.

Remember to change the hashing algorithm in the main cgminer source first, since it needs to check the hashes.  If you get it working correctly with cgminer doing CPU mining, and the shares are being accepted by, say, pushpool (or the YAC-modified pushpool over at the yac.dontmine.me pool), you can then move on to changing the OpenCL kernel.  Or solo-mine Yacoin testnet, or make your own genesis block for Yacoin and solo mine off-network with very low difficulty so you can solve blocks quickly.  That way you already have a known-good implementation for the hashing algorithm to check the hashes coming from the GPU.

 ;D

And even in that case, the power consumption difference is massive

I thought you were on FPGA bro, not GPU.

mind sharing the knowledge :P

I started (late, 8.5 hours after coin launch) with a massive server farm while I modified cgminer, then once that was working, I moved on to the Xilinx implementation.  I just got the Xilinx approach (for N=32, anyway) going last night.  I'll reevaluate whether to bother continuing to mess with it when N=64 tomorrow, we'll see whether Yac exchange rates continue dropping.  N=32 was not difficult on the FPGA, it's really not difficult to pipeline a bunch of 32 bit wide processing stages (as opposed to, say, 1024 bits of data width for Litecoin).  N=64 starts getting a little hairier.



Lots of hints already posted in this thread that'll probably point a fair number of people toward where they need to look.  And if not, perhaps more people will have learned about OpenCL in the process, something they might never have otherwise had the fun of playing with.  I don't need the bounty.  But I'm very curious to see which of the people I gave hints to wins the bounty first, or if someone else that already modified cgminer comes forward to collect the bounty.  Personally, I think the bounty is much too low though.

Actually, most of all, I'm curious to see the hash rates the other implementations achieve(d).  I didn't spend a lot of time optimizing, I moved straight on to writing Verilog for the FPGA attempt.

I'm a decent programer but I'm "scared" of looking into openCL because most of my programming is databases, user interfaces, automation etc... not much math involved like all graphics stuff.

What kind of bounty would be worth your time?

Also please don't dump more YAC :P

Thanks for your tips. Will try tomorrow with pyopencl first. Im proficient python but not C ... so ... if i can somehow by magic get ocl kernel to work... i guess the cgminer side of it should be trivial in comparison.

Can you provide some test data?

i.e. some inputs and known nonce for it? That would be real helpful.

well people?

I'm mining with GPU now, works great.
Testing it for 2-3 weeks for stability, then release.

wouldnt u like a "beta " tester alongside you?

+1 willing to donate my time to do some "testing".

I'm afraid it will leak out and kills the difficulty for CPU miners.
Not even sure if I'm releasing it.

How fast is it? Mine is, with N=128, 4MH/s on a core-underclocked (830->738) HD6990.

Adding 200 YAC to the bounty (a small amount for you, not for me), will pay when released. People please add to the bounty or it will go nowhere. ^^

Guys, lol, can't you see you're just being trolled? Gold rush sure has struck here.

i dont mind pre-complied for x64 ubuntu, i want to see the feasibility, and considering the money it would make me, i'd be further willing to put 5 BTC for the source code.

bump
https://bitcointalk.org/index.php?topic=232241.0
 ;D