no worries, thanks for confirming with bertrandtalked to bertrand (dev)
u are right - everything working and on track
(never mind me)
no worries, thanks for confirming with bertrandtalked to bertrand (dev)
u are right - everything working and on track
(never mind me)
Is this actually true?a new start is required after upgrading
New protocol version, so yes.. thats true.Is this actually true?
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.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"
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/124125739/Stakeholder+statusIs 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...
Welcome brotha. If you mean to ask if you could mine dash with antminer D3? Yes you can.Is that work with antminer D3?
dash-cli masternode status
"status": "Not capable masternode: Invalid protocol version"
Dmn03 still on protocol 70206 is okay, i think Elbereth use one daemon node for backward compatability.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
Use https://www.dash.org/forum/threads/gui-tool-for-running-masternode-with-trezor.13748/How to "start alias" from hardware wallet?
0.9.12 works alsoOK, 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.
You can find it on the Dash stats page and click on the "V12.2 Adoption" button.Where is the data for the number of miners that have updated?
I have been there...but there is just a flat line at 0.You can find it on the Dash stats page and click on the "V12.2 Adoption" button.
Seems like none of the major mining pools (AntPool, ViaBTC, etc.) have updated yet. >35% of masternodes have, though.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.I have been there...but there is just a flat line at 0.
I am to understand 0 miners have updated?
It's doing it even with update...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)
strange, your cronjob should move it from watchdog expired to pre-enabled and then later to enabled.It's doing it even with update...
1 : i always check with Dash CentralQuestions:
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"
Yeah, it did, but it took much longer than the cron job interval. Took almost 45 minutes.strange, your cronjob should move it from watchdog expired to pre-enabled and then later to enabled.
?Satoshi Labs is also not with the program... Any attempt to send from wallet.trezor.io and the TX bounces off the network.