You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should be able to see in the logs the hash of the message as msg_hash. This image is (afaik) from Waku 0.24 for testing purposes.
This is something the Waku team is currently working on, and refactoring. When there is any update regarding this, please let us know in this issue. For now, we will work with the aforementioned image.
Using the following image:
docker pull harbor.status.im/wakuorg/nwaku@sha256:a149122c9a54b7da1a9b4fa66f83d803c3af27e3f6acfbc46010e15e2f3f751c
We should be able to see in the logs the hash of the message as
msg_hash
. This image is (afaik) from Waku 0.24 for testing purposes.This is something the Waku team is currently working on, and refactoring. When there is any update regarding this, please let us know in this issue. For now, we will work with the aforementioned image.
cc @Ivansete-status
The text was updated successfully, but these errors were encountered: