Version 12.2 release

Status
Not open for further replies.

qwizzie

Well-known Member
Aug 6, 2014
1,607
763
183
Is this actually true?
New protocol version, so yes.. thats true.

Also dont forget to do a sentinel update (git pull) or you get in the "Watchdog Expired" state again
(happened to me today)
 
Last edited:

qwizzie

Well-known Member
Aug 6, 2014
1,607
763
183
Is there a plan of action with regards to informing mining pools and exchanges that there is a mandatory update out for Dash
that they need to implement ? I'm curious if core-team has contactpersons within mining pools and exchanges that they can reach in a situation like this...
 
Last edited:

Dusan

New Member
Oct 7, 2016
32
9
8
I updated MN on server to 12.2 and also on local PC and tried to start MN
"alias": "MN",

"result": "failed",

"errorMessage": "Could not allocate outpoint

$ ./dash-cli masternode status
{
....
"status": "Not capable masternode: Invalid protocol version"
Having masternode.conf is NOT enough to start a masternode, you need to have the actual private key which controls your funds in the Dash Core wallet you are trying to start a masternode from to do so. Thanks to UdjinM6 for this Information.
 
  • Like
Reactions: UdjinM6

Ninazu

New Member
Feb 10, 2017
13
4
3
34
After update to v.0.12.2.0 i have a problem


Fuuuuu!. NEW_START_REQUIRED needed. Start MISSING don't work.
Why dmn03 still protocol 70206 instead 70208. Its Ok?

Code:
dash-cli masternode status
"status": "Not capable masternode: Invalid protocol version"
 

qwizzie

Well-known Member
Aug 6, 2014
1,607
763
183
After update to v.0.12.2.0 i have a problem


Fuuuuu!. NEW_START_REQUIRED needed. Start MISSING don't work.
Why dmn03 still protocol 70206 instead 70208. Its Ok?

Code:
dash-cli masternode status
Dmn03 still on protocol 70206 is okay, i think Elbereth use one daemon node for backward compatability.

Now that you switched to v.0.12.2, the restart from cold wallet (START ALIAS) is indeed mandatory or your masternode will not get activated.
Also you need to update sentinel with a git pull.
 
Last edited:

maky

Member
Nov 14, 2014
71
32
58
OK, my problem was:
"Not capable masternode: Invalid protocol version"
I got Trezor to start mn. I used version 0.9.13 of Dash Masternode Tool.
Moving to version 0.9.11 fix the problem.
 
  • Like
Reactions: UdjinM6

Acedian

Member
Mar 17, 2017
247
71
88
Dash Address
XeMABbcebB5yeZH2HxsV7yLNJA9hbzMgpz
Where is the data for the number of miners that have updated?
 

adi382

New Member
Aug 5, 2017
8
2
3
36
I have been there...but there is just a flat line at 0.
I am to understand 0 miners have updated?
Seems like none of the major mining pools (AntPool, ViaBTC, etc.) have updated yet. >35% of masternodes have, though.
 

tungfa

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,906
6,729
1,283
I have been there...but there is just a flat line at 0.
I am to understand 0 miners have updated?
Hey guys. The update will only be visible when both the masternode to be paid and the pool has updated (Udjin and Holger both confirmed this). Since you need activate the masternode again after updates that bumps protocol version, these masternodes go to the end of the queue. Since they are at the end of the queue, it takes quite some days for them to be selected for a block. In general it takes 7-8 days to get selected. We are 3 days after the update.
only 37% of masternodes have updated till now, so based in thus we need to wait like 4 more days to have updated masternodes get to the top of the queue
 
  • Like
Reactions: Roger Rodriguez

camosoul

Grizzled Member
Sep 19, 2014
2,263
1,130
1,183
I'm getting WATCHDOG_EXPIRED on restarted/updated nodes... They aren't sticking.
 

camosoul

Grizzled Member
Sep 19, 2014
2,263
1,130
1,183
New protocol version, so yes.. thats true.

Also dont forget to do a sentinel update (git pull) or you get in the "Watchdog Expired" state again
(happened to me today)
It's doing it even with update...
 
Apr 23, 2017
66
26
58
Questions:
1)What is currently the most accurate way to check which position in the payment queue a masternode has?
2) is it correct that if you do a the master-node start you will go back to the queue 100% of the time ?
This command: "masternode start-alias MN1"
 

qwizzie

Well-known Member
Aug 6, 2014
1,607
763
183
Questions:
1)What is currently the most accurate way to check which position in the payment queue a masternode has?
2) is it correct that if you do a the master-node start you will go back to the queue 100% of the time ?
This command: "masternode start-alias MN1"
1 : i always check with Dash Central
2 : masternode start-alias will always (100%) get you to the last position of the queu & reset the active duration on dashninja.pl
 
  • Like
Reactions: tungfa
R

RGXDK

Guest
Could you guys please update dashman so we can update from 12.1 to 12.2 using it?
 

camosoul

Grizzled Member
Sep 19, 2014
2,263
1,130
1,183
Satoshi Labs is also not with the program... Any attempt to send from wallet.trezor.io and the TX bounces off the network.
 

camosoul

Grizzled Member
Sep 19, 2014
2,263
1,130
1,183
strange, your cronjob should move it from watchdog expired to pre-enabled and then later to enabled.
Yeah, it did, but it took much longer than the cron job interval. Took almost 45 minutes.

I expected it to be much faster since the cron job runs every minute.

Whatevs. It worked.
 
Last edited:
  • Like
Reactions: qwizzie

tungfa

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,906
6,729
1,283
Satoshi Labs is also not with the program... Any attempt to send from wallet.trezor.io and the TX bounces off the network.
?
no probs here
used wallet.trezor multi times and no worries !
 
Status
Not open for further replies.