Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potentially infeasible #14

Open
lastmjs opened this issue Jun 18, 2020 · 0 comments
Open

Potentially infeasible #14

lastmjs opened this issue Jun 18, 2020 · 0 comments

Comments

@lastmjs
Copy link
Owner

lastmjs commented Jun 18, 2020

This app is potentially infeasible, mostly because of these concerns: MetaMask/metamask-extension#1190 (comment)

If we don't want the user to have to enter their private key into the application, then we need to somehow send up an encrypted message to something that can decrypt the message. MetaMask is the obvious candidate. But, MetaMask only supports nacl decryption in v8, which requires a new public key derived from a user's private key. This means that users must communicate their public keys with each other out of band of the base Ethereum protocol...this is not ideal.

The point of Ethereum PM was to allow any address to communicate with any other address, while only knowing each other's addresses and at least one transaction sent by each address.

A possible solution is to create a smart contract that maps public keys generated by MetaMask to addresses, but that seems like a lot of work for the user, and they wouldn't be able to send a message to any other address.

We'll need to think about the feasibility of continuing with this project given these constraints.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant