Just got a reply from user kowabit
- "not real. ;-)" (see txid: CH8bBc5HiYo6X2oMJUfM5n2cJZNypcRGxtwTEu4BbfUx)
on my question:
- "Am I the first who sent you now a MESSAGE ? :-) https://twitter.com/FutureMeHere " (see txid: 6M7q5V3fE4v7pU84VCsf5oc7mtXBHDaz6C8G4ddjbQ4Q)
The idea is nothing fancy, you just use the Attachment field to send an encoded message (here base58).
You also don't need a specific coin to do that (here I am using the MSG coin), since you just have to tell your buddy on what to listen:
- e.g. you could create your own coin (for 1 WAVES) and write a simple prog that listens for incoming transactions and decodes the attachment field then
- the message itself could be a securely encoded message (with method M1) which you then encode again with base58
- and your prog just decodes that on the rules/method you agreed on (e.g. 1. decode with base58 rules 2. decode the result with the M1 rules)
Also the WAVES team writes in their roadmap (October 5):
So we can do that a little bit more comfortable :-)
Reach out to me also on twitter!
multi-platform communication :-)