It is difficult to send an unsolicited message to a Bitcoin address, where a communication channel is yet to be established
No existing solution results in a message which is reasonably noticable to an unexpecting recipient.
Messages using the BTCMessage tool are relatively expensive & public, and therefore are not effective means of communication. But they may be desirable in certain circumstances:
This is an optional message header which identifies the transaction as a message, I own this address so might get a few cents from each message.
I am currently searching for a vanity address "1BTCMessage...", which for a case insensitive match will take ~70 days on my GTX 970. I'm using shorter ones until I find a match, or a better solution.
Before 2015, there was no standard for how inputs outputs of Bitcoin transactions should be ordered. As a result, wallets could often have discenable fingerprints based on how they composed transactions.
BIP0069 introduced a standard for ordering where outputs are first ordered by amount, and then secondly by the `scriptPubKeys` byte arrays.
We use this to our advantage to order our message, by using ascending output amounts our message will display in the correct order.
Any to feature requests/suggestions please email me at email@example.com.