biolizard89 wrote:
If you're willing to spend a name fee on contacting the name owner, you can register a new name with a message for the owner, and transfer that name to the owner. It will show up in their wallet; maybe they'll notice and read the message. No guarantees that this will work though.
This is a simple but good idea. But we could make it even better.
1. It would be much easier to use and wouldn't be needed to explain for every user if this would be an automated function from the wallet.
A new menu entry:
-send message-
- enter domain name or another namespace entry
- random name generated(20 character long) and registered it wallet has at least 0.02 NMC
- random name transferred to the name entry holder
The name holder would see the message if he has an open wallet holding that name.
2. The former message would be an open message which could be read by everyone even if not automatically showed in his wallet.
But we could make it encrypted.
What we need for that is a public key from the name holder which could be linked from his name entry in an id/ or another standardized namespace for this purpose.
Actually it could be only a 0.5k length key but it is still better then having a plaintext.
3. We could even make another step of automation to make it easier for user who have difficulties using public key cryptography.
Making another menu entry
- adding encrypted channel-
- select name entry on which to receive encrypted message
- create random keypair(a 0.5k key by the actual size limit)
- storing private key for communication channel in wallet
- publishing public key in the blockchain in a random generated name entry
- and linking the public key from the namespace entry where to receive the messages( for ex id/bob)
If you like the idea we could discuss about it in another thread.