Just a silly question about the proposed system to sent messages and ip obfuscation (3 masternodes encrypting / decrypting messages) :
What happens when a masternode goes down in that process?
Will the message get trough somehow, or can it never be decrypted again ? :p
I don't know if this was answered but there was always a slave to pick up where the last left off if that were to happen. Now, I think we have all masternodes that are in line as back up, ie: 1st winning masternode, 2nd in line, 3rd in line, etc...
Yes, it was answered. Thanks, good to know it's redundant!
I thought it was automatically picked up by the next masternode in line, but apparently not. Listen to our president, he's one of the smartest people here, LOL. My only talent is IF I understand, I can usually put it into layman's terms... but if I'm not understanding, I screw it up, LOL
Actually Evan didn't mention redundancy. So I answered as 'do retry'.
https://darkcointalk.org/threads/development-update-july-30th.1924/But there are many ways to archive redundancy.
ex) mininum redundancy(at least 2 path)
1) client send msg twice
- select 6 Masternodes and make 2 set of encrypted msg, send it to 1 and 4.
- 1[2[3[msg]]], 4[5[6[msg]]]
2) first Masternode send msg twice
- select 5 Masternodes and make 1 set of encrypted msg, send it to 1.
- 1[2[3[msg]], 4[5[msg]]]
3) ++
4) ++
IP Obfuscation:
IP Obfuscation is a critical part of the anonymity package that Darkcoin will bring to bear. Though completion and release of RC4 is our primary concern at the moment, we do have a working roadmap for the implementation of IP obfuscation.
Here’s how it works:
Anyone on the Darkcoin network will be able to communicate securely by using the Masternode network and our encrypted transit system. A user who would like to transmit a payment securely will encrypt the message in such a way that only specific Masternodes can decrypt it.
The user’s client will select three Masternodes, then use the privkey from each of those nodes to wrap the message it wishes to send in three successive encrypted containers. These containers can only be decrypted by their associated Masternodes.
Once wrapped in these three containers, the client will send the encrypted package to the Masternode that corresponds to the outermost encryption layer (Masternode 1). Upon receiving it, Masternode 1 will decrypt the outermost layer in order to learn the identity of the second Masternode in the sequence. Masternode 1 will then relay the message to Masternode 2, which will decrypt the 2nd encryption layer and learn the identity of the third Masternode in the sequence. Masternode 2 forwards the package on to Masternode 3, which decrypts the innermost encryption layer, gaining access to message itself. Masternode 3 then broadcasts the message to the network, and far as the network is concerned, that is where the message originated.
With this envelope encryption system, Masternode 1 is not able to determine which Masternode will ultimately broadcast the message. Similarly, Masternode 3 is unable to determine the identity of either the first Masternode in the sequence or of the original sender.