[JCE]Fast & stable CN/v8/Heavy/Tube/XHV miner, CPU+GPU, Vega56 1800+ RX580 1200+

[saewone]

2nodes 4 x 6267

[saewone]

--variation 3 works fine but just 3% fast than xmrig
--variation 4 has a problems
Rejected by the pool.
Message from the pool: Low difficulty share
--variation 4 280% fast than xmrig
I want use --variation 4

[JCE-Miner]

--variation 3 works fine but just 3% fast than xmrig
--variation 4 has a problems
Rejected by the pool.
Message from the pool: Low difficulty share
--variation 4 280% fast than xmrig
I want use --variation 4

Seems we misunderstood : variation is not the xmrig term, where it means "dualhash" or not.
on JCE the variation is the algo fork.

Code:

    N=1 Original Cryptonight
    N=2 Original Cryptolight (for AEON)
    N=3 Cryptonight V7 fork of April-2018
    N=4 Cryptolight V7 fork of April-2018
    N=5 Cryptonight-Heavy

4 is super fast because it's cryptolight, twice less computation to do.
the best you can do is --variation 3 with AES 64-bits, with +3% perfs. Even fees deduced, that's still the most efficient miner for CPU so far.

And it still need to fix it

[carlosmonaco]

Working perfectly but :

https://www.virustotal.com/fr/file/b9cf92c59ab73038afffb9a1a5bfb4539a90b24b5926881a5af29d852038e1cd/analysis/1523997467/

[JCE-Miner]

I'm preparing version 0.24a, a hotfix of the 0.2x

Code:

Fixed bad shares (finally, i hope...)
IPBC good auto fork (0.24 badly chose v7, while IPBC is CN-classic)
Better autoconfig for CPU with 3M cache (defaults to 2 threads, which is better)

Virus, trojan, backdoor... nope, absolutly nothing malicious in JCE, it's a miner, period. I don't even try to know how many people use my miner, to mine what, where, or anything. Not a single byte is written to your disk (except log (default=disabled) of course, and Large Page autoconfig when needed) nor sent to anybody, except to mine coins on pools.

But that's fair: all miners are detected as virus/trojan : stak, claymore... jce is no exception.
Note the attrib trick to be stealthier, on purpose. That's a documented feature, in case you wonder. See bottom of first post.

edit 0.24a online
I found a huge bug in Cryptonight Heavy SSE2/3 x64 (but was ok on SSE4 and AES, and 32bits)
I reverted the netcode changes since 0.20, except the 64-threads max limit, still 64

[nsummy]

that parameter already exists: --variation
please read first post or github page

Correct but the parameter is pointless if you want to mine one of the supported algos but the coin doesn't show up in the list of supported currencies.  A wallet format that the miner doesn't recognize shouldn't prevent the use of miner.  Most pools won't even let a miner connect if they are using an invalid address.

[JCE-Miner]

Correct, you're not the first to point out that issue, my argument is that the coin detection allows to choose the fork automatically and format good log, and provide a good error in case of bad wallet, because forwarding the check to the pool may pass for a jce netcode bug, and i want to avoid getting reported such wrong bugs.

If the pool doesn't report the bad wallet, it may occur, and the miner guy never gets his coins, i don't want to be accused to have stolen them.

Also the cryptonote coin list is not infinite and i add them quickly on demand. If your coin is not listed yet, just ask

I'm thinking about adding the "unknown coin" to handle them all, but i'd rather prefer making a complete list and keep the mandatory checking.

btw i've let jce 0.24a mine all day, on nicehash and normal pool, both zero bad shares so far.

[Lonnegan64]

IPBC good auto fork (0.24 badly chose v7, while IPBC is CN-classic)

IPBC still not working. The forked coin is not CN-classic! The hashrate of the official ipbc-miner indicates, that it is Cryptonight-lite, but it is neither CN-lite-AEON, nor CN-lite-V7. It must be something else 

And AMD FX-8350 is detected as Kuma instead of Vishera. Besides, the code the miner uses with auto is generic_sse3. When I set the CPU to vishera manually, it uses generic_aes.
With SumoCoin (Cryptonight-Heavy) the miner chooses 2 threads for AMD FX-8350, reaching ~115 H/s. But since FX has exclusive cache architecture with 4x 2 MB L2 + 1x 8 MB L3, it is better so use 4 threads to fill both cache levels. Then the FX-8350 reaches 216 H/s with CN-heavy.

[nsummy]

I mean its your software, so you can do as you please, but I think you should offer a flag to override this.  The coin I am referring to is SuperiorCoin.  Its listed on coinmarketcap and has been around for nearly a year, yet I can't use your miner because of a wallet address.  And if a new coin comes out we will be at the mercy of you to issue an update.  Also there are flags that you mention on the github page that do not appear in the built in help command.

[shiroocrypto]

I mean its your software, so you can do as you please, but I think you should offer a flag to override this.  The coin I am referring to is SuperiorCoin.  Its listed on coinmarketcap and has been around for nearly a year, yet I can't use your miner because of a wallet address.  And if a new coin comes out we will be at the mercy of you to issue an update.  Also there are flags that you mention on the github page that do not appear in the built in help command.

Dev has been very friendly with adding coin support though.

Maybe if one helped him via donations then he'd be open to flags on his closed source software. I think it's perhaps unfair to profit off of something/someone and you're not willing to invest in the guy.

I went through the same thought process, but upon reflection that's the conclusion I came to. Just my 2 sats.

[Ayuluv2001]

Hi mate am currently using 0.23 and it seems there is an issue of logging in as well as invalid shares
I am mining XMR

May I know how can i resolve it? Thanks in advance

[JCE-Miner]

Hi mate am currently using 0.23 and it seems there is an issue of logging in as well as invalid shares
I am mining XMR

May I know how can i resolve it? Thanks in advance

Please update to 0.24b, and provide the first lines of log that jce outputs. Of course you can anonymize your wallet in the log.

The coin override flag sounds a good idea, i could allow that and make the --variation param mandatory in such case, so the fork config belongs to the user.

IPBC is strange, is that a coin that change fork at every hash ? I tested it good with v7 then CN-classic, and now i get bad shares again. It probably change often. In such case, it would need a very special code that i don't have time to do yet

And AMD FX-8350 is detected as Kuma instead of Vishera. Besides, the code the miner uses with auto is generic_sse3. When I set the CPU to vishera manually, it uses generic_aes.

Ok it's a bad bug , will check this, thanks

Meanwhile, SuperiorCoin to be added

[JCE-Miner]

0.24b online

Code:

* Added SuperiorCoin
* Added EDollar
* Added Masari
* Removed Interplanetary (coin with dynamic PoW, not handled by JCE)
* Netcode fixes, should fix last cases of pool errors and bad shares
* AMD cpu detection fixes

CPU detection not tested because i've no Vishera CPU
This version invalidates all previous versions.

[nsummy]

Hi mate am currently using 0.23 and it seems there is an issue of logging in as well as invalid shares
I am mining XMR

May I know how can i resolve it? Thanks in advance

Please update to 0.24b, and provide the first lines of log that jce outputs. Of course you can anonymize your wallet in the log.

The coin override flag sounds a good idea, i could allow that and make the --variation param mandatory in such case, so the fork config belongs to the user.

IPBC is strange, is that a coin that change fork at every hash ? I tested it good with v7 then CN-classic, and now i get bad shares again. It probably change often. In such case, it would need a very special code that i don't have time to do yet

And AMD FX-8350 is detected as Kuma instead of Vishera. Besides, the code the miner uses with auto is generic_sse3. When I set the CPU to vishera manually, it uses generic_aes.

Ok it's a bad bug , will check this, thanks

Meanwhile, SuperiorCoin to be added

I believe this is the code that shows you the difference between IPBC and Cryptonight:  https://github.com/ipbc-dev/ipbc-miner/commit/93fb121a19626e0c1b9dac9a0e2af73072be9fea      its actually a modification of cryptonight-light.  It forked on Monday:  https://www.reddit.com/r/ipbcoin/comments/8cms2s/ipbc_has_now_forked_at_block_54900_all_you_need/

The devs created an xmrig fork to mine it, would be nice to have a 2nd option

[JCE-Miner]

yeah, just read the code, that's Cryptolight-v7 plus a subtle change. easy to do, even in assembly. will be in next version, as --variation 6
thanks for the guide !

[KriptoGuruTR]

AMD Phenom(tm) II X6 1100T Processor
Architecture codename: Thuban
  SSE2          : Yes
  SSE3          : Yes
  SSE4          : No
  AES           : No
  AVX           : No

Found CPU 0, with:
  L1 Cache:    64 KB
  L2 Cache:   512 KB
  L3 Cache:  6144 KB, shared with CPU 1, 2, 3, 4, 5
Found CPU 1, with:
  L1 Cache:    64 KB
  L2 Cache:   512 KB
  L3 Cache:  6144 KB, shared with CPU 0, 2, 3, 4, 5
Found CPU 2, with:
  L1 Cache:    64 KB
  L2 Cache:   512 KB
  L3 Cache:  6144 KB, shared with CPU 0, 1, 3, 4, 5
Found CPU 3, with:
  L1 Cache:    64 KB
  L2 Cache:   512 KB
  L3 Cache:  6144 KB, shared with CPU 0, 1, 2, 4, 5
Found CPU 4, with:
  L1 Cache:    64 KB
  L2 Cache:   512 KB
  L3 Cache:  6144 KB, shared with CPU 0, 1, 2, 3, 5
Found CPU 5, with:
  L1 Cache:    64 KB
  L2 Cache:   512 KB
  L3 Cache:  6144 KB, shared with CPU 0, 1, 2, 3, 4

Preparing 6 Mining Threads...

+-- Thread 0 config -----------------------------+
| Run on CPU:             0                      |
| Use cache:              yes                    |
| Assembly module:        generic_sse3           |
+------------------------------------------------+

133 h/s average monero in 18 hours, no idea about power, 0.24b. CPU is overclocked 19.5 x 200 MHz.

Thanks

[JCE-Miner]

@JCE-Miner

It will be nice to see a total hashes / uptime when I press R key.

So far so good, a nice addition to my GPU rigs. Thanks

in case you didn't notice, I added that feature, and i love it!

[Lonnegan64]

* AMD cpu detection fixes

CPU detection not tested because i've no Vishera CPU

Detection now works perfekt, FX-8350 is detected as Vishera and uses generic_aes automatically.

But the miner still uses just 2 threads with SumoCoin (Cryptonight-Heavy), ending up at only 115 H/s. Forcing the miner to use 4 threads to fill L2 and L3 cache completely results in 219 H/s 

[JCE-Miner]

right, i didn't want to fix all bugs the same time, to avoid another bad share fiasco like the 0.22. need to take more time to test each release.

next dev is ipbc variation and exclusive cache detect.
dualshare still pending

thanks for the feedback

[UnclWish]

On my i3 on my work 32-bit no-EAS miner finds shares, but they are go away to nowhere.
Pool didn't show finded shares...
Thats the screen: