v0.11.0.x Core Testing

Status
Not open for further replies.
eduffield said:
Please Update To v0.11.0.5

-changed max rounds to 16
-Fixed masternode payments issue - Masternode payments have been broken on testnet, this patch fixes them. Enforcement will turn on after the network has updated
-Bitcoin 0.9.4 upstream changes (Vertoe)
-KeePass integration - Can we get a few people to test this please? (Freynder)
-Darksend balance shows sendable amount now.
-Fixed "darksend is disabled" inaccurate message
-Fixed crashing on -reindex and -gen
-Fixed darksend balance update on click
-Fix for random segfaultfrom Masternode::Check
-Unlock coins when using Darksend reset button

--------

CI-builds for v0.11.0.5

Linux
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/v11/darkcoin-0.11.0.5-linux.tar.gz

Windows & Mac
- Having some issues, will push up binaries later
Click to expand...

Still testnet only yes?
 
Same syncing behaviour as before - syncs fine until about block 72000 (5/6 weeks behind) then hits a brick wall and GUI becomes unusable. Exited QT and synced the rest of the way with the daemon. (Last time I left it alone, came back about 12 hours later and the QT client had eventually synced.)
 
Whenever I try to send anything close to my total balance to a new address in-wallet I get this:

tdrk1.png


This is with a freshly synced blockchain, no conflicting txes shown in tranasaction tab and no locked inputs.

When I manually select all the inputs it works fine.
 
Last edited by a moderator:
Running a Liquidity Provider on the latest version - any idea why I'm seeing this after running the daemon for about two hours?

Code: 
drkcoin@108:~/.darkcoin/testnet3$ tail -f debug.log
2015-01-13 04:58:26 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:00:37 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:02:47 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:04:57 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:07:07 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:09:17 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:11:27 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:13:37 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:15:47 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:17:57 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:20:07 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:22:17 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:24:27 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:26:37 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:28:47 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:30:57 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:33:07 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:35:17 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:37:27 CDarkSendPool::UpdateState() == 3 | 7

What does UpdateState == 3 | 7 mean? I see it almost constantly running liquidity provider on all of the version 11 releases. Just curious, it seems to start working against after a daemon restart. It always seems to slip back into 3 | 7 limbo shortly after one denom. Should I open a ticket in Jira for this?
 
snogcel said:
Running a Liquidity Provider on the latest version - any idea why I'm seeing this after running the daemon for about two hours?

Code: 
drkcoin@108:~/.darkcoin/testnet3$ tail -f debug.log
2015-01-13 04:58:26 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:00:37 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:02:47 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:04:57 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:07:07 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:09:17 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:11:27 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:13:37 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:15:47 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:17:57 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:20:07 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:22:17 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:24:27 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:26:37 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:28:47 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:30:57 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:33:07 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:35:17 CDarkSendPool::UpdateState() == 3 | 7
2015-01-13 05:37:27 CDarkSendPool::UpdateState() == 3 | 7

What does UpdateState == 3 | 7 mean? I see it almost constantly running liquidity provider on all of the version 11 releases. Just curious, it seems to start working against after a daemon restart. It always seems to slip back into 3 | 7 limbo shortly after one denom. Should I open a ticket in Jira for this?
Click to expand...

I have no clue ,but I'll run a liquidity provider in a debugger to try and figure out what's happening.
 
thelonecrouton said:
Whenever I try to send anything close to my total balance to a new address in-wallet I get this:

tdrk1.png


This is with a freshly synced blockchain, no conflicting txes shown in tranasaction tab and no locked inputs.

When I manually select all the inputs it works fine.
Click to expand...

That can mean the transaction you're creating is too large.

Edit: I just got this error and sent every input in separate smaller transactions.
 
Last edited by a moderator:
CI-builds for v0.11.0.5

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-85/gitian-win-darkcoin-bin/32/darkcoin-qt.exe
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-85/gitian-win-darkcoin-bin/32/darkcoind.exe
http://bamboo.darkcoin.qa/artifact/...5/gitian-win-darkcoin-bin/32/darkcoin-cli.exe
http://bamboo.darkcoin.qa/artifact/...rkcoin-bin/32/darkcoin-0.11.0-win32-setup.exe

Windows 64bit:
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-85/gitian-win-darkcoin-bin/64/darkcoin-qt.exe
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-85/gitian-win-darkcoin-bin/64/darkcoind.exe
http://bamboo.darkcoin.qa/artifact/...5/gitian-win-darkcoin-bin/64/darkcoin-cli.exe
http://bamboo.darkcoin.qa/artifact/...rkcoin-bin/64/darkcoin-0.11.0-win64-setup.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DR...n-osx-darkcoin-dist/darkcoin-0.11.0.6-osx.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-89/gitian-linux-darkcoin-bin/bin/32/darkcoind
http://bamboo.darkcoin.qa/artifact/...gitian-linux-darkcoin-bin/bin/32/darkcoin-cli

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-89/gitian-linux-darkcoin-bin/bin/64/darkcoind
http://bamboo.darkcoin.qa/artifact/...gitian-linux-darkcoin-bin/bin/64/darkcoin-cli
 
Last edited by a moderator:
This is all the progress I have made since I downloaded v05 yesterday:
tdrk2.png

I will leave it and see, but I suspect that the top lump of 2981 DRK will never get denominated unless I manually split it up. I had the same issue with the last few builds.
 
thelonecrouton said:
This is all the progress I have made since I downloaded v05 yesterday:
tdrk2.png

I will leave it and see, but I suspect that the top lump of 2981 DRK will never get denominated unless I manually split it up. I had the same issue with the last few builds.
Click to expand...

What amount did you start with? I've never had that issue.
 
Windows 32bit v.1105 still has this problem: Click on button "Start Darksend Mixing". After typing in the passphrase to unlock the wallet, a message pops up in the Darksend textbox, saying "Wallet is locked", but after a minute or so the wallet proceeds with the mixing and that message disappears, replaced with the Darksend mixing messages as usual...

upload_2015-1-13_13-21-9.png
 
eduffield said:
What amount did you start with? I've never had that issue.
Click to expand...
I funded the wallet with two transactions, one for 2983.9xxxx and another for 11.xxxxx, plus there was a <1 bit of change in there. Only the 11.xxxx chunk is getting Darksent.

Settings are 2000/16 rounds, the 11.xxxxx chunk is at 8 rounds, so I'll change settings to 2000/8 rounds and see if that persuades it to start on the big lump.

Haha nope, that just reset all the 8 round DS'd amounts to zero and it's starting again just on the 11 DRK chunk.
 
Last edited by a moderator:
New wallet, starting balance 999 tDRK, v.11.0.5, os: win7 64bit.
Amount and rounds set to 500 / 4.
After 3 hours of the mixing, process hits to wall (Too little to denominate), picture shows the problem.

EDIT: Status update, mixing continue again...

Toolittle.png
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top