V12 Testing Thread

Please update -- v0.12.0.5

-Removed need for amounts in masternode winners protocol - eduffield
-Spork changes / improvements - eduffield
  • New Command "Spork Active" : Show which sporks report as active
  • Cleaned up the spork code and fixed some bugs with defaults
-refresh en source/translations - Udjin
-fix strings - Udjin
- Implemented spork for only paying new nodes after a period of time on mainnet
- protocol bump
- fixed a few issues with sporks. Spork show now shows all sporks, instead of the changed ones. IsSporkActive now supports sporks set to 0 as on.



Linux32:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux32.tar.gz

Linux64:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux64.tar.gz

Mac:
https://dashpay.atlassian.net/build...n-osx-dash-dist//dash-0.12.0-osx-unsigned.dmg

Win32:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win32.zip

Win64:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win64.zip
 
Last edited by a moderator:
eduffield UdjinM6

I don't know if this is important or not, but I thought I would report.

I, like moli, had two Darksend denominate "conflicted" transactions which disappeared after a reindex. Then, they reappeared as conflicted in my transaction list after around 12 hours. Darksend continued normally after a while, but then stopped and now I haven't had another Darksend denominate transaction for over 12 hours. If you need my debug I'll send it to you.

I'm now upgrading to version 5, I'll see if that helps.
 
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win32.zip => v0.12.0.4

04e160a0cf5eab01f7111591e85e.png


cb9129869acbfd97d2e5c89d9c5e.png
 
Last edited by a moderator:
eduffield said:
Please update -- v0.12.0.5

-Removed need for amounts in masternode winners protocol - eduffield
-Spork changes / improvements - eduffield
  • New Command "Spork Active" : Show which sporks report as active
  • Cleaned up the spork code and fixed some bugs with defaults
-refresh en source/translations - Udjin
-fix strings - Udjin
- Implemented spork for only paying new nodes after a period of time on mainnet
- protocol bump
- fixed a few issues with sporks. Spork show now shows all sporks, instead of the changed ones. IsSporkActive now supports sporks set to 0 as on.
Click to expand...



windows 64bit : both GUI and client version in debug console still point to v0.12.0.4

getinfo shows :

"version" : 120004,
"protocolversion" : 70082,
"walletversion" : 61000,

so at least the protocol version looks good.
 
TaoOfSatoshi said:
eduffield UdjinM6

I don't know if this is important or not, but I thought I would report.

I, like moli, had two Darksend denominate "conflicted" transactions which disappeared after a reindex. Then, they reappeared as conflicted in my transaction list after around 12 hours. Darksend continued normally after a while, but then stopped and now I haven't had another Darksend denominate transaction for over 12 hours. If you need my debug I'll send it to you.

I'm now upgrading to version 5, I'll see if that helps.
Click to expand...
Reindex did not fix the conflicted DS denominate tx's on my wallet, but -zapwallettxes did.
For the one conflicted DS Denominate tx on my second wallet, I didn't do anything but it disappeared after a restart..
 
moli said:
Reindex did not fix the conflicted DS denominate tx's on my wallet, but -zapwallettxes did.
For the one conflicted DS Denominate tx on my second wallet, I didn't do anything but it disappeared after a restart..
Click to expand...

Thanks, I have conflicted trans -reindex doesn't fix... I'll try -zapwallettxes
 
moli said:
Reindex did not fix the conflicted DS denominate tx's on my wallet, but -zapwallettxes did.
For the one conflicted DS Denominate tx on my second wallet, I didn't do anything but it disappeared after a restart..
Click to expand...
Fixed, and Darksend kicked off right away!
 
Can anyone link me a primer to how to install the testnet wallet on ubunntu?

Pablo.
 
Initial Suggestions:

1. I don't think Darksend should be "on" (box ticked) by default. It takes a while to mix funds and when you get the wallet up for the first time and want to send a payment it gives you an error because you have no DS funds ready (naturally); this is an easy fix and will greatly reduce first time user friction.

2. I think Coin Control should be on by default, I had to go hunt for it in settings. If I recall correctly previous wallets had coin control available from the start. I think the risk of newbie users mucking something up with CC is low and it's an important feature many newbies who will need it will not know about unless they go trolling in settings.

:)

Pablo.
 
bertlebbert said:
This did happen a coupla times on previous versions; sometimes "Restart wallet" helped, or Starting/stopping mixing helped, but neither seems to work here...
Click to expand...
Something is sticky... I clicked on "Reset Options", it restarted the wallet. Now I'm able to change the rounds and amount from the options screen and it does so on the wallet.
 
You must log in or register to reply here.
Back
Top