Mn start message relaying

GilAlexander

Member
Jun 26, 2014
84
23
48
When one hit "masternode start" some message is forming and propagating through the network. For now masternode gets to the end of payment queue after "masternode start". Is it possible to save someone's valid "masternode start" message and rebroadcast it later (to kick other masternodes down the list and receive all the payments)?
So does it contain smth like timestamp in the sign?
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
When one hit "masternode start" some message is forming and propagating through the network. For now masternode gets to the end of payment queue after "masternode start". Is it possible to save someone's valid "masternode start" message and rebroadcast it later (to kick other masternodes down the list and receive all the payments)?
So does it contain smth like timestamp in the sign?
The message contains the sigtime, IP and the protocol number and is signed with the masternodeprivkey - so only someone knowing this key can alter it and kick you off the queue.
 
  • Like
Reactions: GilAlexander

GilAlexander

Member
Jun 26, 2014
84
23
48
The message contains the sigtime, IP and the protocol number and is signed with the masternodeprivkey - so only someone knowing this key can alter it and kick you off the queue.
And why precisely someone needs to alter it? Because of sigtime (expiration period?)?
IP (I believe it's hot wallet's ip) and the protocol number are constant for every starting message.
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
And why precisely someone needs to alter it? Because of sigtime (expiration period?)?
IP (I believe it's hot wallet's ip) and the protocol number are constant for every starting message.
Sigtime is the "time of signature" - so basically a "when did the owner of the privkey sign the message". This is also used as base time for startup (if the difference between sigtime and activesince is too large the network will not relay the message though).

If you want to kick someone off/down the queue, you need to alter his message - which is signed. Intercepting the message and relaying it at a later time does not affect queue position, as this is what the masternode is doing by itself anyway: Relay his own start message each 15mins as keep-alive sign...