In the web3 network, the ideal state is that with one DID account, you can connect to and enjoy all services, even all network services, including web2, so that users no longer have to worry about remembering account passwords one by one, and they don’t have to worry about personal privacy data leakage. But the reality is bleak. Not to mention that the web2 network is impossible, even the web3 network, because there are different public chains and different networks, it means there are different account systems. Moreover, for some purpose, individuals may also create many different accounts for different environments. The direct result is that no matter what, users have a bunch of accounts to manage and a bunch of passwords to remember.
Most wallets support multiple chains by using the same seed and then generating the corresponding key pair according to the algorithm of the target public chain. In other words, these different accounts are actually generated by the same seed, which is essentially one account. If you already have different accounts on different chains, or different accounts on the same chain, it is impossible to manage these accounts in a unified way for most current wallets. The fundamental reason for this problem is that these wallets do not support saving users' encrypted data.
For the super account of TinyVerse Space, unlimited connection and expansion capabilities are natural attributes, because the super account of TinyVerse Space can save the user's encrypted data. No matter what type of data the user wants to save, it can be saved, even if the data is a certain account and password. This capability eventually becomes a sub-account management module. Users can create a new sub-account at any time, select the public chain to connect to, and then have the ability to connect to the public chain. Users can also import existing wallet private keys, so that old wallets can make full use of the convenience provided by the super account of TinyVerse Space, without worrying about the account recovery of old wallets.
TinyVerse Space super accounts can not only connect to web3 services, but also web2 services. Because for super accounts, any network service is just a combination of RPC address, username, password and other information. As long as the connected service has an open interface, it can become a sub-account of the super account. Even if a network service does not have an open network interface, users can save the username and password of the service, so they don't have to worry about retrieving the password after losing it.
There are countless sub-accounts of different types under the super account. Combined with the TinyVerse Space app plug-in platform, developers can create endless account management solutions for themselves or users, suitable for different individuals, teams and organizations. For example:
1. You have planned different sub-accounts for yourself to cope with different usage scenarios. One is a large-amount wallet that can be hidden from others; one is for daily small payments; one wallet is for investment; if there are different projects, different wallets may be needed for docking, etc. A person may need many wallets to ensure a certain degree of privacy.
2. If you are the boss of a team and you have the private key of the wallet, you can assign the approval authority of the wallet to an approval team and let this team manage and use it in daily life according to the rules of the MPC wallet. However, the final approval authority and ownership still belongs to you as the boss.
3. Combined with the smart contracts that will be supported soon, the potential of sub-accounts will gradually explode.
