This way, somebody contacted me not telling me, who he/she is, which is somewhat weird/funny. I published one of my Bitmessage addresses on Twitter. The sender gets an acknowledgment in case the message gets delivered. If the receiving person is not online for those two days, the network keeps sending the message in larger periods of time. Each message stays on each node for two days. (Exception: when the network grows, it gets splitted into distinct sections called streams.) This is usually not instant. Messages are transferred through the whole Bitmessage network.

This way, spam should not be of any issue with Bitmessage. Sending of each message needs a certain amount of computation. You have to know Bitmessage address of your peers (funny looking character sequences starting with 'BM-' as shown above). You first generate you first set of addresses (this takes a couple of minutes on current hardware). It is very easily set up on GNU/Linux, OS X, and even Windows.

In contrast to GnuPG/OpenPGP, most people should be able to use Bitmessage without any deeper knowledge of cryptography. So far, I am really pleased by Bitmessage. (Please refer to the whitepaper for more details.) As with any serious security-aware software, Bitmessage is open source ( MIT license). However, there are certain mechanisms that compensate things so that Bitmessage should be able to grow to a large number of participants. With Bitmessage, every message gets encrypted and sent to everybody in the Bitmessage network. If you want more privacy, you can now test Bitmessage. This way, anybody is able to determine to which other parties you are communicating with. ) is clear-text even when you encrypt your mail body with GnuPG. One disadvantage of email is that the header information (who is sending when an email to who subject other time-stamps. This whitepaper describes the basic principles. From now on, you can reach me via BM-NBPFzM7jqFjpHkBB3nLRau4RdLtLTGxw which is an address used by the rather new Bitmessage protocol.

Bitmessage github