Backend for accounts

[sestinj]

Users who accept grants (or all users, really) need to be able to sign in with their email. While we act as their union, we will store their DID and secret key. Just need a backend for this, can happen through AWS, GCP, Firebase, whatever. At some point we'll want to make sure we've left a way for the ecosystem to create non-custodial unions, but this works for now. Coinbase proves that people trust it.

The backend should receive a request to create an account that includes

• email
• password
• grant token and then on the backend it will randomly generate a DID with secret key, store this stuff somewhere safe (encrypted by what, because the password will be encrypted...) (probably store in the keystore files of node, and then store the username and password with GCP.

[sestinj]

We should build 2 backends:

1. Sign in with email to our union, we store your data
   • Use MongoDB or something on backend for storage. AWS/GCP user authentication, run the node on EC2
2. Non-custodial browser extension and IPFS data storage
   • Store the private keys in browser data store, use IPNS files for resources ...Is a local-only data storage a good idea?

[TyDunn]

@sestinj are we (the union) storing data in the beginning?

[sestinj]

@TyDunn Def not for any enterprise use case, but thinking about how to quickly get people onto the network through backendless webapps, it makes sense not to force the user to setup their own data store. So in that situation, yes, either we will manage a datastore for users. Or they can use IPFS to store everything publicly, but now that I think of it, this would require using IPNS, which would require running an IPFS node, so that's not ideal either. Could use Filecoin but then users have to pay.