Show HN: Web 3 Exclusive Features / Benefits – A Twitter Thread(twitter.com)
twitter.com
Show HN: Web 3 Exclusive Features / Benefits – A Twitter Thread
https://twitter.com/valuable/status/1472589751089831937
4 comments
Yes. On web2 you may need passwords and have to worry about how secure your users passwords may be. With web3 you can assume as a default that all users can use 256 bit keys with near infinite security. This is possible on web2 as well but isn’t feasible as it’s too hard to convince all of society to start using 256 bit passwords on existing platforms, whereas on web3 it’s a pre-requisite.
I mean, we have better with https://webauthn.guide/#registration and the such, which is able to use any TPM for a given system
Should I maintain separate keys per application? What happens if my key is compromised?
- - -
> Guaranteed 256bit Operability
> This one isn’t exclusive to Web3 in the sense that it’s not possible on Web2, but rather, it’s not feasible on Web2.
> You can design, on web3, with the assurance that every user is guaranteed able to participate in 256bit-key features.
what does this even mean, is it just to say everyone has a privkey?