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

V12 Testing Thread

2 of my 6 windows wallets ended up getting stuck on certain blocks during mixing, i needed to do another -reindex, -zapwallettxes for those two

edit : after it synced correctly one of those two wallets that got stuck before got again stuck on a block.
 
Last edited by a moderator:
v12.0.29

This should be a million times more stable, I found a few rather large bugs and dealt with them. Please restart with --reindex and we shouldn't have any more forks or other consensus issues. We will probabably need to recreate the budget proposals because I changed the format of budget.dat. Thanks!

eduffield
- Implement planned hard forks, August 24, 2015
- Masternode inv messages / save seen in mncache
- only take newest votes
- Fixed budget syncing issues / forking issues / syncing issues …
- Budgets now store the seen objects locally so they're not overwritten when saving/loading to check validity of budget.dat
- Added safer sync "failure" mode, that will retry an hour later if the sync fails for some reason. This will stop the client from thinking it has budget data and rejecting blocks when they're valid.
- protocol bump
- version bump

UdjinM6
- more info for masternode count output/rpcconsole dialog
- include lastPing in mnb hash calculation


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:
This is the correct chain -> dash_c getblockhash 89756
000000101c521ddc9e9f84ce06e1769f53821c8e16ec0616d0d560f4d3081a6a
 
@Evan

I assume the launch of 12 will have a 48 hour - 1 week window to get everybody updated?
before folks are forced off network?

thx
 
UdjinM6 : the masternode number descriptions look good

For those interested in mixing : we will have to wait for the number of DS compatible masternodes to go up first..

T8EhmFA.jpg
 
Sorry if this is off topic. Just wanted to say from someone in the community, thanks to everyone for all the hard work on V12, and making such a unique and awesome system. V12 and the decentralized governance is gonna be epic. You are the best team with the best tech in crypto!!!

THANKS & YOU ROCK!!! :D
 
Do we need to propose the votes again ? (I deleted budget.dat to test persistance but have lost the votes permanently I think)
 
Sub-Ether said:
Do we need to propose the votes again ? (I deleted budget.dat to test persistance but have lost the votes permanently I think)
Click to expand...
Probably so because Evan said, "We will probabably need to recreate the budget proposals because I changed the format of budget.dat."
 
Sub-Ether said:
I get a weird masternode count mismatch from the same ip,same chain and block ? (both on for same time)

hot/cold masternode shows 78 masternodes (with 9 connections)
normal wallet shows 98 masternodes (with 18 connections)
Click to expand...

I bet there's no different with just the new protocol, see what this command says on each:

masternode list protocol 70097
 
flare said:
15mins - but not compiled on a Pi but crosscompiled via gitian on a 8core AWS instance.
Click to expand...


OMG 15 mins - wow - so nice
lol
as you might know - 2 hours on the Pi - lol


You do know that everybody luvs Flare right?
Because we do - lol

\o/ woot !!
 
You must log in or register to reply here.
Back
Top