v0.13 registration: two MNs, one QT core

[Coqui33]

I have two moocowmoo-hosted MasterNodes. Both MNs are controlled from the same Ubuntu QT core. The MN's v0.13 registration will require two ProRegTx transactions (one registration transaction for each MN). Those transactions will need some newly-created addresses: owner address, payout address, and (optionally) transaction funding address,

My question: Can both MN's use the same owner address, payout address, and (optional) funding address (two or three new addresses in all)? Or must each MN have its own owner address, payout address, and (optional) funding address (four or six new addresses in all)?

 

[strophy]

From the documentation: https://docs.dash.org/DIP3-masternode-changes

The owner address must be unique.
The payout addresses can be the same.
feeSourceAddresses can be the same.

 

[Sven]

From that link, it seems I also need a different BLS key pair for each MN? bls generate only creates one. So I just issue that command multiple times and keep track separately which key I use for which MN? What does BLS actually stand for?

 

[strophy]

Yes, you need different BLS keys for each MN. These keys are used for the P2P messages between masternodes during live operation of the network, e.g. signing quorums on InstantSend, ChainLocks, etc.

BLS stands for Boneh-Lynn-Sacham and is a type of cryptographic signature. It is particularly useful for Dash because it enables threshold signing of quorums transactions based on the principles of Shamir's Secret Sharing. You can read about it here:

https://medium.com/cryptoadvance/bls-signatures-better-than-schnorr-5a7fe30ea716
https://blog.dash.org/secret-sharing-and-threshold-signatures-with-bls-954d1587b5f
https://blog.dash.org/bls-is-it-really-that-slow-4ca8c1fcd38e
https://blog.dash.org/introducing-long-living-masternode-quorums-76ea8b23a85a

 

[Sven]

Thanks, very interesting. So I just issue that command multiple times and which key I use with which MN doesn't matter as long as I keep track to always use the same key for the same MN, correct?

 

[strophy]

Yes, correct. The command will generate private/public key pairs each time you run the command. Note that these are not stored anywhere, so you need to either use them in your registration transaction (which will store the pubkey on the blockchain itself) or keep track of them in a text file or password manager somewhere.

Note also that HD BLS keys are technically possible, but not particularly useful in this case since it is the link between a whole range of keys that allows a masternode to register and operate on the Dash network.