XHV Haven Compatability

[mdgross]

Hello-

Could you please make the proxy compatible with Haven XHV?

Thanks!

[bobbieltd]

Hi ! What error do you have when you use “coin” : “cryptonightheavy” with XHV ? For remind, XNP (xmr-node-proxy) only works with nodejs-pool (look at pool website footer, powered by nodejs-pool).

[untoreh]

I have tested on 2 different pools and the proxy returns bad diff share, it fetches the block template correctly but it returns bad shares

[bobbieltd]

Can you provide the pool names so I can test by myself ?

[untoreh]

tried on haven.miner.rocks and haven.minercartel.com

[bobbieltd]

haven.miner.rocks : It's not nodejs-pool (look at footer of website). No test. haven.minercartel.com : It's nodejs-pool. Quick test : OK.

You should double check your workers' config. Try with one or two workers at first. If there is still bad shares, I need more info. I don't use this algo and have no workers on this.

[untoreh]

I'll try again minercartel.com, but haven.miner.rocks has even a link to this github repository in the headers :) so it is weird

[bobbieltd]

miner.rocks uses forked zone117x’s repo. By coding design, XNP can not work with (even if we want to). You can try xmrig-proxy which works with all pools. But in my knowledge, there is no advantage to use xmrig-proxy except to switch workers from one pool to another. It doesn’t reduce difficulty.

[untoreh]

@bobbieltd I tested with this configs and it keeps getting bad shares, also started with --workers 1 on a fresh install:

{
    "pools": [
        {
            "hostname": "haven.minercartel.com",
            "port": 3333,
            "ssl": false,
            "allowSelfSignedSSL": false,
            "share": 100,
            "username": "putanaddress",
            "password": "xnp",
            "keepAlive": true,
            "coin": "cryptonightheavy",
            "default": true
        }
    ],
    "listeningPorts": [
        {
            "port": 8490,
            "ssl": false,
            "diff": 5000,
            "coin": "cryptonightheavy"
        }
    ],
    "bindAddress": "0.0.0.0",
    "developerShare": 1,
    "daemonAddress": "127.0.0.1:18081",
    "accessControl": {
        "enabled": false,
        "controlFile": "accessControl.json"
    },
    "httpEnable": true,
    "httpAddress": "0.0.0.0",
    "httpPort": "8480",
    "addressWorkerID": false,
    "minerInactivityTime": "300",
    "coinSettings": {
        "cryptonightheavy":{
            "minDiff": 5000,
            "maxDiff": 300000,
            "shareTargetTime": 15
        }
    }
}

{
    "algo": "cryptonight-heavy",
    "aesni": 1,
    "threads": 4,
    "force-pow-version": 0,
    "multihash-factor": 1,
    "multihash-thread-mask" : "0x0",
    "background": false,
    "colors": true,
    "cpu-affinity": "0x0",
    "cpu-priority": null,
    "donate-level": 0,
    "log-file": null,
    "max-cpu-usage": 100,
    "print-time": 360,
    "retries": 5,
    "retry-pause": 5,
    "safe": false,
    "syslog": false,
    "pools": [
        {
            "url": "127.0.0.1:8490",
            "use-tls": false,
            "user": "test",
            "pass": "pass",
            "keepalive": true,
            "nicehash": false
        }
    ],
    "api": {
        "port": 8089,
        "access-token": null,
        "worker-id": null,
    }
}

[bobbieltd]

Botnets / Hidden mining sponsored by xmrigCC ? It's bad idea to mine cryptonight-heavy with CPUs. You can try to point directly to the pool (without proxy) to test if it works. Under my new test, xmrigCC did not to work with Haven (bad shares). If you are using it, it won't work (with or without proxy). You can try xmrig 2.6.x

[untoreh]

Tried also with xmrig and still gives bad shares, yes direct pool always worked, it's just the proxy that doesn't with haven, it works with sumo though! Anyway you are right that cryptonight-heavy is not worth mining since both sumo and haven have too huge centralized pools. I was just testing in case someday they decide to do something about it.

[bobbieltd]

It is weird. I guess the autoswitch algo with Sumokoin doesn’t work with haven (different block version). The mining software messes up with old cryptonight (it thinks it is old Sumokoin ). With latest xmrig, I don’t see bad shares. xmrigCC causes bad shares. Nothing is wrong with huge centralized pools. It is amusing saying on miners’ side and some idiot or hypocrite pool owners. 51% attack is not easy to carry out ( and only irrational people will do that ). With small coins, you can rent 51% hashing power easily. Botnets / hidden free mining are wrong but we are living in imperfect world. Even big corporations are doing dirty tricks to gain more profits.

[untoreh]

i don't know i get same results with latest xmrig bad shares both variant 0/1. On which pool are you testing? also do you wait for the pool to register a valid share? From my end the proxy is not even recognized as a miner in the pool miners list

[bobbieltd]

minercartel + my xmrig compiled by myself. His pool put min diff 1000 and I have only a shit CPU tp test. Everytime I test, I need to wait quite a long time. When you kept saying bad shares, I tested xmrigCC and it didn’t work (with or without proxy). I guess it is because of mining software. I will test it again when I have free time (heavy = really heavy with me).