[account-web-vault] Refactor how database endpoints are specified

[tahpot]

Key requirements:

• We need to pivot the architecture so that an end user, by default, is responsible for setting the service endpoint(s) to use for a given application context.
• We also need to ensure an application running on testnet that talks to user's Vault ensures the Vault is running in testnet mode as well.
• We need to make connecting an application to the Vault much simpler, which is currently complicated by the need to specify database endpoints.

Changes required:

• Applications are no longer required to specify endpoints when connecting an account to the Verida network via the Vault (this will still be required when using the account-node package). Task
• The QR code must specify the network being connected to (testnet, mainnet), so the Vault can construct an appropriate response with correct service endpoints for the requested network. Task
• The Vault must be updated to understand different networks (login screen, settings). Task
• The Vault must be updated to allow users to specify their own default endpoint or host their own. Task
• The developer interface for connecting a user to an application must be simplified to it's minimal requirements. Task

Suggested interface:

const options = {}
const context = new Context(`CONTEXT_NAME`, 'testnet', options)

[nick-verida]

I think this is mostly right, except how does an application developer supply a default storage node if they choose? If I'm using a Primacy app I think I'd expect to use their node unless I explicitly decide otherwise.

I think maybe something like this is what we want (this really should be a state table):

Case 1

• dev specifies mainnet/testnet
• user specified nothing
• Storage is in Verida node on mainnet/testnet

Case 2

• dev specified mainnet/testnet
• user specified their own preference
• Storage is on the user chosen preference

Case 3

• dev specified their own storage
• user specified nothing
• Storage is on dev specified node

Case 4

• dev specified their own storage
• user specified their own preference
• Storage is on the user chosen preference

[tahpot]

That makes sense. The key here is the user has choice, which will need to be presented to them in the Vault screen when they sign into an application context for the first time.

The user will always have a default storage node available (via the Vault). As such, I think there's just two options:

1. Developer doesn't specify a storage node. The storage node will default to the user's Vault default.
2. Developer does specify a storage node. The user will be asked which storage node to use; the developer supplied storage node or their own. This could even have a default setting where the user always selects one or the other

[nick-verida]

What if the developer specified testnet and the user chooses their own node?

The dev then moves into production, specifying mainnet, and the user remains on their own node. The context name is the same (I assume?)

The user might move back to the testnet version. Would this then corrupt (overwrite/combine) data?

[tahpot]

What if the developer specified testnet and the user chooses their own node?

The Vault will now have a distinction between testnet and mainnet nodes.

As the QR code will be updated to specify the network, the Vault can use this to ensure it only links a node for the user that is running on the correct network.

[nick-verida]

But when the user specifies their own storage do they need to understand the difference between mainnet and testnet?

[nick-verida]

does the context name and environment need to be combined somehow? So if you have on personal storage node, the same context name and are switching between mainnet and testnet they appear different environments?

[tahpot]

But when the user specifies their own storage do they need to understand the difference between mainnet and testnet?

Probably not.

The majority of users will be on mainnet when they first install the app and will remain in that mode unless they specifically go into their settings and switch to testnet.

As such, adding a storage node will add that node to the currently selected network in the app.

I'd expect developers to know what they're doing and be following instructions to switch to testnet before adding a testnet storage node.

does the context name and environment need to be combined somehow? So if you have on personal storage node, the same context name and are switching between mainnet and testnet they appear different environments?

I'm not sure what you mean here.

[tahpot]

Looking for @pranavburnwal feedback here.