I remember from a few years ago apps had a identifying triplet: vendor, name and ID. This can now too be found in the APIs. If I understand correctly, the authenticator will hand out (sub)keys (?) to apps that identify themselves with that triplet. I assume these might have a balance so that the apps can then connect to the network with the provided keypair and access the network.
Is this correct? Could someone give an overview how it currently works (in terms of Rust/API) and perhaps even elaborate on how it’s envisioned to work?
I know it’s a little early for guides and detailed documentation on specifics, but perhaps I can be of more help with a better understanding than the high level view:
- Then, is the browser considered an app in itself? Will the apps/sites that run in the browser be considered sub-apps of the browser, or will the browser proxy the app authentication requests to the authenticator directly?
- What’s to prevent apps from identifying with a fake or different triplet? Can I use the CLI triplet and possibly profit from the already given permissions/keypair?
- The Wallet is a container type on the network. But isn’t it better to have something like (Bitcoin) hardware wallets where the addresses/keys are derived from the master (in-memory)?