Signature & Encryption with Web3

[D4nte]

Problem

DApp developers may need to setup private channels or end-to-end encryption for privacy purposes.

Generic symmetric, asymmetric encryption and signature is tracked with #179, using Waku Message version 1.

It is not clear at this stage how users can sign/encrypt with their Ethereum account.

Web3 API provides an API to sign messages eth_sign, some wallets such as Metamask provide an API to decrypt messages and retrieve Ethereum's account public key.

Solution

Encryption of messages maybe limited to using Metamask's eth_decrypt API for now.
The signature is not compatible with WakuMessage version 1 so a wrapper (and spec) will need to be provider.
Encryption with Metamask is unlikely to be compatible with version 1 but it should be investigated and documented. Confirmed, it uses a different encryption schema.

DoD

• Build PoC that signs and encrypt messages using Web3: https://github.com/status-im/js-waku/tree/main/examples/eth-pm-wallet-encryption
• Provide guide on how to sign messages using Web3: Best to wait for Poll/Vote White Label Solutions #257 to learn how to then use the signatures on the blockchain.
• Provide guide on how to encrypt messages using Web3.
• Build PoC that signs messages as per Waku message version 1
• Build PoC that encrypt messages as per Waku message version 1 (Eth-PM)
• Provide guide on how to sign messages using Waku message version 1
• Provide guide on how to encrypt messages using Waku message version 1 Add guide to encrypt messages using version 1 #283.

[D4nte]

See vacp2p/rfc#373

Best to have few examples ready:

• Encryption with web3
• Signature with web3
• Encryption without web3
• Signature without web3

[D4nte]

First version of Eth-DM done #204

Features:

• Send private messages to a recipient, only knowing their Ethereum address
• The messages are encrypted, only the recipient can decrypt
• Works with metamask (and hopefully status app, will test)
• Participants need to opt in to receive messages
• Uses push light protocol

[D4nte]

Lots of work done with #179, using Waku Message version 1.

Web3 API cannot really be used for encryption, except when using metamask.
Web3 API can be used for signing.

Re-focus this issue on web3 integration.

[D4nte]

Also, to investigate: In Eth-DM, the Eth-DM Public Key is signed with Ethereum account.
We store it in a custom protobuf message. Instead, could version 1 format be used to store the signature? I.e., is web3 signature method eth_sign compatible with web3 format? If so, then we should have symmetric encryption for Eth-DM Public Key Message and use version 1 instead of a custom format.

[D4nte]

Also ask Status team (keycard) to know what message encryption is possible.

[D4nte]

Also, to investigate: In Eth-DM, the Eth-DM Public Key is signed with Ethereum account.
We store it in a custom protobuf message. Instead, could version 1 format be used to store the signature? I.e., is web3 signature method eth_sign compatible with web3 format? If so, then we should have symmetric encryption for Eth-DM Public Key Message and use version 1 instead of a custom format.

Did some research: https://forum.vac.dev/t/eip-191-signature-and-waku-message-version-1/94