js-waku/examples/eth-pm-wallet-encryption
Franck Royer 9692b4af72
Rename Eth-DM to Eth-PM
"Direct Message" can lead to confusion with "Direct Connection" that
refers to low latency network connections.
2021-08-17 16:06:46 +10:00
..
public Init commit Eth-PM Wallet 2021-08-12 16:06:09 +10:00
src Rename Eth-DM to Eth-PM 2021-08-17 16:06:46 +10:00
.gitignore Init commit Eth-PM Wallet 2021-08-12 16:06:09 +10:00
README.md Add caveat section 2021-08-13 16:48:32 +10:00
package-lock.json Use Web3 wallet for encryption instead of generated keys 2021-08-12 16:42:35 +10:00
package.json Use Web3 wallet for encryption instead of generated keys 2021-08-12 16:42:35 +10:00
tsconfig.json Init commit Eth-PM Wallet 2021-08-12 16:06:09 +10:00

README.md

Ethereum Private Message Using Wallet Encryption Web App

Demonstrates:

This dApp demonstrates how to send and received end-to-end encrypted messages using the encryption API provided by some Web3 Wallet provider such as Metamask.

The sender only needs to know the Ethereum address of the recipient. The recipient must broadcast his encryption public key as a first step.

To run a development version locally, do:

git clone https://github.com/status-im/js-waku/ ; cd js-waku
npm install   # Install dependencies for js-waku
npm run build # Build js-waku
cd examples/eth-pm-wallet-encryption   
npm install   # Install dependencies for the web app
npm run start # Start development server to serve the web app on http://localhost:3000/js-waku/eth-pm-wallet

Caveats

This is a PoC with some obvious UX caveats:

  • As the message payload is fully encrypted, the dApp asks MetaMask who in turns ask the user to decrypt every received message (even if we are the sender).
  • This only uses Relay protocol to receive messages, meaning that participants must have the dApp open at the same time to receive private messages or public keys from each other.