I know this old miner, it works, but I am curious if in this miner is some optimisations for scryptjane.
It's aready optimized up to AVX2 so it's as good as it gets.
Edit: Upon further analysis of the code scryptjane:18 might work for yac.
When I first ported scryptjane I just did a quick functional test on Nicehash and it worked with default options.
That was good enough and I Ieft it at that. I hadn't noticed that the default NF was 1024 which made no sense
and that Nicehash was NF16.
I'd like to retest at Nicehash with NF16 but the stratum is down due to lack of orders.
I know nothing about scrypt so I have no idea of the effect of the wrong NF. If the wrong NF works
maybe the right one works better.
I'm not that interested in setting up a user on a yac pool just for a quick test but if it works for you I'd
be curious.
Thanks for your response.
-a scryptjane:18 miner say "Unknown algo: scryptjane:18"
-a scryptjane:16 seems to work, but as far I know, there is no coins at NF16 (LEOcoin switched to POS)
to mine scryptjane need to use corect NF for respective coin
Tue, 08 Aug 2017 16:15:28 GMT YAC NF will be 19
http://download.muuttuja.org/yacoin/countdown/ UTC will stay forever at NF 14
Are you sure the miner isn't expecting N instead of NF? So for NF18, maybe you should specify scryptjane:524288 instead (according to the table in the link you provided)
That's part of it. There is inconsistent handling of N vs NF. The command line parser expects algo:n but scyptjane expects algo:nf.
scryptjane:18 fails because it is not a power of 2.
This is not an area I am familiar with so some suggestions are welcome.
NF seems more user friendly than N. Is it a convention to use algo:n notation or is algo:nf acceptible?
Can software reliably distisguish a NF spec from N spec by its value? For example if the value is not a power of 2 and
is smaller than some limit it is interpreted as NF, else N. What would be that limit?
Any personal preferences on how to handle it? -a algo:nf or -a algo -n nf
I still don't understand why the default NF=1024 worked on Nicehash (Leo). This was actually interpreted as NF=2.
As far as I know scryptjane is not scrypt:n, is not only to change N, is different algoritm, in scryptjane algo in miners need to put some aditional parameters --starttime --nfmin and --nfmax, to automaticaly calculate NF, but in some miners is manual you need to put NF --scryptjane:NF.
In Nicehash miner v1.3.0.3 (cpuminer_x64_AVX.exe) scryptjane algo work corect with -a scyptjane:NF, (tested with YAC -a scryptjane:18)
I mined LEO at NF 16 and before NF 15 ... 14..., but with GPU. If I put cpuminer with -a scryptjane (NF16) to YAC (NF18) miner work but submited shares is rejected.
