If you are new to the blockchain technology, taking our Introduction to Blockchain Technology self-paced course is highly recommended. Also, for a comprehensive coverage of blockchain development in Ethereum or mastering Solidity programming, taking our below self paced courses is highly recommended:
In our previous article (How to work with Decentralized Data and Content Storage in Ethereum), we covered how to work with decentralized data and content storages like IPFS or BigChainDB in Ethereum.
In this article, we learn about how decentralized messaging with Whisper works in Ethereum.
We are living in an eventful and reactive world. We subscribe to newsletters, and follow people and companies on Twitter, Facebook, or LinkedIn. We buy and sell stocks when the stock prices get to some predefined limits. In a traditional application scenario, an event- driven architecture with a messaging service might be a popular choice for this kind of use case to make the event source and event consumer integrate together asynchronously.
Whisper is a decentralized messaging mechanism designed for asynchronous low- bandwidth, uncertain latency communication and data transmission between decentralized applications. It is almost the same in concept as JMS (Java Message Service) in the Java world, or newer ones like Kafka. A message is an atomic unit of work of data passed from the source application to one or more destination applications. It is up to the receiving party to look into the messages and take action.
Messages can be handled in both the request/reply model or publish/subscribe model. In the request/reply model, DApp A needs to send a message to DApp B in one message channel, and expects the response back from B in another message channel. In the publish/subscribe case, a group of DApps can subscribe messages with a certain topic, and will be able to receive such messages whenever the source system publishes a message about the topic.
As the following diagram shows, when DApp A needs to send a message to B, it will send the messages to the decentralized network. Here, the Whisper nodes will relay the messages to all Whisper nodes, and the targeted receiver or the subscriber, DApp B, will be able to pick up the messages from any of the nodes. Let's have a look at the following diagram:
The following list further explains the process:
[expiry: P, ttl: P, [topic0: B_4, topic1: B_4, ...], data: B, nonce: P]
Visually, the envelope structure looks like the one shown in the following diagram, where expiry is the field as the intended expiry date/time for the message, ttl is the time to live given in seconds, which means the message should no longer be transmitted once it is past the time to live time. Let's have a look at the following image:
The nonce here is conceptually similar to the nonce in the PoW; it is an arbitrary value intended to demonstrate proof of work in composing the message. Topics are a set of indexes intended to help the message recipients watch and find the expected messages.
Whisper provides low-level APIs in web3.shh for DApps to send or watch the messages.
Messages can be sent as anonymous or public messages, can be signed or not signed, can be encrypted or sent as plain messages. It can be sent to one or more recipients, or published to anyone. When sent as signed messages, the message sender will sign the messages with the SHA-256 hash to show the authenticity of the owner of the messages. When encrypted, it can be encrypted using symmetric key, or public and private key pairs. Whoever owns the symmetric key or private keys can decrypt the messages.
Now that we finished our third series of article, we move on to our next article series discussing Ethereum tools and frameworks. Specifically, we cover the following 11 articles:
This article is written in collaboration with Brian Wu who is a leading author of “Learn Ethereum: Build your own decentralized applications with Ethereum and smart contracts” book. He has written 7 books on blockchain development.
Here is the list of our free webinars that are highly recommended:
Here is the list of our 10 free self-paced courses that are highly recommended:
If you like to learn more about Hyperledger Fabric, Hyperledger Sawtooth, Ethereum or Corda, taking the following self-paced classes is highly recommended:
If you want to master Hyperledger Fabric, Ethereum or Corda, taking the following live classes is highly recommended:
If you like to learn more about blockchain technology and how it works, reading the following articles is highly recommended:
If you like to learn more about blockchain development in Ethereum with Solidity, reading the following articles and tutorials is highly recommended:
If you like to learn more about blockchain development with Hyperledger, reading the following articles and tutorials is highly recommended:
If you like to learn more about blockchain development on Corda , reading the following articles and tutorials is highly recommended:
If you like to learn more about blockchain development in other platforms, reading the following articles and tutorials is highly recommended:
We offer private custom tutoring classes both online and in DC, MD and VA for almost all of our courses or bootcamps. Give us a call or email us to discuss your needs.
$50 Limited OfferREGISTER NOW