Hi,
Keep on mining and support the devs! Make a donation for the release of much faster NeoScrpyt miner for NVIDIA GPUs: https://bitcointalk.org/index.php?topic=1317772.0
p.s.: this should also be supported directly by the feathercoin maintainers/team.
Best regards,
NiceHash.
OK, here is little help from us (the NiceHash.com team): we just released a new version of our NiceHash Miner, which also includes extremely highly optimized sgminer NeoScrypt version. This version is also tested on all new versions of AMD Drivers. So hopefully by using this sgminer (see …\bin\sgminer-5.2.1-general in the NiceHash Miner package) will help to secure Feathercoin and NeoScrypt mining.
More information: https://www.nicehash.com/index.jsp?p=news&id=56
Best regards,
NiceHash team.
@Wellenreiter please contact us to [email protected] … we might have a solution for NeoScrypt issue if we can work together. Thanks.
ad 1. Why is Scryt even related to this? Scrypt is ASIC, nobody cares about Scrypt on GPUs.
ad 2. Nothing works, not the pre-compiled bins neither if you try to compile with latest drivers.
This is a major flaw for Feathercoin.
Hi,
Keep on mining and support the devs! Make a donation for the release of much faster NeoScrpyt miner for NVIDIA GPUs: https://bitcointalk.org/index.php?topic=1317772.0
p.s.: this should also be supported directly by the feathercoin maintainers/team.
Best regards,
NiceHash.
OK, here is little help from us (the NiceHash.com team): we just released a new version of our NiceHash Miner, which also includes extremely highly optimized sgminer NeoScrypt version. This version is also tested on all new versions of AMD Drivers. So hopefully by using this sgminer (see …\bin\sgminer-5.2.1-general in the NiceHash Miner package) will help to secure Feathercoin and NeoScrypt mining.
More information: https://www.nicehash.com/index.jsp?p=news&id=56
Best regards,
NiceHash team.
@Wellenreiter please contact us to [email protected] … we might have a solution for NeoScrypt issue if we can work together. Thanks.
ad 1. Why is Scryt even related to this? Scrypt is ASIC, nobody cares about Scrypt on GPUs.
ad 2. Nothing works, not the pre-compiled bins neither if you try to compile with latest drivers.
This is a major flaw for Feathercoin.
Hi,
NeoScrypt (and thus Feathercoin) mining broken in Windows sgminer with latest AMD Drivers (Crimson 15.12). Even if one includes amdocl.dll from previous AMD Driver version, mining is still broken. This is bad for Feathercoin. Will Feathercoin developers hire a developer to fix sgminer NeoScrypt kernel to be compatible with newer AMD Drivers?
Hi,
NeoScrypt (and thus Feathercoin) mining broken in Windows sgminer with latest AMD Drivers (Crimson 15.12). Even if one includes amdocl.dll from previous AMD Driver version, mining is still broken. This is bad for Feathercoin. Will Feathercoin developers hire a developer to fix sgminer NeoScrypt kernel to be compatible with newer AMD Drivers?
Forgot to mention; if you do not have a mining rig and would like to mine some FeatherCoin, you can do it here now: https://nicehash.com
We found a programmer and he finished the job. Actually it took as a bit longer to implement proper validator because we were testing on cgminer-neoscrypt 3.7.8 and only today figured out that the issue is with the extranonce bug in cgminer-neoscrypt 3.7.8 … it is a pity that developers took such an old buggy version of cgminer for neoscrypt implementation … anyway, the implementation in the latest sgminer-5.0-develop is OK (https://github.com/sgminer-dev/sgminer/tree/develop).
The job is basically fairly simple. You need to provide a function, coded in C (copy-paste & merge code from existing miners, for example cpuminer-multi - https://github.com/wolf9466/cpuminer-multi, or [https://github.com/vehre/neo-gpuminer)][1] which takes input parameters from stratum (prevhash, coinbase, merkleroot, ntime, extranonce1&2, nonce,…) and returns share diff (double). We would include this function in our stratum-proxy server, used to validate shares for NeoScrypt algorithm. The code must compile under VS2010 (32bit mode C, not C++).
Here are the list of input parameters:
params[] = Hash of previous block. Used to build the header.
params[] = Coinbase (part 1). The miner inserts ExtraNonce1 and ExtraNonce2 after this section of the coinbase.
params[] = Coinbase (part 2). The miner appends this after the first part of the coinbase and the two ExtraNonce values.
params[][] = List of merkle branches. The coinbase transaction is hashed against the merkle branches to build the final merkle root.
params[] = Bitcoin block version, used in the block header.
params[] = nBit, the encoded network difficulty. Used in the block header.
params[] = nTime, the current time. nTime rolling should be supported, but should not increase faster than actual time.
params[] = ExtraNonce 2
params[] = nonce
We can send existing validators (C source files) where problem is already resolved for other algorithms (Scrypt, SHA…) - contact us via PM or @ [email protected] if you are interested.
Of course you must test your function with some example shares - your algorithm should return the same diff as it is received, for example, by cgminer: [https://www.nicehash.com/docs/upload/neoscrypt-cgminer-printscreen.png][2]
If you know the guy that implemented this stuff into the cpuminer itself or some other programmers, that contributed to NeoScrypt algorithm, please forward them this job description.
Contact us via PM or @ [email protected] if you are interested.
Thanks.
[1]: https://github.com/vehre/neo-gpuminer)
[2]: https://www.nicehash.com/docs/upload/neoscrypt-cgminer-printscreen.png
Is there nobody? 5 minutes of work for someone who knows what exactly is changed in regard to Scrypt…