-
Notifications
You must be signed in to change notification settings - Fork 10
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
shh_getFilterMessages always returns empty array #4
Comments
I'm not sure you can receive messages you send yourself, from what I understand of whisper. Whisper builds a filter of messages it's seen before as it runs and ignores them; if that includes the messages it's sent, seeing an empty result would make sense - can you try sending and receiving from different nodes? |
Thanks for the quick response! Yeah, the same thing happens with:
I don't know if it's helpful or not to add that both of this snippet and the original do return results using geth ¯_(ツ)_/¯ |
I'm not sure whether creating a new key pair on the same node will be sufficient but it certainly should be - I'm sure you've noticed but parity-ethereum's whisper implementation is entirely incompatible with geth's 😅 |
Since whisper is not any longer part of parity-ethereum and NOT included in parity 2.7.2, it means that whisper on parity is a dead-end street, right? |
@pepihasenfuss as you can see in the README https://github.com/OpenEthereum/whisper#deprecated, this project is no longer maintained. |
Parity client running with the following options:
parity --config dev -lrpc=trace --whisper
When running the following snippet from web3.py:
received_messages
which callsshh_getFilterMessages
under the hood, comes back with an empty result ({"jsonrpc":"2.0","result":[],"id":14}.
), even though there should be a message. Any hints would be awesome! Thanks!The text was updated successfully, but these errors were encountered: