mirror of https://github.com/waku-org/js-waku.git
c5d1ea86f1
Bumps [@testing-library/jest-dom](https://github.com/testing-library/jest-dom) from 5.14.1 to 5.16.1. - [Release notes](https://github.com/testing-library/jest-dom/releases) - [Changelog](https://github.com/testing-library/jest-dom/blob/main/CHANGELOG.md) - [Commits](https://github.com/testing-library/jest-dom/compare/v5.14.1...v5.16.1) --- updated-dependencies: - dependency-name: "@testing-library/jest-dom" dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| config | ||
| public | ||
| src | ||
| .env | ||
| .gitignore | ||
| README.md | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.json | ||
README.md
Ethereum Private Message Using Wallet Encryption Web App
Demonstrates:
- Private Messaging
- React/TypeScript
- Waku Light Push
- Signature with Web3 using EIP-712:
eth_signTypedData_v4 - Asymmetric Encryption
- Usage of
eth_decryptWallet API
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.