• 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.
Crouton MNs both 1 click updated. :)

edit: and local qt wallet has finally sprung into action and is DS+ing like nobodies business. v.15 initially split the balance then just sat there inert, v.16 looking far more lively!

edit2: wow, v16 is on performance enhancing drugs. Up to 4 rounds of DS+ already on a 3000DRK balance in just a few of your Earth 'minutes.' :eek:
 
Last edited by a moderator:
thelonecrouton said:
Crouton MNs both 1 click updated. :)

edit: and local qt wallet has finally sprung into action and is DS+ing like nobodies business. v.15 initially split the balance then just sat there inert, v.16 looking far more lively!

edit2: wow, v16 is on performance enhancing drugs. Up to 4 rounds of DS+ already on a 3000DRK balance in just a few of your Earth 'minutes.' :eek:
Click to expand...

That speed sounds awesome.

I was just thinking ahead, say a windows users was running with a encrypted wallet (most do), as it asks you multiple times for a password during each round, what would happen if you enter the password, 30 mins later it asks again on another round, then it ask again but your not at the computer and can't enter the password. What would happen with your coins? Would it hang....coins get stuck somewhere?... Real world use.

It would be cool if on the password popup, there was an option for how long to keep wallet unlocked..? Sufficient time for all the rounds.
 
mattmct said:
That speed sounds awesome.

I was just thinking ahead, say a windows users was running with a encrypted wallet (most do), as it asks you multiple times for a password during each round, what would happen if you enter the password, 30 mins later it asks again on another round, then it ask again but your not at the computer and can't enter the password. What would happen with your coins? Would it hang....coins get stuck somewhere?... Real world use.

It would be cool if on the password popup, there was an option for how long to keep wallet unlocked..? Sufficient time for all the rounds.
Click to expand...

It shouldn't lock the wallet until the whole process is complete, so that's a bug. Thanks !
 
I just started a new amazon vs and want to set up a testnet remote masternode on it. Question I have, is how do I keep it from denominating. Do I just make sure I have masternode=1 in the conf file before I send the funds? I think I just answered my own question.... LOL
 
TanteStefana said:
I just started a new amazon vs and want to set up a testnet remote masternode on it. Question I have, is how do I keep it from denominating. Do I just make sure I have masternode=1 in the conf file before I send the funds? I think I just answered my own question.... LOL
Click to expand...
darkcoind was set to not denominate by default last I heard, so you shouldn't have to do anything special. I didn't do anything out of the ordinary with the one I just set up this afternoon. With a local/remote setup I think you have to lock the 1000DRK with coin control in the local qt wallet (if you're using the qt client locally) but I haven't tried that yet.
 
clayop said:
Can someone send me tDRK for send/receive tests?
mwr8VD3WUGXrYeHf5r1cugRdw8UMG5hbJT
Click to expand...
Just sent you 123.4567 without anything in coin control selected, just 'use anonymised funds' from a completely anonymised 3000 balance and the wallet is reanonymising the whole lot again - it could stand to be a bit more intelligent about that.
 
Running a fresh instance of v0.10.12.16-beta. Sent 1k from faucet about an hour ago. It split up the large input just fine, but it is apparently not attempting to auto-denominate. Up to 19 confirmations on the initial split.
Edit: Waited for 75 confirms and it still hadn't attempted to auto-denominate. Finally decided to restart the daemon and it immediately started denominating (2014-08-07 02:02:18 DoAutomaticDenominating : Running darksend denominate. Return '').
Code: 
$ grep -i ds debug.log|tail -n50
2014-08-06 23:34:40 dsc - message doesn't match current masternode - 149.255.109.167:19999 != 149.255.109.167:36720
2014-08-06 23:34:40 ProcessMessage(dsc, 38 bytes) FAILED
2014-08-06 23:34:40 dsc - message doesn't match current darksend session 0 588387
2014-08-06 23:34:40 ProcessMessage(dsc, 38 bytes) FAILED
2014-08-06 23:34:40 dssu - message doesn't match current masternode - 149.255.109.167:19999 != 149.255.109.167:36720
2014-08-06 23:34:40 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:34:40 dsc - message doesn't match current darksend session 0 852597
2014-08-06 23:34:40 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:34:40 dssu - message doesn't match current masternode - 149.255.109.167:19999 != 149.255.109.167:36720
2014-08-06 23:34:40 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:34:40 dsc - message doesn't match current darksend session 0 852597
2014-08-06 23:34:40 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:34:51 dssu - message doesn't match current masternode - 149.255.109.167:19999 != 149.255.109.167:36720
2014-08-06 23:34:51 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:34:51 dsc - message doesn't match current darksend session 0 434981
2014-08-06 23:34:51 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:35:07 dssu - message doesn't match current masternode - 149.255.109.167:19999 != 149.255.109.167:36720
2014-08-06 23:35:07 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:35:07 dsc - message doesn't match current darksend session 0 434981
2014-08-06 23:35:07 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:34 DoAutomaticDenominating --- connected, sending dsa for 99900000000
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dsf, 893 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dsc, 38 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 261055
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 261055
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:36 dsc - message doesn't match current darksend session 0 261055
2014-08-06 23:36:36 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:52 dsc - message doesn't match current darksend session 0 261055
2014-08-06 23:36:52 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:37:05 dsc - message doesn't match current darksend session 0 381827
2014-08-06 23:37:05 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:37:21 dsc - message doesn't match current darksend session 0 381827
2014-08-06 23:37:21 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:38:19 ProcessMessage(dseep, 116 bytes) FAILED
 
Last edited by a moderator:
GNULinuxGuy said:
Running a fresh instance of v0.10.12.16-beta. Sent 1k from faucet about an hour ago. It split up the large input just fine, but it is apparently not attempting to auto-denominate. Up to 19 confirmations on the initial split.
Code: 
$ grep -i ds debug.log|tail -n50
2014-08-06 23:34:40 dsc - message doesn't match current masternode - 149.255.109.167:19999 != 149.255.109.167:36720
2014-08-06 23:34:40 ProcessMessage(dsc, 38 bytes) FAILED
2014-08-06 23:34:40 dsc - message doesn't match current darksend session 0 588387
2014-08-06 23:34:40 ProcessMessage(dsc, 38 bytes) FAILED
2014-08-06 23:34:40 dssu - message doesn't match current masternode - 149.255.109.167:19999 != 149.255.109.167:36720
2014-08-06 23:34:40 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:34:40 dsc - message doesn't match current darksend session 0 852597
2014-08-06 23:34:40 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:34:40 dssu - message doesn't match current masternode - 149.255.109.167:19999 != 149.255.109.167:36720
2014-08-06 23:34:40 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:34:40 dsc - message doesn't match current darksend session 0 852597
2014-08-06 23:34:40 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:34:51 dssu - message doesn't match current masternode - 149.255.109.167:19999 != 149.255.109.167:36720
2014-08-06 23:34:51 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:34:51 dsc - message doesn't match current darksend session 0 434981
2014-08-06 23:34:51 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:35:07 dssu - message doesn't match current masternode - 149.255.109.167:19999 != 149.255.109.167:36720
2014-08-06 23:35:07 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:35:07 dsc - message doesn't match current darksend session 0 434981
2014-08-06 23:35:07 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:34 DoAutomaticDenominating --- connected, sending dsa for 99900000000
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dsf, 893 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 576739
2014-08-06 23:36:35 ProcessMessage(dsc, 38 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 261055
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:35 dsc - message doesn't match current darksend session 0 261055
2014-08-06 23:36:35 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:36 dsc - message doesn't match current darksend session 0 261055
2014-08-06 23:36:36 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:36:52 dsc - message doesn't match current darksend session 0 261055
2014-08-06 23:36:52 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:37:05 dsc - message doesn't match current darksend session 0 381827
2014-08-06 23:37:05 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:37:21 dsc - message doesn't match current darksend session 0 381827
2014-08-06 23:37:21 ProcessMessage(dssu, 17 bytes) FAILED
2014-08-06 23:38:19 ProcessMessage(dseep, 116 bytes) FAILED
Click to expand...
That's my MN, someone let me know if there's a problem with it - it's receiving payments though...
 
During the denomination process, if I receive funds, they all will be anonymized without password input. This is great!
After denomination is done, I have to put password when I get funds to denominate.
It was a fun test. I really enjoyed the speed and convenience!
 
Might I suggest that under the Send tab, the balance label also shows unconfirmed coins, ie when you're waiting for DS+'d coins to make it back to you from the anonymisation process. It's a small thing but it might prevent a few heart attacks. Maybe a reassuring tooltip popup 'Your unconfimed funds are being anonymised and will be available again shortly/in x blocks' or something. Might calm people down when there's 20 mins between blocks like just now between 10343 and 10344.
 
thelonecrouton said:
darkcoind was set to not denominate by default last I heard, so you shouldn't have to do anything special. I didn't do anything out of the ordinary with the one I just set up this afternoon. With a local/remote setup I think you have to lock the 1000DRK with coin control in the local qt wallet (if you're using the qt client locally) but I haven't tried that yet.
Click to expand...
Well, I was going to use QT, then I remembered I needed to start darkcoind with the -masternodeaddr=etc so I used the daemon.

And when ... well, I think that was 15, but when opened that wallet and sent myself 2000 dark, it started denominating right away, no input from me other than a request to put in my password?

Anyway, I got an amazon VPC running a masternode now. We shall see how it goes?
 
Windows 0.10.12.16
darkSend Status => ERROR : not compatible with existing transactions

Now keep getting:
darkSend Status => ERROR : transaction not valid
 
Status
Not open for further replies.
Back
Top