is monero still supported in miningcore

[magecrimson]

I am able to setup a pool, stratum starts up, miners can connect though get disconnected instantly.

Error is:

login error code 2

I have been able to run other xmr based coins like morelo which is a fork of monero. If there is something I am missing please let me know.

coin config:

"monero": {
"name": "Monero",
"canonicalName": "Monero",
"symbol": "XMR",
"family": "cryptonote",
"website": "",
"market": "",
"twitter": "",
"telegram": "",
"discord": "",
"hash": "randomx",
"hashVariant": 0,
"smallestUnit": 1000000000000,
"addressPrefix": 18,
"explorerBlockLink": "https://www.exploremonero.com/block/$height$",
"explorerTxLink": "https://www.exploremonero.com/transaction/{0}"

pool config:

        "id": "monero",
        "enabled": true,
        "coin": "monero",
        "randomXRealm": "xmr1",
        "address": "ADDRESS",
        // Block rewards go to the configured pool wallet address to later be paid out
        // to miners, except for a percentage that can go to, for examples,
        // pool operator(s) as pool fees or or to donations address. Addresses or hashed
        // public keys can be used. Here is an example of rewards going to the main pool
        // "op"
        "rewardRecipients": [
            {
                // Pool wallet
                "address": "ADDRESS",
                "percentage": .5
            }
        ],
        // How often to poll RPC daemons for new blocks, in milliseconds
        "blockRefreshInterval": 400,
        // Some miner apps will consider the pool dead/offline if it doesn't receive
        // anything new jobs for around a minute, so every time we broadcast jobs,
        // set a timeout to rebroadcast in this many seconds unless we find a new job.
        // Set to zero to disable. (Default: 0)
        // "jobRebroadcastTimeout": 10,
        // Remove workers that haven't been in contact for this many seconds.
        // Some attackers will create thousands of workers that use up all available
        // socket connections, usually the workers are zombies and don't submit shares
        // after connecting. This features detects those and disconnects them.
        "clientConnectionTimeout": 600,
        // If a worker is submitting a high threshold of invalid shares, we can
        // temporarily ban their IP to reduce system/network load.
        "banning": {
            "enabled": false,
            // How many seconds to ban worker for
            "time": 600,
            // What percent of invalid shares triggers ban
            "invalidPercent": 50,
            // Check invalid percent when this many shares have been submitted
            "checkThreshold": 50
        },
        // Each pool can have as many ports for your miners to connect to as you wish.
        // Each port can be configured to use its own pool difficulty and variable
        // difficulty settings. 'varDiff' is optional and will only be used for the ports
        // you configure it for.
        "ports": {
            // Binding port for your miners to connect to
            "11008": {
                // Binding address (Default: 127.0.0.1)
                "listenAddress": "0.0.0.0",
                // Pool difficulty
                "difficulty": 100000,
                // TLS/SSL configuration
                "name": "CPU Mining",
                "tls": false,
                "tlsPfxFile": "/var/lib/certs/mycert.pfx",
                // Variable difficulty is a feature that will automatically adjust difficulty
                // for individual miners based on their hash rate in order to lower
                // networking overhead
                "varDiff": {
                    // Minimum difficulty
                    "minDiff": .02,
                    // Maximum difficulty. Network difficulty will be used if it is lower than
                    // this. Set to null to disable.
                    "maxDiff": null,
                    // Try to get 1 share per this many seconds
                    "targetTime": 15,
                    // Check to see if we should retarget every this many seconds
                    "retargetTime": 90,
                    // Allow time to very this % from target without retargeting
                    "variancePercent": 30,
                    // Do not alter difficulty by more than this during a single retarget in
                    // either direction
                    "maxDelta": null,
                }
            }
        },
        // Recommended to have at least two daemon instances running in case one drops
        // out-of-sync or offline. For redundancy, all instances will be polled for
        // block/transaction updates and be used for submitting blocks. Creating a backup
        // daemon involves spawning a daemon using the "-datadir=/backup" argument which
        // creates a new daemon instance with it's own RPC config. For more info on this,
        // visit: https:// en.bitcoin.it/wiki/Data_directory and
        // https:// en.bitcoin.it/wiki/Running_bitcoind
        "daemons": [
            {
                "host": "127.0.0.1",
                "port": 18081,
                "user": "rpcuser",
                "password": "password",
                // Enable streaming Block Notifications via ZeroMQ messaging from Bitcoin
                // Family daemons. Using this is highly recommended. The value of this option
                // is a string that should match the value of the -zmqpubhashblock parameter
                // passed to the coin daemon. If you enable this, you should lower
                // 'blockRefreshInterval' to 1000 or 0 to disable polling entirely.
                // "zmqBlockNotifySocket": "tcp://127.0.0.1:15101",
                // Enable streaming Block Notifications via WebSocket messaging from Ethereum
                // family Parity daemons. Using this is highly recommended. The value of this
                // option is a string that should  match the value of the --ws-port parameter
                // passed to the parity coin daemon. When using --ws-port, you should also
                // specify --ws-interface all and
                // --jsonrpc-apis "eth,net,web3,personal,parity,parity_pubsub,rpc"
                // If you enable this, you should lower 'blockRefreshInterval' to 1000 or 0
                // to disable polling entirely.
                // "portWs": 18545,
            },
            {
                "host": "127.0.0.1",
                "port": 28088,
                "user": "rpcuser",
                "password": "pasword",
                "category": "wallet"
            }
        ],
        // Generate payouts for recorded shares
        "paymentProcessing": {
            "enabled": true,
            // Minimum payment in pool-base-currency (ie. Bitcoin, NOT Satoshis)
            "minimumPayment": .005,
            "payoutScheme": "PPLNS",
            "payoutSchemeConfig": {
                "factor": 2.0
            }
        }
    }

[oliverw]

It should be supported yes.

[ei8ht187]

see issue #1175
probably the same

[magecrimson]

@ei8ht187 yes this is exactly the same issue. Waiting on an answer . My guess based on issue #1175 the current state is "not supported" until MC is updated.