Announcing DIP 28 - High-Performance Masternodes

[thephez]

We're excited to announce the release of DIP 28, which introduces and describes the protocol changes necessary for implementing High-Performance Masternodes. High-Performance masternodes will be responsible for hosting Dash Platform services and existing features like ChainLocks and InstantSend. You can read the details about DIP 28 on GitHub. Thanks to everyone that contributed to this DIP (and its implementation)!

 

[qwizzie]

Tenderdash contains a reference implementation of P2P key pair and platformNodeID generation. The tenderdash gen-node-key command generates and displays a node ID (the “id” field) and P2P private key.

What is the P2P private key used for ? DIP28 does not really explain that, it just mentions it gets generated together with a node ID.
Is it an unused part of the P2P key pair ?

 

[xkcd]

Why are you using

Default HTTP port: 443

and not a number about 1024?

 

[thephez]

What is the P2P private key used for ? DIP28 does not really explain that, it just mentions it gets generated together with a node ID.
Is it an unused part of the P2P key pair ?

My understanding is that it's similar to the BLS operator key pair used in Core, but it will be used by Platform (Tenderdash IIRC). Ivan or Łukasz could explain more fully what will be signed with that key.

 

[lklimek]

What is the P2P private key used for ? DIP28 does not really explain that, it just mentions it gets generated together with a node ID.
Is it an unused part of the P2P key pair ?

Platform uses Tenderdash (fork of Tendermint). When two Tenderdash instances communicate, they use p2p keys to encrypt/authenticate the communication.

Why are you using
Default HTTP port: 443
and not a number about 1024?

443 is very good for public APIs, as it is usually allowed on firewalls by default.