Separate names with a comma.
Please sign up to discuss the most innovative cryptocurrency!
Discussion in 'Official Announcements' started by tungfa, Feb 27, 2019.
Alright, looks like I missed that. I'm sorry.
I'll take that claim back
DIP3 masternodes : 1474
Masternodes on latest protocol - DIP3 masternodes : 2932
Hello to the community
I have a Dash Masternode on GinPlatform, do i need to do anything for the registration ?
If you hold your own coins, then I assume you had to sign the Start masternode message at the beginning? Maybe you used the Dash Masternode Tool?
Then you also need to register your node for the deterministic masternode list (DIP3) before Sport 15 activates.
You also have to share a BLS key pair with the operator, so either they have to give you the public key, or you have to give them the private key.
Thanks for your reply
I have a Dash Wallet Core installed on my Mac and i have my coins. With GinPlatform, you hold your coins, you show them the transaction ID that shown that you own your 1000 DASH in one address of your core dash wallet, and then they give you a command that you add in masternode.conf and then they send you a command line to start the masternode from your Dash Core debug console. This is all i know unfortunately and i dont know if i need to do anything else now to register asap my Masternode
@airmanos Yes something similar has to happen this time. They should really contact you about it and if they didn't you should probably contact them.
I will contact them immediately Thank you for all help!
Hey everybody! I am trying to follow the guide to register with the Deterministic Masternode List, but I would like some clarification: https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html#dashcore-dip3-upgrade
I was hoping that someone could clarify the command in the first step:
dash-cli bls generate
If I am running a local wallet with multiple masternode addresses, should I run "bls generate" for each address, or just once for the whole wallet? The guide seems to apply to the scenario where we have one masternode address locally and one masternode remotely, but I am not sure how I might apply it to my situation.
Also, I wish the guide would be more explicit about specifying when to do something on the local masternode wallet (with the balance) vs. the remote masternode (without a balance). It seems to use the term "masternode" ambiguously for both types (although once it does mention using ssh for presumably the remote masternode; I wish it would do this more consistently).
In general the term “masternode” refers to the remote server and “collateral” or “collateral address” refers to the local wallet with 1000 Dash and the corresponding keys.
I assume you have a core wallet with several 1000 addresses and the same number remote servers (or masternodes). I also assume you are not using a hardware wallet.
Given all that, you are following the correct part of the guide. As for the bls keys, you need a set of bls keys, comprised of a owner/voter AND operator key, for EACH collateral address with 1000 dash. The owner and voter key are set separately but MUST be the same before spork 15. The voter bls key can be set to something different post spork 15.
Thank you @JGCMiner for your helpful response! Now I know that I need to run "bls generate" (presumably from the remote masternode) for each 1000 Dash collateral address.
I followed the guide for my first masternode, and got as far as running the "dash-cli protx register_prepare ..." command (from my local collateral wallet).
Unfortunately at this point, I got:
error code: -32603
No funds at specified address
I followed the instructions as carefully as I could, and I don't think I am supposed to specify my collateral address in that command, but rather the txid and output index of that collateral (which I did).
Any address I used as a parameter to the "protx" command was a new address, with 0 balance, which is what I interpret I was supposed to do.
Do you have any ideas how I can avoid this error?
When you set up the prepare comand you need to specify a “payout address”. This address can be your “collateral address” OR a different address where you would like to receive payments.
Now, whatever you set as that address needs to have enough funds in it to use for a transaction fee for submit protx in a later step. If you don’t have enough funds in that address you need to separately provide a special “fee address” in prepare protx.
Failure to have enough funds in the “payout address” as well as not providing a “fee address” will result in that error.
It will be interesting to see what happens to the blockrewards / masternode payments, after Spork 15 activates in a few days and DIP3 masternodes have passed their first full payment cycle
and are starting to queue for masternode payments for real.
With a lot less (DIP3) masternodes there could be shorter masternode queues (maybe every 3 or 4 days ?) and maybe even higher amounts (depending on mining difficulty and number of DIP3 masternodes).
That is untill the rest of the masternodes (2000+) catch up and get registered as DIP3 masternode.
@qwizzie why would DIP3 affect reward amount or difficulty?
Where did you get those numbers? When I look in my Core wallet it says there are 5000 masternodes in total.
Total number of active masternodes on latest protocol = 4556 according dashninja (this includes both DIP3 masternodes and normal masternodes)
Link : https://www.dashninja.pl/masternodes.html (91% on latest protocol = 4556)
Use ./dash-cli protx list|head -n -1|tail -n +2|wc -l to see number of DIP3 masternodes (2026),
Total number of masternodes - DIP3 masternodes = 2530 masternode not yet registered as DIP3 masternode.
(this number will decline as more of those masternodes get registered as DIP3 masternode )
Activation of Spork 15 happens when around 50% of our network is registered as DIP3 masternodes (it also depends on daily progress %). When that happens (spork 15 activation) and untill the normal masternodes catch up,
i assume the smaller number of DIP3 masternodes will have an effect on payment cycle and amount.
(at least i hope it will)
I don't see why it would have any effect on amount.
Sure, if the queue is short you have to wait less long, but how does that affect the amount you get when it's your turn?
The masternode rewards (and also the miner rewards as they are both 45% of each blockrewards) is depending on both mining difficulty
and total number of masternodes. Its formulated in such a way that with low mining difficulty and low number of active masternodes
the masternode / miner payments get higher. Before this update we constantly had high mining difficulty and high number of masternodes
so the masternode / miner payments got to the lowest point (1.67 Dash).
With spork 15 activation the number of active masternodes (which will then only be DIP3 masternodes) could start to play a role in that formula as
for a limited time the number of active masternodes (DIP3) will be considerably lower then normal.
I guess we will find out soon enough, because once Spork 15 has been activated any change in either mining difficulty or number of active masternodes
and how this impacts the payments should be automatically updated in here : http://22.214.171.124/~pub/Dash/Dash_Info.html
That's incorrect. Block supply does not depend on the number of masternodes. The number of masternodes basically represent the length of the payment queue, so the more there are masternodes the less frequent each of them is paid. For example, with 50% less masternodes remaining ones might expect to be paid twice as often as they were paid before, so their reward per month would double while reward per block will still be the same.
Thank you - I added a small amount of Dash to the "payout address" and was able to register my masternodes successfully!
Looks like DIP3 masternodes passed the 50% just now :
2289 : DIP3 masternodes
4573 : number of masternodes on latest protocol
Now it gets a little bit more complicated :
MN 2292/4576 = 50,08%
24h 219/4576 = 4,78%
As of 16:00 UTC
Current active 4543
Mar 3 16:00 registered 2109
Mar 4 16:00 registered 2321
MN 2321/4543 = 51.09 %
24h 212/4543 = 4.66%
4546 active masternodes
March 3rd 20:00 registered: 2182
March 4th 20:00 registered: 2356
24h registered: 3.83%
Over 50% Masternodes Registered Deterministic Masternode List
Looks like this is the goal for now (my own interpretation) :
And we have 3 days to achieve this (tilll 8th of march), which should be feasible with current progress rate (keeping fingers crossed).
4550 active masternodes
March 4rd 0:00 registered: 2211
March 5th 0:00 registered: 2384
24h registered: 3.80%
It seems very unlikely that if we reach 60% by March 8 that we'd have less than 1.25% registered in the last 24h.
Yeah, looks like we manage to hit some kind of worst kind scenario here. Some wild guess on how we progress from here:
Time Share Change
2/3 49.0 +4.0
3/3 53.0 +3.0
4/3 56.0 +2.0
5/3 58.0 +1.0
6/3 59.0 +0.5
7/3 59.5 +0.5
Looks like we are way more likely to hit a scenario where we go live with less than 80% registrations than more, unless some whale comes in and register a large number at once.
The question is if the registrations tail off quick enough or not. Too bad we can't create block congestion to stop new registrations
Time Share Change
2/3 49.0 +4.0
3/3 53.0 +3.0
4/3 56.0 +2.0
5/3 58.0 +1.0
6/3 59.0 +0.5
7/3 59.5 +0.5
@martinf What is 2/5, 3/5, 4/5, 6/5, 7/5, 8/5?
If it becomes likely that we'll make it, I would rather expect more people to register in the last 24h than less, since people don't want to miss out.
Dates. May 2nd to May 8th.
Yeah, you might be right. In which case we won't make the May 8th target.
@martinf Huh? May is 2 months from now. Today is March 5th. And since when does May not have a 5th day?