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

Merge pull request #265 from status-im/update-changelog 

Update changelog for Eth-PM Wallet Encryption changes
This commit is contained in:
Franck Royer 2021-08-13 20:09:21 +10:00 committed by GitHub
parent 5be718ffdb 0e8062d32e
commit 43f57aeb3e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGELOG.md
View File

@ -22,6 +22,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
it is a type used for the [TOY-CHAT](https://rfc.vac.dev/spec/22/) protocol; it is a type used for the [TOY-CHAT](https://rfc.vac.dev/spec/22/) protocol;
js-waku users should not build on top if this toy protocol and instead design message data structures appropriate to their use case. js-waku users should not build on top if this toy protocol and instead design message data structures appropriate to their use case.
### Added
- Examples: New [Ethereum Private Message Using Wallet Encryption Web App](./examples/eth-pm-wallet-encryption/README.md)
example that demonstrates the usage of `eth_encrypt` API (available on Metamask) and EIP-712 for typed structured data signing.
## [0.10.0] - 2021-08-06 ## [0.10.0] - 2021-08-06
### Added ### Added

7
examples/eth-pm-wallet-encryption/README.md
View File

@ -25,3 +25,10 @@ cd examples/eth-pm-wallet-encryption
npm install # Install dependencies for the web app 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 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.