Security in Web 3
There's a thing about the transition from Web 2.0 to Web 3.0.
🔐We are used to having our security taken care of by services we use, but it's not the case in Web 3.
Now we have to take care of it ourselves.
🔑Over time, control over your private key becomes the main concern of personal information security.
The more your money, information and identity is controlled by you and not the bank, Google or government – the more important it is to keep it private and unavailable to others.
We can't expect information security expertise from billions of web3 users, so security tools will be balancing between being easy-to-use, custodial and real security.
We'll see a spectrum of solutions: from centralized, fully managed and guaranteed by "Coinbases" and "Binances" of this world; to completely decentralized, in CLI format under Kali Linux.
Most will be somewhere in between.
It's unlikely that only one wallet will get a monopoly, but hundreds of wallets will operate based on a single standard, such as, for example, WalletConnect today.
Social recovery methods will become increasingly popular: when the user's key is not stored in one centralized repository, but is divided into several pieces.
One of those parts is not enough to get access to the wallet, but for example 5 out of 7 will be enough.
In this case, there is no single seed phrase you can lose along with access to thousands of your BTCs and ETHs. But you are not 100% relying on some service that can run away with your money at any time.
We start gradually with CeFi products that use DeFi.
🚀The step into DeFi is already predetermined, but we are being gentle with bringing users there.
16 comments