2.1.1 reports different "total parked" value than 2.0.3 on mainnet

Issue #235 new
CoinGame
created an issue

Reference: https://discuss.nubits.com/t/nubits-2-1-1-release/3582/76?u=coingame

While I did not see this personally on my mainnet yet I'm creating the issue to track reports and my other findings. I cannot find the post now but someone reported the issue

Comments (2)

  1. mOD Nu

    Here's my report - because I once again encountered different "totalparked" values between 2.0.3 (my liquidity broadcast node) and 2.1.1 (my testnode):

    2.0.3

    nud -unit=B getinfo | grep -v ip
    {
        "version" : "v2.0.3-dirty-beta",
        "protocolversion" : 2000000,
        "walletversion" : 1,
        "walletunit" : "B",
        "balance" : 0.0,
        "newmint" : 0.0,
        "stake" : 0.0,
        "parked" : 0.0,
        "blocks" : 856825,
        "moneysupply" : 1301113.0143,
        "totalparked" : 85682.1854,
        "connections" : 8,
        "proxy" : "",
        "difficulty" : 0.0001667,
        "testnet" : false,
        "keypoololdest" : 1453190192,
        "keypoolsize" : 101,
        "paytxfee" : 0.01,
        "unlocked_until" : 1561864572,
        "errors" : ""
    }
    

    2.1.1

    nud -unit=B getinfo | grep -v ip
    {
        "version" : "v2.1.1-RC1-15-gcf6a10f-beta",
        "protocolversion" : 2000000,
        "walletversion" : 1,
        "walletunit" : "B",
        "balance" : 0.0,
        "newmint" : 0.0,
        "stake" : 0.0,
        "parked" : 0.0,
        "blocks" : 856825,
        "moneysupply" : 1301113.0143,
        "totalparked" : 27060.9599,
        "timeoffset" : -1,
        "connections" : 8,
        "proxy" : "",
        "difficulty" : 0.0001667,
        "testnet" : false,
        "keypoololdest" : 1460528227,
        "keypoolsize" : 101,
        "paytxfee" : 0.01,
        "errors" : ""
    }
    
  2. CoinGame reporter

    Thanks for the info. I've been looking into this a bit for the past week. It's really difficult to test and look for reproducible changes, so any info is helpful.

  3. Log in to comment