js-waku / go-waku interop issue

[vpavlin]

This is a bug report

Problem

I am trying to use ECIES to secure communication between js-waku and go-waku based application instances. There seems to be some issue somewhere as I cannot get it fully working.

Example repo: https://app.radicle.xyz/nodes/seed.radicle.garden/rad:z29t7pWyymDmGcHR8KUtKMPzXbLh6/

The issue I am seeing is that I cannot get any encrypted messages originating in go-waku decoded in js-waku. If you run the demo above (make backend and open jswaku/index.html in browser), they will start regularly publishing messages -

• js-waku publishes on /wakuecies/1/ping/json
• go-waku publishes on /wakuecies/1/ping-from-go/json

And the subcsribing to receive messages is reverse.

I can see messages published by js-waku to be decoded by go-waku, but messages published by go-waku are never received/decoded by js-waku.

EDIT: I also added a bit where go-waku decodes it's own published messages (obivously using the privateKey used in js-waku component) as they are delivered by Relay (and it does work fine)

Proposed Solutions

No clue:)

Notes

[vpavlin]

Not an issue/bug after all - I made a mistake with attaching RLN proof for plaintext (non-encrypted) payload