• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.10.12.x RC4 Testing

Status
Not open for further replies.
Evan - with the 5000drk limit per wallet.dat - if I have 4950DRK and get sent 100DRK to pass that threshold and have my wallet open - what is the sequence of events?
1) Only 5000 DRK will get denominated and the remainder 50DRK will be left as un-denominated
2) It will try and denominate and fail and will warn the user upon next wallet start up?

Testing this now
 
Wallet can't find a single masternode for almost an hour now.:confused:
masternode count
0
Will try fresh wallet now...
 
Wallet can't find a single masternode for almost an hour now.:confused:
masternode count
0
Will try fresh wallet now...
My two report themselves as OK but my qt client can't see them any more.
Code:
ubuntu@ip-172-31-23-218:~/.darkcoin$ ./darkcoind getinfo
{
  "version" : 101217,
  "protocolversion" : 70029,
  "walletversion" : 60000,
  "balance" : 16674.13800000,
  "anonymized_balance" : 0.00000000,
  "blocks" : 10870,
  "timeoffset" : 0,
  "connections" : 18,
  "proxy" : "",
  "difficulty" : 0.04727956,
  "testnet" : true,
  "keypoololdest" : 1406222622,
  "keypoolsize" : 1001,
  "paytxfee" : 0.00000000,
  "mininput" : 0.00001000,
  "errors" : ""
}
ubuntu@ip-172-31-23-218:~/.darkcoin$ ./darkcoind masternode list
{
  "54.191.236.39:19999" : 1,
  "149.255.109.167:19999" : 1
}
and
Code:
crouton@croutonmn1:~/.darkcoin$ ./darkcoind getinfo
{
  "version" : 101217,
  "protocolversion" : 70029,
  "walletversion" : 60000,
  "balance" : 3162.24740000,
  "anonymized_balance" : 0.00000000,
  "blocks" : 10871,
  "timeoffset" : 0,
  "connections" : 16,
  "proxy" : "",
  "difficulty" : 0.04562441,
  "testnet" : true,
  "keypoololdest" : 1407356284,
  "keypoolsize" : 1001,
  "paytxfee" : 0.00000000,
  "mininput" : 0.00001000,
  "errors" : ""
}
crouton@croutonmn1:~/.darkcoin$ ./darkcoind masternode list
{
  "149.255.109.167:19999" : 1,
  "54.191.236.39:19999" : 1
}

Weird, closed then restarted client again, it's gone back to coin control inputs locked but undenominated and I can see my MNs from the console again.

Closed client again with a view to deleting testnet folder and starting from scratch and got a wallet database runaway error. Debug log shows:

EXCEPTION: St13runtime_error
CDB() : can't open database file wallet.dat, error 2
darkcoin in Runaway exception
 
Last edited by a moderator:
Deleted testnet3 folder and tried again with fresh wallet. Masternode list either empty or on restart again populated but either way no actual denomination appears to be happening.
 
Deleted testnet3 folder and tried again with fresh wallet. Masternode list either empty or on restart again populated but either way no actual denomination appears to be happening.
Have the same issue :( btw almost all inputs appear to be locked for some reason... unlocked them manually and had 2 denomination rounds. But then they became locked again and denomination stopped...
EDIT: unlocked them manually again and had another round... and they locked once more...:confused:
 
Last edited by a moderator:
Evan - with the 5000drk limit per wallet.dat - if I have 4950DRK and get sent 100DRK to pass that threshold and have my wallet open - what is the sequence of events?
1) Only 5000 DRK will get denominated and the remainder 50DRK will be left as un-denominated
2) It will try and denominate and fail and will warn the user upon next wallet start up?

Testing this now
1) Testing results showed that it still denominated my coins over 5000tDRK if I left my wallet open. It showed 5940 anomyized.
2) When I closed the wallet and re-opened I got this message and denomination was then disabled but for some reason the denominated coins that had 3 darksend rounds previously were now not considered "anonymized. You can see below it went down to 3924 anonymized:
pXDf7u8.png

3) When I sent coins out of my account to bring it back below the 5000tDRK threshold denomination started again :)
 
Quick question: Is then new masternode based enforcement switched "on" on testnet? If so, have there been any forking issues or is the new code thought to be bug free and ready for mainnet.
 
Quick question: Is then new masternode based enforcement switched "on" on testnet? If so, have there been any forking issues or is the new code thought to be bug free and ready for mainnet as well.

I'm going to skip enforcement of the payments for RC4. Perfecting Darksend+ has been a lot larger than originally intended and we're having 90%+ payments currently, so I don't want to make people wait a few more weeks for such a small benefit.

Although, once I start testing if there's no problems with the code I'll go ahead and turn it on. It just depends if I find anything.
 
I'm going to skip enforcement of the payments for RC4. Perfecting Darksend+ has been a lot larger than originally intended and we're having 90%+ payments currently, so I don't want to make people wait a few more weeks for such a small benefit.

Although, once I start testing if there's no problems with the code I'll go ahead and turn it on. It just depends if I find anything.

Thanks for the update.
 
Was just about to post the coin locking issue - and you have already fixed it - too fast :)
s1hJgLH.png


Edit: Coins are now unlocked with new version, but not denominating yet prob due to MNs need updating?
 
Last edited by a moderator:
Was just about to post the coin locking issue - and you have already fixed it - too fast :)
s1hJgLH.png


Edit: Coins are now unlocked with new version, but not denominating yet prob due to MNs need updating?

I'm not having any trouble denominating. Try deleting peers.dat, then open the console and type "masternode list", you should see results
 
MN 66.172.33.248:19999 upgraded to 0.10.12.17 RC4 binary. If needed, here is my getinfo output:
Code:
{
    "version" : 101217,
    "protocolversion" : 70029,
    "walletversion" : 60000,
    "balance" : 1121.60260000,
    "anonymized_balance" : 0.00000000,
    "blocks" : 10942,
    "timeoffset" : 0,
    "connections" : 12,
    "proxy" : "",
    "difficulty" : 0.03438802,
    "testnet" : true,
    "keypoololdest" : 1407389757,
    "keypoolsize" : 1002,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "unlocked_until" : 0,
    "errors" : ""
}
And my masternode list output:
Code:
{
    "54.191.236.39:19999" : 1,
    "184.73.179.196:19999" : 1,
    "184.73.179.187:19999" : 1,
    "184.73.179.148:19999" : 1,
    "184.73.179.235:19999" : 1,
    "149.255.109.167:19999" : 1,
    "108.61.198.220:19999" : 1,
    "50.191.199.127:19999" : 1,
    "66.172.33.248:19999" : 1
}
 
Fresh headless v0.10.12.17-beta with auto-denomination enabled seems fast and looks very healthy so far. Sent 1k from faucet to default address.
Code:
$ ./darkcoind getbalance
999.99900000
$ ./darkcoind listaddressgroupings
[
    [
        [
            "mqJCsf4cFcjXaDLAd1iU47N84H4c9CBiLA",
            1.00000001
        ],
        [
            "mmRh7ycvNkaaDUjJr5FwDgrkp6D4Pw3cmK",
            1.00000001
        ],
        [
            "n3LBcmxFRhU8SkmBcZ9jdSP4tETwLca5gB",
            10.00000001
        ],
        [
            "mtwK7QjJmNJ5Au9wfZrFxGMMghdqo6Bodz",
            0.49899977
        ],
        [
            "msckqgWJZxwWfZH89ZUCPUbSb3nW2HikR3",
            1.00000001
        ],
        [
            "mwtnEQCsyZA8ioSGqFi3eLMwo1cdU952DY",
            1.00000001
        ],
        [
            "mk5hAbZkSAtzcAMM3g9odqf25ibuhyJDMa",
            10.00000001
        ],
        [
            "mh5NfHf8foCks2aa5d2Xn9xghD6z5763jj",
            0.50000000
        ],
        [
            "ms3zNjBhkVfLQLaSQyVXeU7juajF8wUpzx",
            10.00000001
        ],
        [
            "mhhUcu6HorEiLNxPNM9rEb6HKbTQWhQbAp",
            10.00000001
        ],
        [
            "mvxuoSRERFXqrKVuGBgYtRSdA93SsWXhPk",
            0.00000000,
            "default"
        ],
        [
            "muzq6EYS7G9Vit5yz5BBEjGYFMgzzWwwZH",
            1.00000001
        ],
        [
            "mhGdSmqRBRwxvk5WApYP5N1h4ABuHLhMFw",
            10.00000001
        ],
        [
            "mxKmTCEGeAXmvbKQs45664whqwutmvxCtA",
            100.00000001
        ],
        [
            "myVrZN8R5RNp1J1bUGnenEPsdhTFBMDLbT",
            1.00000001
        ],
        [
            "mohxA5Gt2GN4pra6VMearG8Tqae9kLgzXx",
            10.00000001
        ],
        [
            "myuPfsPReZ5ei5ELZSuNoScwQ7oMYN7FPF",
            100.00000001
        ],
        [
            "mr3NqFnGLxY93D8SbsRLzhgZ39TWurPtBt",
            10.00000001
        ],
        [
            "mjPtgsVdrt2dw7M3KUUPt1eF59XtERMNhF",
            100.00000001
        ],
        [
            "n4Qf3cBrpxfU41Cgc5ww9cargB1fdCLHqr",
            500.00000001
        ],
        [
            "mfXUpgnMbSVk6cftMhxSYQ7YUdwgu8951L",
            10.00000001
        ],
        [
            "n31nX5Cp7QsYsogpB84yEGUbLUrYbSXevb",
            1.00000001
        ],
        [
            "mhiGJ5bd2vupiyzCvjFkaygW9SR1esMYQ6",
            1.00000001
        ],
        [
            "n2h2CfsC71HPYFUCkaJuHo8fPRvipnFvQX",
            1.00000001
        ],
        [
            "mx5DDNKgFbgvMrhuzaUXJ6ZNJiwsqD8mst",
            100.00000001
        ],
        [
            "mwxyRWDWppKbsPoYkshYTVoDyGHDyWbixU",
            10.00000001
        ]
    ]
]
 
Loads of MNs now:
{
"184.73.179.148:19999" : 1,
"54.191.236.39:19999" : 1,
"184.73.179.187:19999" : 1,
"184.73.179.196:19999" : 1,
"184.73.179.235:19999" : 1,
"149.255.109.167:19999" : 1,
"108.61.198.220:19999" : 1,
"50.191.199.127:19999" : 1,
"66.172.33.248:19999" : 1
}
 
Status
Not open for further replies.
Back
Top