Attention Dash Masternode Owners: Please register with the Deterministic Masternode List now

Status
Not open for further replies.

tungfa

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,906
6,730
1,283


Dash Community,

We are pleased to share that DIP3 (Deterministic Masternode List) has activated. We are asking masternode owners to please begin registering with the Deterministic Masternode List as soon as possible in order to accelerate the activation of sporks 15 and 16 and prevent any delay in the launch of our next release, Dash Core v0.14.

Instructions on how to register can be found here. Masternodes who register will continue to receive payments as scheduled, so there is no need to wait to register. It is critical that masternodes register as soon as possible, as those who have not registered by the time spork 15 (Deterministic Masternode List) is activated will not receive payments.


Spork 15 Activation Criteria
Because spork 15 will reset proposal votes, we must time the activation with the beginning of the voting cycle to minimize the impact to the governance system. If the network does not meet the below activation criteria by March 8, the team will hold off activating it until the next voting cycle begins in early April.

To enable a fair process that allows for sufficient time to register while minimizing delays, the team plans to activate spork 15 based on a formula that takes into account both the total percentage of masternodes already registered, as well as the pace at which masternodes are registering (specifically, the percentage who have registered in the last 24 hours).

The total percentage of masternodes registered must be greater than 50% for us to consider activating. Once we reach 80%, we will automatically activate without regard to the percentage registered within the last 24 hours.

Below is a table displaying the thresholds at which we would activate spork 15. For example, if 60% of masternodes have registered total, and 1.25% or less have registered in the last 24 hours, we will activate. Similarly, if in the last 24 hours we saw 2.5% or less register, we will activate so long as at least 70% total have registered.




Spork 16 - Automatic InstantSend

Spork 16 is the final milestone in the deployment of Dash Core v0.13. After Spork 15 is activated, we will monitor the network for a short period of time to ensure general stability before activating Spork 16. Spork 16 will activate Automatic InstantSend, making 90%+ of the transactions on our network instant by default at no extra cost. We are eager to offer this functionality to users as soon as possible, which is another reason we are working towards a speedy activation of the Deterministic Masternode List. We are also excited to wrap up the rollout of Dash Core v0.13 so we can focus fully on our next release, Dash Core v0.14.




Summary:
- Please register your masternode now, following the guides below
- You can do it now, there is no need to wait for masternode payment
- You have 7 days to register
- Please make sure you are using the latest version of DMT 0.9.22
https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.22

https://docs.dash.org/DIP3-masternode-changes <-- bullet list of changes and new concepts in DIP3
https://docs.dash.org/DIP3-masternode-upgrade <-- guide to upgrade an existing mn without moving collateral
https://docs.dash.org/DIP3-masternode-setup <-- guide to set up a new mn from scratch
https://docs.dash.org/DIP3-upgrade <-- upgrade status and guide for partners
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html#dmt-dip3-upgrade ← Masternode Registration from DMT
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html#dashcore-dip3-upgrade ← Masternode Registration from Dash Core

Reminder:
if you only register your MN - NO start is needed !!
 
Last edited:

qwizzie

Well-known Member
Aug 6, 2014
1,609
764
183
Is it possible to fetch a list of deterministic masternodes (with a total number) through dash-cli command ?
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
Is it possible to fetch a list of deterministic masternodes (with a total number) through dash-cli command ?
Number of registered nodes:
Code:
$ dash-cli protx list|head -n -1|tail -n +2|wc -l
List of IPs registered:
Code:
$ for n in `dash-cli protx list|head -n -1|tail -n +2` ; do n=${n//\"/} ; dash-cli protx info  ${n//,} ; done | grep service|sort
 

qwizzie

Well-known Member
Aug 6, 2014
1,609
764
183


Data :

549 DIP3 masternodes
4459 masternodes on latest protocol - 549 DIP3 masternodes = 3910 masternodes

Note : i could not get the list of IPs registered code from flare to work, so i took data from Dashninja.pl
(the code for number of registered nodes / DIP3 masternodes works fine)
 
Last edited:

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
i could not get the list of IPs registered code from flare to work
What issue are you running into?

Does
Code:
$ for n in `dash-cli protx list|head -n -1|tail -n +2` ; do echo $n ; done
Work for you?
 

qwizzie

Well-known Member
Aug 6, 2014
1,609
764
183
What issue are you running into?

Does
Code:
$ for n in `dash-cli protx list|head -n -1|tail -n +2` ; do echo $n ; done
Work for you?
i need to put ./dash-cli before it correct ? which means ./dash-cli for n in `dash-cli protx list|head -n -1|tail -n +2` ; do echo $n ; done
-bash: syntax error near unexpected token `do'
 
  • Like
Reactions: bhkien

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
i need to put ./dash-cli before it correct ? which means ./dash-cli for n in `dash-cli protx list|head -n -1|tail -n +2` ; do echo $n ; done
-bash: syntax error near unexpected token `do'
Ya, that may be it. dash-cli is in my path, so you may need to add ./ in front of the calls

Try

Code:
for n in `./dash-cli protx list|head -n -1|tail -n +2` ; do n=${n//\"/} ; ./dash-cli protx info  ${n//,} ; done | grep service|sort
assuming that dash-cli is in your current directory.
 
  • Like
Reactions: bhkien

qwizzie

Well-known Member
Aug 6, 2014
1,609
764
183
Ya, that may be it. dash-cli is in my path, so you may add ./ in front of the calls

Try

Code:
for n in `./dash-cli protx list|head -n -1|tail -n +2` ; do n=${n//\"/} ; ./dash-cli protx info  ${n//,} ; done | grep service|sort
assuming that dash-cli is in your current directory.
That works, thanks.
 
Last edited:

qwizzie

Well-known Member
Aug 6, 2014
1,609
764
183
Lets say that at some point i want to update my deterministic masternode (maybe i want to change my payout address in the future), which means that the ProUpRegTx command will come in play .. so i have been reading up about this command in the
maintenance section (https://docs.dash.org/en/stable/masternodes/maintenance.html)



  • proTxHash: The transaction id of the initial ProRegTx

I assume someone (with bad intentions) can not simply look up a random ProRegTx transaction id on our blockchain and use it to update the masternode associated with it ? (put in his own payout address)
Because all i see thats needed for a ProUpRegTx command to succeed is :

  • proTxHash: The transaction id of the initial ProRegTx
  • operatorKeyAddr: An updated BLS public key, or 0 to use the last on-chain operator key
  • votingKeyAddr: An updated voting key address, or 0 to use the last on-chain operator key
  • payoutAddress: An updated Dash address for owner payments, or 0 to use the last on-chain operator key
  • feeSourceAddress (optional): An address used to fund ProTx fee. PayoutAddress will be used if not specified.

Are there checks to the collateral wallet to prevent above from happening ? Or can the transaction id of the initial ProRegTx only be found in our own collateral wallet and is it private information ?
I feel like i'm missing something here about how this ProUpRegTx command exactly works.
 
Last edited:

nmarley

Active Member
Jun 28, 2014
366
424
133
Are there checks to the collateral wallet to prevent above from happening ? Or can the transaction id of the initial ProRegTx only be found in our own collateral wallet and is it private information ?
I feel like i'm missing something here about how this ProUpRegTx command exactly works.
It has to be signed w/the owner key, as stated in the DIP:

https://github.com/dashpay/dips/blob/master/dip-0003.md#updating-registrar-of-masternode-proupregtx

To registrar update a masternode, the masternode owner must submit another special transaction (DIP2) to the network. This special transaction is called a Provider Update Registrar Transaction and is abbreviated as ProUpRegTx. It can only be done by the owner.
And see the payloadSig field description:

Signature of the hash of the ProTx fields. Signed by the Owner.
 
  • Like
Reactions: qwizzie

masternube

Member
Nov 9, 2017
81
14
48
Last week Ryan tweeted:
The sooner you register after DIP3 activates the higher up the payment queue you’ll be when the network switches to the deterministic masternode list. I.e., it will pay to be prompt!
How does that work if the activation of Spork 15 is timed based on the voting cycle? Wouldn't it be kind of random who happens to be at the front of the queue at the time the voting cycle starts? Or does the activation of Spork 15 automatically reset the queue into registration order?
 

Figlmüller

Member
Sep 2, 2014
85
45
58
Vienna, Austria
When trying to register we came across the following error message, which does not tell what's exactly wrong:

Code:
bad-protx-key-not-same (code 16) (code -1)
But the sources reveal the following:

Code:
        if (!deterministicMNManager->IsDeterministicMNsSporkActive(pindexPrev->nHeight)) {
            if (dmn->pdmnState->keyIDOwner != ptx.keyIDVoting) {
                return state.DoS(10, false, REJECT_INVALID, "bad-protx-key-not-same");
            }
        }
So if you come across this error, be sure that the OWNER address matches the VOTING address, as long as Spork15 is NOT active.
You could really mention that within the docs. Took us some time to figure out what's wrong with our transaction. //Edit: I'm stupid. It's mentioned withing the docs :)
 
Last edited:
  • Like
Reactions: stan.distortion

Liz R

New Member
Mar 2, 2018
30
117
33
Last week Ryan tweeted:


How does that work if the activation of Spork 15 is timed based on the voting cycle? Wouldn't it be kind of random who happens to be at the front of the queue at the time the voting cycle starts? Or does the activation of Spork 15 automatically reset the queue into registration order?
Hey there, @masternube. You are correct, it is basically random who gets paid first. Spork 15 does not automatically reset the queue into the order in which masternodes registered. Sorry for the confusion.
 
  • Like
Reactions: bhkien

masternube

Member
Nov 9, 2017
81
14
48
Hey there, @masternube. You are correct, it is basically random who gets paid first. Spork 15 does not automatically reset the queue into the order in which masternodes registered. Sorry for the confusion.
So Ryan was saying nonsense and nobody who understood told him to remove his tweet? And he got us all stressing and scrambling to register ASAP for no reason?

I woke up very early and bothered my operator to give me the BLS key in time for nothing?

Edit: In any case, thanks for the quick and honest reply! But quite disappointing.
 

Liz R

New Member
Mar 2, 2018
30
117
33
@masternube I hear you. So sorry for the confusion. We do want folks to register and get their spot on the deterministic masternode list sooner rather than later to ensure readiness for the spork 15 activation, but I realize the messaging wasn't clear around this. We will try to do better.
 

murkey

New Member
Jul 13, 2018
12
2
3
29
So will we lose our place in queue doing this? seems I lost mine. :( Also can't tell if my MN is running at all now lol.


does everything look normal?

 

Liz R

New Member
Mar 2, 2018
30
117
33
So will we lose our place in queue doing this? seems I lost mine. :(
@murkey No, you should not lose your place in the queue by registering. You should continue to receive payments as scheduled based on the current ("old") queue. The "new" queue (based on the DML, post spork 15 activation) is simultaneously cycling through in parallel and simulating payouts, but will not actually become "the" queue (e.g. that actually enforces the payments) until spork 15 is activated. Let me know if that makes sense. :)

Regardless I will ask one of my more technical colleagues to review your screenshot to ensure everything is in order.
 

murkey

New Member
Jul 13, 2018
12
2
3
29
Thank you.

I am actually getting another error now ( haven't change anything since earlier screenshot)

I might have messed up by clicking "Start masternode using hardware wallet" on DMT. after registering my Deterministic masternode with "automatic update".

 

nmarley

Active Member
Jun 28, 2014
366
424
133
I might have messed up by clicking "Start masternode using hardware wallet" on DMT. after registering my Deterministic masternode with "automatic update".
If you sent out an MNB (e.g. a "masternode start" message using your HW wallet), then this will have reset your place in the current queue.

It looks from this screenshot that your dashd isn't running, however, I can't say for sure as I am not familiar with this tool. This looks like it might be dashman, which is community developed and supported, but I don't have experience using it, so can't say.
 

tungfa

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,906
6,730
1,283
Reminder to all
if you only register your Masternode NO start is needed !!!
 

masternube

Member
Nov 9, 2017
81
14
48
@masternube I hear you. So sorry for the confusion. We do want folks to register and get their spot on the deterministic masternode list sooner rather than later to ensure readiness for the spork 15 activation, but I realize the messaging wasn't clear around this. We will try to do better.
Liz, will Spork 15 be activated exactly at the superblock? Or some time that day? Or some time in the following days?
Is the activation automatic based on set conditions or is human action and judgement involved?
 

c3works

Member
Jun 22, 2016
52
18
48
58


Data :

549 DIP3 masternodes
4459 masternodes on latest protocol - 549 DIP3 masternodes = 3910 masternodes

Note : i could not get the list of IPs registered code from flare to work, so i took data from Dashninja.pl
(the code for number of registered nodes / DIP3 masternodes works fine)
Is there a live version of the DIP3 data available somewhere? Also, though unrelated, how do I reverify the MNO banner for my member name?
 

masternube

Member
Nov 9, 2017
81
14
48
Actually the next superblock is expected on March 2nd. So March 9th isn't the beginning of the voting cycle, is it?
 

qwizzie

Well-known Member
Aug 6, 2014
1,609
764
183
Is there a live version of the DIP3 data available somewhere? Also, though unrelated, how do I reverify the MNO banner for my member name?
You can fetch DIP3 data a few ways :

Through your linux server : ./dash-cli protx list|head -n -1|tail -n +2|wc -l (credits flare)
Through your windows wallet after full sync (Masternodes tab --> DIP3 tab --> there is a total number displayed there.

Then you have to calculate the percentage of DIP3 masternodes against the number of masternodes on latest protocol (which can be found on dashninja.pl and is currently 88% / 4472)
If you want this data displayed on a chart you can check this site : https://www.meta-chart.com/pie
In Data you set number of slices to 2 (slice 1 value = number of DIP3 masternodes that you fetched through dash-cli or through your wallet, slice 2 value = number of masternodes from dashninja - number of DIP3 masternodes)

If you are just interested in the percentage you can also check https://percentagecalculator.net/



From post 1 :
The total percentage of masternodes registered must be greater than 50% for us to consider activating. Once we reach 80%, we will automatically activate without regard to the percentage registered within the last 24 hours.
Which means we are almost halfway to activating Spork 15.
If we can reach 50% before 8 of march, the Dash dev team can active Spork 15.
If its below 50% or if the 24 hour % are not met, then activation of Spork 15 will have to be postponed to next voting cycle early april..

* the team plans to activate spork 15 based on a formula that takes into account both the total percentage of masternodes already registered, as well as the pace at which masternodes are registering (specifically, the percentage who have registered in the last 24 hours).



how do I reverify the MNO banner for my member name?
i dont have an answer for you on that one..
 
Last edited:

c3works

Member
Jun 22, 2016
52
18
48
58
You can fetch DIP3 data a few ways :

Through your linux server : ./dash-cli protx list|head -n -1|tail -n +2|wc -l (credits flare)
Through your windows wallet after full sync (Masternodes tab --> DIP3 tab --> there is a total number displayed there.

Then you have to calculate the percentage of DIP3 masternodes against the number of masternodes on latest protocol (which can be found on dashninja.pl and is currently 88% / 4472)
If you want this data displayed on a chart you can check this site : https://www.meta-chart.com/pie
In Data you set number of slices to 2 (slice 1 value = number of DIP3 masternodes that you fetched through dash-cli or through your wallet, slice 2 value = number of masternodes from dashninja - number of DIP3 masternodes)

If you are just interested in the percentage you can also check https://percentagecalculator.net/



From post 1 :

Which means we are almost halfway to activating Spork 15.
If we can reach 50% before 8 of march, the Dash dev team can active Spork 15.
If its below 50% or if the 24 hour % are not met, then activation of Spork 15 will have to be postponed to next voting cycle early april..

* the team plans to activate spork 15 based on a formula that takes into account both the total percentage of masternodes already registered, as well as the pace at which masternodes are registering (specifically, the percentage who have registered in the last 24 hours).




i dont have an answer for you on that one..
 

Liz R

New Member
Mar 2, 2018
30
117
33
Liz, will Spork 15 be activated exactly at the superblock? Or some time that day? Or some time in the following days?
Is the activation automatic based on set conditions or is human action and judgement involved?
Hey @masternube - it will be activated in the days following the superblock, so long as the criteria outlined above re: % total MNs registered and % registered in the last 24h. However if the criteria isn't met by March 8 (~25% of the way into the voting period), we will wait until the next voting period and try again in April, to minimize disruption to the proposal system since spork 15 will reset votes. The criteria is not actually coded in, however - the spork 15 activation is manual.
 

masternube

Member
Nov 9, 2017
81
14
48
The criteria is not actually coded in, however - the spork 15 activation is manual.
Given that the timing of the Spork 15 activation affects who gets paid when, I find it a bit concerning that this is manual and it could even result in a conflict of interest.
A few lucky people will get rewarded twice on the same day while others may have to wait 2 weeks between payments.
I hope this will be considered with future migrations to minimize potentially unfair impact on payouts.
 
Last edited:
Status
Not open for further replies.