3 ms·
We certainly have the ability to implement transfer authorization, from the sender side, using good authentication technology. This doesn’t have to be cryptocur
by matthewdgreen 2y ago
We certainly have the ability to implement transfer authorization, from the sender side, using good authentication technology. This doesn’t have to be cryptocurrency: it can just be the same techniques that we use to authenticate people logging into their bank account, eg passwords, MFA, passkeys, Face ID. We don’t do that for a bunch of business reasons given in the article (mostly that sending institutions are disincentivized from enabling this, and regulators have come up with a kludge that spreads the losses out in weird ways.) The result is that we use a system based on trust, reversal and insurance. This seems fine, but it almost certainly raises costs across the entire system in ways that we can’t obviously measure. Those costs presumably show up in places that typical consumers can’t really see, unless they’re very sophisticated: for example, higher management costs and worse spreads and weird fees.
- TheNewsIsHere 2y agoInsomuch as this is a problem, I also don’t think it will change materially any time soon. A robust financial system has to be reasonably accessible to such a wide range of people and institutions with varying capabilities that even building something that caters exclusively to the technically inclined is all but impossible. I wrote on here before about how Vanguard used to offer a FIDO2-only MFA option. You could disable SMS MFA. That eventually got removed because the mobile app never supported it, so now they’ve enforced SMS as a mandatory MFA factor. And FIDO2 has been fairly easy to implement on mobile for years before Passkeys specifically were pushed.