Masternode status is broadcasted to peer.
It's like a transaction msg but has a different identifier.
Is it prevented somehow that the attacker can't fake the status message after successfully ddos'ing the node down?
masternodeprivkey is the one.
Masternodes now sign their 1000DRK vin for the first message to the network, then they specific a second pubkey
that they will sign all further messages with. This second signing key must be specified for
all masternodes in the configuration with the option "masternodeprivkey"
https://darkcointalk.org/threads/new-version-9-4-0-and-10-8-0.690/I think the attacker can't fake, but can duplicate previous msg, and eventually get banned.