Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: Elmit on August 14, 2014, 05:34:54 AM



Title: Auto swtiching - Auth error
Post by: Elmit on August 14, 2014, 05:34:54 AM
I am trying to use autoswitching!

Node shows me that it wants to use another coin, but then says it is not authorized.

Quote
2014-08-14 13:30:21 [Switching] [Connect] (Thread 1) Connection to switch2 from 1.2.3.4 on 4444 routing to bottlecaps
2014-08-14 13:30:21 [Pool]      [bottlecaps] (Thread 1) Unauthorized  LeJZH5ZpD2F9o3FLEj7WpBodkW5x3wAZ6U:x [1.2.3.4]

I miss a link in my thinking ;-)

If I mine LTC    I use a LTC address   in my miner.  Pointing to the LTC port and it works fine.
If I mine xxx    I use a xxx address  in my miner. Pointing to the xxx port and it works fine.

If I use autoswitching with the LTC address it works till it wants to switch, then I get above quote.

How would I need to use it?


Title: Re: Auto swtiching - Auth error
Post by: Elmit on August 14, 2014, 12:43:05 PM
I came a big leap further ;-)

I found on http://pool.kryptochaos.com/mining_key   how to create the address.
This address now works even when it switches to another coin.

However, how do I handle that? Where are the awards going to? How can I check it?
If you know of a guide, please give me the link!


Title: Re: Auto swtiching - Auth error
Post by: Elmit on August 15, 2014, 06:19:06 AM
I got another problem, autoswiching died:


Quote
TypeError: Cannot call method 'hasOwnProperty' of undefined
    at /home/ronald/nomp/libs/profitSwitch.js:452:36
    at Array.forEach (native)
    at /home/ronald/nomp/libs/profitSwitch.js:450:51
    at /home/ronald/nomp/node_modules/async/lib/async.js:610:21
    at /home/ronald/nomp/node_modules/async/lib/async.js:249:17
    at iterate (/home/ronald/nomp/node_modules/async/lib/async.js:149:13)
    at /home/ronald/nomp/node_modules/async/lib/async.js:160:25
    at /home/ronald/nomp/node_modules/async/lib/async.js:251:21
    at /home/ronald/nomp/node_modules/async/lib/async.js:615:34
    at /home/ronald/nomp/libs/profitSwitch.js:407:25
2014-08-15 14:16:28 [Master]    [Profit] Profit switching process died, spawning replacement...

How can I fix that?


Title: Re: Auto swtiching - Auth error
Post by: Elmit on August 15, 2014, 05:12:43 PM
My portal config parts for switching are:

Quote
    "switching": {
        "sha256": {
            "enabled": false,
            "algorithm": "sha256",
            "ports": {
                "3333": {
                    "diff": 10,
                    "varDiff": {
                        "minDiff": 16,
                        "maxDiff": 512,
                        "targetTime": 15,
                        "retargetTime": 90,
                        "variancePercent": 30
                    }
                }
            }
        },
        "scrypt": {
            "enabled": true,
            "algorithm": "scrypt",
            "ports": {
                "4444": {
                    "diff": 10,
                    "varDiff": {
                        "minDiff": 16,
                        "maxDiff": 512,
                        "targetTime": 15,
                        "retargetTime": 90,
                        "variancePercent": 30
                    }
                }
            }
        },
        "scrypt-n": {
            "enabled": true,
            "algorithm": "scrypt-n",
            "ports": {
                "5555": {
                    "diff": 10,
                    "varDiff": {
                        "minDiff": 16,
                        "maxDiff": 512,
                        "targetTime": 15,
                        "retargetTime": 90,
                        "variancePercent": 30
                    }
                }
            }
        }
    },

    "profitSwitch": {
        "enabled": true,
        "updateInterval": 60,
        "depth": 0.90,
        "usePoloniex": true,
        "useCryptsy": true,
        "useMintpal": true,
        "useBittrex": true
    }



Title: Re: Auto swtiching - Auth error
Post by: Elmit on August 16, 2014, 01:57:27 AM
How can I track down the TypeError as mentioned above???