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

V12 Testing Thread

thelazier said:
FYI, Current hard fork scheduled on mainnet is around September 6th, 2015 at #328008 as commented in https://github.com/dashpay/dash/blob/0d625c888d3b3fa51768ea92a2d0118eb5ea1bad/src/main.cpp#L1572
Click to expand...
Evan also posted here: https://dashtalk.org/threads/v12-testing-thread.5484/page-105#post-61537

"Rollout is planned to be staggered:

8/5 - Turn off enforcement / network upgrade
8/7-12 - Turn on enforcement
8/24 - Hard fork to allow for super blocks
9/6 - The very first budget block will be 332320, so that's quite a ways off (about 36 days from today)"


 
thelazier said:
FYI, Current hard fork scheduled on mainnet is around September 6th, 2015 at #328008 as commented in https://github.com/dashpay/dash/blob/0d625c888d3b3fa51768ea92a2d0118eb5ea1bad/src/main.cpp#L1572
Click to expand...

I thought we might possibly launch on mainnet tomorrow

eduffield said:
DOWNGRADE TEST - 0.11.2.23

I'm happy to announce that v12 looks like it's finished and is very stable! The final test we will need to do is to downgrade the network to 0.11.2.23, then re-upgrade to 12.0.35. The final version will activate a hard fork and the budget system within a day of being launched. Then after a few days (probably about Wednesday), we'll launch v12 officially on mainnet!

Instructions:

1. Please download the official client from dashpay.io
2. Go into dash.conf and add "txindex=1" (our database has this on by default now)
3. Start the client with --reindex
4. Start masternodes anything else you had running

The reindex will send us back to the last valid block before v12 became active last time, so we might need to recreate masternodes. However, when we upgrade from 11.2.23 to 12.0 they should still function correctly.

Thanks so much for helping with testing and the hard work you've put in! You've all made this release a great success already.

-Evan

----

Edit: These messages are OK

************************

EXCEPTION: St12out_of_range

CInv::GetCommand() : type=15 unknown type

dash in ProcessMessages()
Click to expand...
 
I just realized I have 'played' WAY too long tonight - ugh
Gonna be hurt'n in my AM - ugh

3am - ugh
or
3PM in HK - ugh
 
19 Minutes ago the baker completed another batch :-D

GOOD MORNING!!!!!


Is today V12 day?
 
eduffield said:
Unfortunately there's another client hanging issue that needs to be found before we can launch. I'll work on this today and then we'll launch once we're sure it's stable.
Click to expand...

i had one wallet that hang in windows 10 yesterday (v0.12.0.37), maybe posting this will narrow it down :

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-08-04T22:22:29.000000000Z" />
<EventRecordID>2575</EventRecordID>
<Channel>Application</Channel>
<Computer>HuiskamerPC</Computer>
<Security />
</System>
- <EventData>
<Data>dash-qt.exe</Data>
<Data>0.12.0.37</Data>
<Data>1e68</Data>
<Data>01d0ceffa21d761e</Data>
<Data>2</Data>
<Data>D:\TestDash5\dash-qt.exe</Data>
<Data>47d0b7c7-3af7-11e5-bff0-c8d719bf9328</Data>
<Data />
<Data />
<Binary>55006E006B006E006F0077006E0000000000</Binary>
</EventData>
</Event>
 
So after working fine last night, my local Hot wallet MN just won't start; I keep getting error says:

"Not capable masternode: Can't detect external address
Please use the Masternodeaddr configuration option."

I tried starting with fresh wallet - new accountaddr, new 1000 coins, new privkey, with and without txindex=1 in dash.conf
Nothing seems to help

Edit: anyone know what Masternodeaddr configuration option is?
 
You must log in or register to reply here.
Back
Top