-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Whisper: test_shh_filter does not work to send messages to another node. #1031
Comments
I also verify that both nodes are connected to the network. |
Stale issue, but Whisper was officially dropped from Geth and Parity/OE, so support has been removed from Web3.py in #1791. |
@marcgarreau In the latest Do you know the reason why is it dorpped from Geth and Parity? and is there any alternative for it? |
@avatar-lavventura my limited understanding is that Whisper is discontinued or abandoned; I don't know the reasons why. You should look into the Status team's effort, Waku. |
@marcgarreau Ah also |
Ah, sorry to hear that Waku isn't an option for you. I don't believe its reasonable for this team to commit to maintaining an interface to a discontinued Whisper, but we are working to make it easier to introduce custom methods in web3.py. I think this interface is still evolving, but @kclowes is there anything we can share about it yet? |
@avatar-lavventura this is the WIP PR for the documentation, but use with caution as it's not public quite yet and is subject to breaking changes. But you should be able to use that in a pinch |
@kclowes Thanks, I manage to make Whisper work, basic example: ( https://ethereum.stackexchange.com/a/58299/4575 ), by many trial-error and using @pipermerriam 's example-file (but the link is gone right now) I am just get lost, where not sure whisper ( If it will be available , I will keep up my work related to whisper on my project; if not I need to find out different solution for peer-to-peer messaging. Anyway Whisper is/was nice but sender's public key is not included along with the message so I had to send it along with the original message for receiver to respond back; and also the Ethereum address of the sender (which would be actually the real benefit of using it). |
What was wrong?
I have followed following ssh-mode code, which lets each node to send message to itself but different nodes are not able to catch/filter the already sent messages from other nodes.
Overall, I am able to send/receive from the same node, but not from two different ones.
On this approach I observe that each node can only sends message to itself and other nodes don't filter/see those messages. For example, when
node-1
sends a message to the network; it won't show up on thenode-2
such that node-2'sweb3.shh.info{memory}
remains 0, where I assume that it never catches the message.How can it be fixed? Please see the example case:
Node_1
runsshh_filter.get_new_entries()
to catch messages butlen(received_messages)
returns 0, where there is no message is received.Output:
After
Node_1
's messages are sent; I have copied printedreceiverPublicKey
intoreceiver_pub
variable on the following code. I run following code onNode 2
.Node 2
sends a message to the network. Later I press enter on theNode_1
and any of those messages does not show up on theNode_1
:[Q] How could I able to make
node-2
to filternode-1
's messages? Is it possible?Also asked at ethereum.stackexchange but I couldn't reach anyone.
The text was updated successfully, but these errors were encountered: