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

[JCE-Miner]

proxy/socks : possible, but i've tons of other tasks more priority : dualshare, Linux version, AMD-GPU version...
JCE netcode works the exact same way than claymore, its netcode is optimized (and restricted) to direct-connect to pools on internet, with or without SSL. Period. No support of proxies, socks, local pools etc. Not even it has a HTTP server to broadcast hashrate, just log file at best. But it can run on a VM.

And even if i add proxy support, i'd like to provide integrated proxy support (JCE being proxy of other JCEs) because i don't like how xmrig-proxy is made, it re-uses the (bad) way Nicehash implement their own proxies, and so xmrig-proxy is not compatible with Nicehash, and not compatible with non-Nicehash miners.

Wallet does not match any of the supported currencies.

Again, what coin/pool did you want to mine? Don't give wallet, just pool/hash-marketplace and coin. I'm adding them on the fly when requested.

[l0adr]

It's cryptonight-heavy algo.

[JCE-Miner]

It's Haven, cryptonight-heavy algo.

Ok, i add it. Nice another Heavy coin . JCE is a lot better than others on Hevay non-AES, and 32-bits, but barely better on AES-64. That's the case i'm the less better on Ryzen, 252 (jce) against 250 (xmrig). Difference barely noticeable. And probably i'm worse on modern Intel

Update:
Mining with a Pentium G3460.
two cores / threads are used in low intensity, it let the miner in auto config.

Results:
- pool is Stellite miner rocks
- coin in Stellite (XTL)
- average hashing speed from the software is around 51H/s
- average hashing speed from pool is updating
- power draw is 22w at the wall.

Thanks for the feedback, yet another limited CPU that is still faster with 2 threads than 1 thread + dual mine. I'm wondering if i should drop the dual mine feature, looks it's good only on the Conroe CPU

edit:
i'm adding blueberries coin support. Looking at their site:
http://berrycoin.xyz/

Did they time travel from 1997 ? It was a long time i hadn't seen such a retro Web 1.0 site. Cannot tell if it's deliberately retro or retard. Btw, i add support...

[JCE-Miner]

0.23 online

Code:

more coins:
Haven (XHV) automatic switch to CN-Heavy
FreelaBit (FBF)
BlueberriesCoin (BBC)
B2BCoin (B2B)
Bitsum (BSM)

[Iamtutut]

Only changes are new coins ?

I have huge swings in hashrate, due I think to the low load setting on the CPU. But it's okay, I'm doing it for fun. With the current price of stellite, it's unprofitable by a few cents a day.

Would you have reports on Ryzen 5 2400G hashrate? It should be my next CPU.

[JCE-Miner]

I plan to buy one too, to use it as a test base for the gpu version. They're cheap, and their motherboards too. Would be nice to have a hybrid miner. I know it sounds like xmrstak, but they use a separate frontend/backend code, with both back end cpu and gpu stolen from Wolf0. I'll do something completely different.

No benchmark yet sorry, but probably the same as normal ryzen : +1% on cn-classic, +2.7% on v7 and less than +1% on heavy. Take version 0.22+ they have a light assembly optim for v7, slightly faster than 0.1x

Edit : Yeah 22 and 23 differ only by coin list. No other change.

[assa777]

Can you add an IPBC coin ?

[shiroocrypto]

i'm adding blueberries coin support. Looking at their site:
http://berrycoin.xyz/

Did they time travel from 1997 ? It was a long time i hadn't seen such a retro Web 1.0 site. Cannot tell if it's deliberately retro or retard. Btw, i add support...

You forget about the comic sans font too lol. But yeah, just taking a risk with that coin which may/may not pay off.

Thanks for the v0.23 updates! Will try it out a bit later

[Ayuluv2001]

Lynfield detect should be fixed in 0.21+, but I couldn't test since I don't own one. Same for the avx detection. My cpu detect really need fixes, even if it's not blocking, and your can override manually with --archi parameter.

B2BCoin to be added ok. I'll add freelabit too.

The hashrate is very sensitive to pc activity. On a rig, it tends to be stable, but on a real life pc It will drop even when you scroll your files. Jce never runs at high priority, even without --low. if you run it on a pc with no other software running, windows update, Superfetch, and Al. disabled, hashrates should be max and stable.

May launch it without --low with

Code:

start /HIGH jce....

To give it high priority

Edit: Jce GPU exists as a prototype, I mine with it on my rx500, but absolutely not ready for diffusion yet. In opposition to other miners, I did not reused Wolf0 opencl, but wrote a brand new one (but still in opencl, not CGN assembly). Wolf0 code contains goofs so blatant that it's funny... I beat it on every gpu, but not always Claymore, which is faster, just Claymore 10+ tends to generate a lot of bad shares while 9.7 was a masterpiece of quality. What happened to Claymore ? And 11.3 is the giveup version, it's free but no longer maintained.

Tell me if you're interested into a jce amd, I may finish it and release.

Thanks alot mate Nice job to be honest! Btw I do get invalid shares with 0.21 and 0.23 as well today. It does not happen previously. Do I need to make few changes?

[Dmitry69]

If your coin is missing, just ask and I add it.
Now compiling 0.22 with exactly the same request : to add CrepCoin and PluraCoin. And MiningRigRentals.

Edit : done, 0.22 online

MiningRigRentals support

Now NtgthMiningRigRentals is connected without error messages, but the share does not accept, there is a re-link with the pool.

16:16:04 | Connected to pool. Now logging in...
16:16:05 | Successfuly logged as Dmitr69.545657
16:16:05 | Pool changes Difficulty to 25000.
16:16:11 | Hashrate Thread 0: 34.57 h/s
16:16:11 | Hashrate Thread 1: 35.88 h/s
16:16:11 | Hashrate Thread 2: 36.49 h/s
16:16:11 | Total: 106.94 h/s
16:17:02 | Pool changes Difficulty to 17241.
16:17:05 | Pool sends a new Job.
16:17:33 | Pool sends a new Job.
16:20:02 | Pool changes Difficulty to 5109.
16:20:29 | Thread 2 finds a Share, value 5109
16:20:29 | Connection failed: Socked receive error: socket explicitly closed by the pool
16:20:29 | Connection interrupted, waiting 5s then retry.
16:20:34 | Connecting to mining pool eu-ru01.miningrigrentals.com:3333 ...
16:20:34 | Connected to pool. Now logging in...
16:20:35 | Successfuly logged as Dmitrii.83858
16:20:35 | Pool changes Difficulty to 25000.

[JCE-Miner]

IPBC Coin to be added, noted

About miningrigrentals, try force v7 with --variation 3

Invalid shares : What mode ? What coin ? Aes or not, 32 or 64 bits ? The first few lines of the log would help
Assembly code is fragile, no compiler to check syntax, very possible I broke something

[Dmitry69]

About miningrigrentals, try force v7 with --variation 3

Thanks, it works.
coin - xmr, x64

[JCE-Miner]

Nice !
I note to autoswitch miningrigrentals to v7 in next release.
I've been reported broken hashes when using Nicehash on 0.21+, now testing...

edit : done 0.24 online

Code:

IPBC support (v7)
MiningRigRentals autoswitch to v7
Blind fix for Nicehash, better update if you use 0.21+

[UnclWish]

Please make low power mode - double threads.

[saewone]

My miners  4xOpteron 6276 128 cores
Very Fast
BUT Allmost
Rejected by the pool.
Message from the pool: Low difficulty share
Sometimes Accepted
So same as not work.

[JCE-Miner]

Mmh... so i really broke Something, can you copy me the first lines of log so i see what assembly is broken ?
and whether you use Nicehash or not.

i add a warning on first page. thanks for reporting

double threads on the way but need to fix the bad hashes first

edit : i revert release to 0.20 until i fix the regression, please retry with 0.20, it should be fine, just don't use dualthread mode (which is pretty useless, btw)

[Lonnegan64]

And I think you have to look at the IPBC code, as well. Shares get rejected immediately.

[ingvarfervent]

And I think you have to look at the IPBC code, as well. Shares get rejected immediately.

because IPBC don`t use "IPBC support (v7)" it is ultra heavy algo, but hash like cryptonight lite and only ipbc now have that cryptonight algo 

[nsummy]

Seems like this miner has the same issue that the Claymore miner used to have (or maybe still has it, not sure):  It maps the algo based on the wallet address you are using.  I think there should be an option to manually specify the algo you want to use.  I am trying to mine a coin based on cryptonight v7 but it is failing to even start because the miner doesn't recognize the address.

[JCE-Miner]

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

currently investigating the regression

edit:

My miners  4xOpteron 6276 128 cores
Very Fast
BUT Allmost
Rejected by the pool.
Message from the pool: Low difficulty share
Sometimes Accepted
So same as not work.

Seems that's the increase from 32 to 64 max threads that broke everything, the bug being more or less bad if you have a lot of threads. 128 threads (probably 2x64) is certainly the worst case. Still investigating more.