Thread by @pedrouid

0/ Wallet vs Account discussion is pretty common in the crypto space

Unopinionated tech is important for decentralization but inefficient for shipping products to users and enable ecosystem-wide interoperability

I’d like to make a proposal below for standarization on this topic

1/ A Wallet is IMO the software or hardware which manages and/or stores private keys.

Traditional wallets which we carry physically have credit cards, identity cards, loyalty cards and cash.

These may constitute different Accounts which might be part of different networks

2/ Thus a digital Wallet may store private keys for multiple accounts which allow you to interact with multiple blockchains but also different layers.

Similarly to credit cards, we can have layer 2 solutions supported within in the Wallet. Same with identity cards.

3/ This brings me to the standardization part where we (focusing on EVM blockchains) need standards for making requests from Dapps to Wallets to interact with these features.

Using this separation of concerns between a Wallet and a Dapp provides better control to the User.

4/ Standarization however needed for developers to ship products without requiring coordination between multiple parties.

Allowing both ends to focus on their expertise.

There needs to be a broader scope JSON-RPC methods to cover these UX and Security improvements.

5/ Finally I would just like to add the way Dapps are sometimes designed to expect Wallets to handle connection to the network.

Within the scope of existing of JSON-RPC methods there are some methods which are conveniently more specific to Dapps and Wallets.

6/ Which adds to the separation of concerns which I propose of this standard definition of Wallets, Accounts and consenquently Dapps.

Here is a diagram to support my reasioning as a comparison of Web 2.0 vs Web3.

Fin.