v0.11.0.x Core Testing
- Thread starter eduffield
- Start date
- Status
qwizzie
Well-known member
there is technically no interesting difference between 64 and 32 bit, the code base is the same.
and no, we didnt test these binaries for ages, we just started 2 days ago. please take some time and read the release notes, this client is a complete different code base and a lot of stuff can go wrong (with any version of the client).
i ment that we were used to working with windows 32bit binaries .. ever since Flare introduced them to us in earlier updates for Testnet and later when Evan took it over and provided them to us directly for Testnet. Only with this update do we see 64bit windows binaries appear so thats why i thought you ment specifically the 64bit edition...
edit : and yes, i read the release notes.
Last edited by a moderator:
hashcow
New member
kryptofoo
Active member
I switched to the 32 bit windows client which I thought was working fine, but after a while it is hanging again, pegging one CPU core, blockchain stuck at 7 weeks behind. I was unable to get to the settings menu to change the option you suggested, because the client was unresponsive immediately even after multiple restarts. I had to delete my darkcoin/testnet3 folder contents again, then I was able to start the client and change the thread count to -1.
Below is a further description of my problem, not sure if it is helpful for troubleshooting purposes or not.
After a restart with the -1 threads setting, it looks like the client is using more than one core and is fine until it hits the "11 weeks behind" point. For some reason at that point the client chokes, becomes unresponsive and pegs one core of the CPU. Now it's stuck at 11 weeks behind. According to the debug.log file, blocks are still being processed for another few minutes, then the CPU load drops to 0, the client is still unresponsive, and the last lines in my debug.log file are this:
2015-01-03 19:32:57 UpdateTip: new best=000000002ed263b6f0fababde05f82382e57846d80fc49bde380de91a98ef773 height=47513 log2_work=45.257043 tx=128515 date=2014-10-14 23:40:45 progress=0.760536
2015-01-03 19:32:57 ProcessBlock: ACCEPTED
2015-01-03 19:33:15 Successfully synced, asking for Masternode list and payment list
2015-01-03 19:33:15 Successfully synced, asking for Masternode list and payment list
2015-01-03 19:33:15 Successfully synced, asking for Masternode list and payment list
2015-01-03 19:33:15 Successfully synced, asking for Masternode list and payment list
2015-01-03 19:33:15 Successfully synced, asking for Masternode list and payment list
Upon restart, the client is immediately unresponsive and has one core pegged. Again the debug.log file shows some blocks being processed although the client is unresponsive. After a few minutes the client responds again and CPU load drops to 1-2% and the last line of the debug.log file is this:
2015-01-03 19:37:11 receive version message: /Core:0.11.0.3/: version 70052, blocks=86405, us=(REDACTED FOR PRIVACY):59769, them=85.214.22.190:19999, peer=85.214.22.190:19999
2015-01-03 19:37:11 Added time data, samples 10, offset +6 (+0 minutes)
2015-01-03 19:37:11 CheckBlock() : Skipping masternode payment check - nHeight 47657 Hash 000000006523ec6d0289232030cfbada81c0acc164d8f3d682460917a011f0d9
2015-01-03 19:37:11 ProcessBlock: ORPHAN BLOCK 0, prev=00000001325cd6a21e4fa6288056228beea983e437c01ba762e516d22fc23ae8
2015-01-03 19:37:28 Successfully synced, asking for Masternode list and payment list
Current state: the blockchain is still stuck at 11 weeks behind, client is responsive but nothing else is happening. Edit: also when closing the client I get the smaller "shutting down" message box, but it never goes away and I have to close it manually. I also have to go into task manager and shutdown the darkcoin-qt background task.
I just started up "108.61.178.130:19999" : 1,
Can I please have 1000 more to each of these addresses? Should I plan on having these MN's up a month or so? Or permanently?
y69ib2R4PdTARbesaTkkvG22jmf83jBRjG
y9FPqtBkWPsNtaWY9HHJM6bh3Me25Tcaek
yK4Av6A87gz7WgJSHXCZF7vVfdRnxhNVzL
xx3mKP5Eaofa4NRNTCNrQCkU4dUK3mtkYq
yHxnVqv9dKF5WC1xDAjKHRrD5hHq7EkEF9
Can I please have 1000 more to each of these addresses? Should I plan on having these MN's up a month or so? Or permanently?
y69ib2R4PdTARbesaTkkvG22jmf83jBRjG
y9FPqtBkWPsNtaWY9HHJM6bh3Me25Tcaek
yK4Av6A87gz7WgJSHXCZF7vVfdRnxhNVzL
xx3mKP5Eaofa4NRNTCNrQCkU4dUK3mtkYq
yHxnVqv9dKF5WC1xDAjKHRrD5hHq7EkEF9
moli
Well-known member
Darksent 1000 tdrk to
yHxnVqv9dKF5WC1xDAjKHRrD5hHq7EkEF9
Edit: Also sent 1000 tdrk to each of your other addresses.
Last edited by a moderator:
flare
Well-known member
I think this should be changed back
Hopefully we're in for a solid month or two of testing leading up to the release of InstantX...
Thanks for helping!
Hi Ya'all again.
So I set my wallet to denominate again after sending the funds to myself. Anyway, for some reason some of the amounts are locked and show N/A for number of rounds. I don't have masternode=1 on or anything and the amounts that are locked are odd: 810, 9.2857xxx and 8.5137xxx
Also, most of my coins were denominated 3-4 times with some 5 and some 9 times. I was wondering if anyone could explain why they denominate more than asked. I get the feeling it's to make funds available to mix and that requesting 3 rounds is a "minimum" and if your wallet is unlocked and mixing, the system will grab some of your coins to help out, is this so?
Right now my wallet is still unlocked. It says 635 coins are available for darksending, though I have a balance of 1400+ and my settings say to mix 1000 coins 3X (with the above locked for some reason) My wallet says it's 100% complete, it notes "no funds detected in need of denominating (2)" yet my wallet is still unlocked (I would think for safety the wallet should re-lock it'self) and again, it's weird that some of my coins are locked.
explanations welcome I want to explain this stuff when we're finished, so if you can explain it to me, until I understand, I can explain it to all the other old ladies out there, LOL.
Last question, why do our addresses now look weird, like 3QJmnh ? What does that mean please?
So I set my wallet to denominate again after sending the funds to myself. Anyway, for some reason some of the amounts are locked and show N/A for number of rounds. I don't have masternode=1 on or anything and the amounts that are locked are odd: 810, 9.2857xxx and 8.5137xxx
Also, most of my coins were denominated 3-4 times with some 5 and some 9 times. I was wondering if anyone could explain why they denominate more than asked. I get the feeling it's to make funds available to mix and that requesting 3 rounds is a "minimum" and if your wallet is unlocked and mixing, the system will grab some of your coins to help out, is this so?
Right now my wallet is still unlocked. It says 635 coins are available for darksending, though I have a balance of 1400+ and my settings say to mix 1000 coins 3X (with the above locked for some reason) My wallet says it's 100% complete, it notes "no funds detected in need of denominating (2)" yet my wallet is still unlocked (I would think for safety the wallet should re-lock it'self) and again, it's weird that some of my coins are locked.
explanations welcome
I want to explain this stuff when we're finished, so if you can explain it to me, until I understand, I can explain it to all the other old ladies out there, LOL.Last question, why do our addresses now look weird, like 3QJmnh ? What does that mean please?
qwizzie
Well-known member
Hi Ya'all again.
So I set my wallet to denominate again after sending the funds to myself. Anyway, for some reason some of the amounts are locked and show N/A for number of rounds. I don't have masternode=1 on or anything and the amounts that are locked are odd: 810, 9.2857xxx and 8.5137xxx
Also, most of my coins were denominated 3-4 times with some 5 and some 9 times. I was wondering if anyone could explain why they denominate more than asked. I get the feeling it's to make funds available to mix and that requesting 3 rounds is a "minimum" and if your wallet is unlocked and mixing, the system will grab some of your coins to help out, is this so?
Right now my wallet is still unlocked. It says 635 coins are available for darksending, though I have a balance of 1400+ and my settings say to mix 1000 coins 3X (with the above locked for some reason) My wallet says it's 100% complete, it notes "no funds detected in need of denominating (2)" yet my wallet is still unlocked (I would think for safety the wallet should re-lock it'self) and again, it's weird that some of my coins are locked.
explanations welcome
Last question, why do our addresses now look weird, like 3QJmnh ? What does that mean please?
issue 1 : locked input amounts (specially larger input amounts like your 810 amount) looks to be bug related
issue 2 : wallet denominate more then set rounds (you set for 3 and it reaches higher rounds) : bug
issue 3 : a whole lot less darksend balance then set amount : directly the result from locked input amounts i suspect : bug
issue 4 : with encrypted wallet on mainnet you can darksend mix with option ''for anonymization only'' set, i havent encrypted my wallet 0.11.0.x yet here on Testnet but i suspect you can do the same... i'm not sure if that totally satisfies yr security need though.
answer to yr last question : with latest wallet version 0.11.0.x new test addresses have been put into use.
Last edited by a moderator:
Sub-Ether
Well-known member
Flare's compilations on page 12 work, the error has disappeared. The dual core hits 90% on both, I set -1 in the threads and now it updatesYes it was 'dummy versions next ' error,never debugged before but I'll see what I can come up with by tomorrow. The mixing going well on win 8 btw, have to go now
Flare's compilations on page 12 work for my Win 7 64 bit, the error has disappeared. The old dual core hits 90% on both with update, I set -1 in theverification threads and now it updates with a 60% and 40% ratio and is fine.
Anybody want to hit me with some tDRK, I am saving up for a new coat for winter.
y46gBd2658iw8kVa4xLmdffgU8DC73iRCB
kryptofoo
Active member
I got my windows-qt client working. I had to delete my old wallet.dat and use a new wallet, this seems to have solved the client hanging errors. The wallet was from an older v16 client. Maybe I missed a line somewhere telling me to upgrade my wallet? So I created a new wallet, let the client finish syncing, then tried to load my old wallet to recover the tDRK from the old wallet. When I try to send from my old wallet to new wallet I get a fatal error and client crashes.
How can I recover the tDRK from the old wallet? Will this happen to everyone who upgrades?!?
How can I recover the tDRK from the old wallet? Will this happen to everyone who upgrades?!?
qwizzie
Well-known member
you could try to use the old v16 client (if you still have it and if it can still connect to testnet) with the old wallet and sent your funds from there to your new wallet?
Then switch to the latest v0.11.0.x version with your new wallet.
Backwards compatability with regards to wallets is less an issue on Mainnet because everyone has upgraded by now to mandatory update 10.17.24
Last edited by a moderator:
qwizzie
Well-known member
flare's latest compilations can also be found here : https://darkcointalk.org/threads/sticky-testnet-tools-resources.1768/
no need to search through all these pages here trying to find it
no need to search through all these pages here trying to find it
kryptofoo
Active member
Thanks for the idea. No block source available with v16 testnet, I guess nobody is running that client any more.
This is not a problem for me personally it is only tDRK, but it does raise a big red flag IMO. Thing is, my v1016 wallet still worked with my v1017 clients, I did notice some CPU pegging when creating transactions, but the same wallet has stopped working with the v1100 client. Seems like others may face the same problem as I have; if this was mainnet and real DRK it would be a severe problem not just a nuisance!!!
flare
Well-known member
We definitely have to test if using a old wallet.dat ("walletversion": 60001 or "walletversion": 60000 ) with new v11 clients ("walletversion" : 61000) works
For me it does work without issues, using v0.11.0.3 Windows 32bit
Code:

{
"version" : 110003,
"protocolversion" : 70052,
"walletversion" : 60000,
"balance" : 30966.80078795,
"blocks" : 86755,
"timeoffset" : 0,
"connections" : 2,
"proxy" : "",
"difficulty" : 1.20183755,
"testnet" : true,
"keypoololdest" : 1405809931,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}kryptofoo
Active member
I think it is safe to say my v60001 wallet did not work on the v11client (windows-qt 32bit & 64bit). I can access the older wallet by running a v1017 client on testnet but can't send my tDRK to the new 'y' address in v11, the address is invalid.
Edit: I could finally move my tDRK from v10 wallet to v11 wallet using dumpprivkey / importprivkey.
Last edited by a moderator:
flare
Well-known member
This does not apply to mainnet, as the address version will not change there.
- Status