waku-org
/
js-waku
mirror of https://github.com/waku-org/js-waku.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
js-waku/examples/eth-pm-wallet-encryption
History
Franck Royer 49e08ff1c2
Upgrade examples to js-waku@0.24.0 		2022-06-01 11:19:27 +10:00
..
config eth-pm-wallet: Remove crypto-browserify 2022-05-11 15:54:54 +10:00
public Init commit Eth-PM Wallet 2021-08-12 16:06:09 +10:00
src Use js-waku from npmjs.com instead of local build 2022-05-03 10:47:13 +10:00
.env Remove ReactJS warning about webpack 2021-10-12 11:43:29 +11:00
.gitignore Init commit Eth-PM Wallet 2021-08-12 16:06:09 +10:00
README.md Fix phrasing 2022-05-13 16:06:24 +10:00
package-lock.json Upgrade examples to js-waku@0.24.0 2022-06-01 11:19:27 +10:00
package.json Upgrade examples to js-waku@0.24.0 2022-06-01 11:19:27 +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.

The master branch's HEAD is deployed at https://js-waku.wakuconnect.dev/examples/eth-pm-wallet-encryption/.

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.