no worries, thanks for confirming with bertrandtalked to bertrand (dev)
u are right - everything working and on track
(never mind me)
- Status
Last edited:
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:
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...
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:
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.
Welcome brotha. If you mean to ask if you could mine dash with antminer D3? Yes you can.
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
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:
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.
- Apr 9, 2014
- 8,902
- 6,729
- 1,283
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
More and more people interested in knowing digital cash
Companies interested in receiving Dash as a form of payment: Hotel, Restaurant, International travel agency
https://www.instagram.com/p/BbHp4m3l7Cl/?taken-by=dashlaguaira
Dash: Xoq6FT4mJwW36hFWt46uQLKF2Bros3i4Fb
Companies interested in receiving Dash as a form of payment: Hotel, Restaurant, International travel agency
https://www.instagram.com/p/BbHp4m3l7Cl/?taken-by=dashlaguaira
Dash: Xoq6FT4mJwW36hFWt46uQLKF2Bros3i4Fb
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)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"
strange, your cronjob should move it from watchdog expired to pre-enabled and then later to enabled.
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
R
RGXDK
Guest
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:
- Apr 9, 2014
- 8,902
- 6,729
- 1,283
- Status