Hot answers tagged

42

Whisper is a part of the Ethereum P2P protocol suite that allows for messaging between users via the same network that the blockchain runs on. There are many uses, some of which are listed on the wiki The protocol is seperate from the blockchain, so smart contracts do not have access. Whisper has existed in a sort of alpha, working-prototype state for ...


7

At this point it's difficult to give a very accurate answer to your questions as Whisper is still very much in its infancy stage, however I'll attempt to answer your question with the implemenation that's currently in operation. The amount of whisper topics that you may use for your messages and filters are theoretical infinite. Please note that whisper ...


7

Check out the Use Cases section in the Ethereum Whisper protocol at https://github.com/ethereum/wiki/wiki/Whisper-Overview : shh.post({ "topic": t, "payload": p }); No signature, no encryption: Anonymous broadcast; a bit like an anonymous subject-filtered twitter feed. shh.post({ "from": myIdentity, "topic": t, "payload": p }); Open signature, no encryption:...


5

The two are related in name, and perhaps in their goals. Whisper.sh was released in 2012 and is operated and controlled by a single entity. Ethereum's Whisper protocol is peer to peer and is not controlled by a single entity. Here is a link to a YouTube presentation by Dr Gavin Wood about Ethereum's Whisper.


2

We have just propose our project UnwiredApp based on Ethereum. that is basically a Smart Contract that records messages related to a given user and let the recipient and only him to read them. The pitch video is here. Essential solidity code in the smart contract is the following: struct mess { uint256 idMessage; uint256 idPrevious; uint256 timestamp;...


2

You need to use callbacks so that the asynchronous functions return a value when it has finished processing. Or use async / await. The line var privateKey = shh.getPrivateKey(kId); will get executed before kId has a value, because the newKeyPair function has not completed yet. Most web3.js objects allow a callback as the last parameter, as well as ...


2

Currently, there is no incentive to route whisper messages through the main network, hence the majority of nodes will not have it enabled.


2

With Geth running, (I used geth --rinkeby --fast --cache=512 console --shh --rpc --rpccorsdomain '*' --ws --wsorigins '*'), and web3.js v1 in the browser, type into the browser console: > web3.shh.setProvider("ws://localhost:8546") // must use websockets (read this on https://ethereum.stackexchange.com/a/34840/6014) > web3.shh.newKeyPair().then(...


1

Shh.newMessageFilter(self, criteria) Create a new filter id. This filter id can be used with ShhFilter to poll for new messages that match the set of criteria. I was able to fix the problem by changing: for event in event_filter.get_new_entries(): => as for event in w3.geth.shh.getMessages(filter_id): from web3.auto import w3 import time from web3 ...


1

Currently most of (all of) mainnet do not support Whisper protocol. It needs to be explicitly enabled by node operators. Not sure how reliably you can connect to it. Here is some old information: https://www.sitepoint.com/ethereum-messaging-whisper-status/ https://ethereum.stackexchange.com/a/11178/620


Only top voted, non community-wiki answers of a minimum length are eligible