What I wish is that there was some way to tie my other accounts, directly or indirectly, to my bank. My bank account is the most recoverable account I have, because they can handle me showing up in person with ID.
Other accounts just know me by my knowing the account password and/or being able to receive emails at the email address associated with the account. If either of those is compromised I can lose the account with no way to recover.
If there were some way I could have my bank verify my identity to my email provider, and tell my email provider that if account recovery is ever needed on my email account to re-verify with my bank that it is really me requesting the account recovery it would be much safer.
(If you are using an email address at a domain you own, then replace email provider with domain registrar).
Then no matter how badly I'm compromised (as long as it is not by someone with sufficient resources and interest to be able to get past an in-person identity check at my bank), I've always got a path to recovery.
Worst case, first recover the bank account in person. Then recover the email account using the bank account. Then recover compromised accounts that are using the email account for verification.
If there were some way I could have my bank verify my identity to my email provider
Major banks can do their end of that. They will notarize documents and provide signature guarantees for established customers. Now, having obtained a notarized statement guaranteed by a major bank that you own your identity, how do you submit that to Gmail?
Banks don't really want to be in the authentication business anyway. It's an unprofitable sideline, and takes up a lot of staff time.
Of course, all this depends on the assumption that your ID should be who you are IRL, rather than the model where we can all make up several independent pseudonyms for different purposes.
Estonia's implementation is usually regarded as one of the best: https://github.com/open-eid
Sure, that would work too. Or even do both. The point is to have some place I can go in person to have my identity verified for a third party such as an email provider or domain registrar. Then set up the email or registrar accounts so that account recovery requires such a verification.
I wouldn't have to tie everything back to the in person verification. Just things that I want to be sure I can recover if I lose them via accident or hacking.
I don't think that helps the Web3 argument. Google has made a choice, whereas crypto it is a technical limitation (or, to some, a feature). It also isn't a very good talking point to say "it's no worse than Google"
Crypto needs to develop a better balance between bad 2FA with loop holes on the traditional side and absolute loss on the crypto side before a lot of people would feel comfortable with it. Maybe that should be one of its target killer apps.
But what would a 3rd party or 2/3 party consensus use that would differ from current mechanisms?
There would also need to be some care taken to make sure that such 3rd parties don't become centralized choke points themselves: They would be somewhat essential, so any service(s) that did this could rise to dominance either as a monopoly or a cartel.
Let's say I control some funds and want you to have access to recover the funds if I lose my master key. I transfer these funds to a smart contract that allows my Ethereum key full control to move things around, and allows your Ethereum key access to give control to a new key if I lose mine (probably with a x-day delay, so I have time to revoke your access if you go rogue!).
For a 2/3 system, it's basically the same except 2 out of 3 of the other people need to "vote" on chain, and only then can my key be reset.
There wouldn't need to be a centralized party who resets the keys. Social solutions where you give trusted friend(s) limited reset access, probably with a time lock like I mentioned, are extremely promising IMO.
The smart contract you describe is sort of what I meant by service providers emerging for this sort of thing: The average user will not feel comfortable rolling their own such contract. It either needs to be dead easy, or there will emerge services that do this for you and oversee their execution. I could be wrong about that... Much of what Web3 will look like is speculation. But if those sorts of services emerge and become market dominators, they would have a lot of control-- contracts that allow termination (deplatforming). As contracts become more complex to avoid edge cases we see being exploited right now, it may become even harder to understand all implications, loopholes, exploits, etc.
The above may be a solvable problem: Develop tools to parse smart contracts. A specialized class of automated testing tools for smart contracts.
Obviously this hinges on the contract not being backdoored by its creator to begin with, but collections of free, open source, audited smart contracts for stuff like this already exists. A user would likely use some app / tool to deploy their instance, once deployed it's really simple to verify the deployed code matches the verified open source version.
It's all shitty and it's all infuriating.