@alex Do you know what payment system bans no one? Bitcoin.
@valleyforge No shit, been spending the past 2 weeks integrating it. It comes with major trade-offs tho.
@valleyforge @uoya Yep. Centralization also has some advantages. You can dispute charges and have a chance of getting it back. With Bitcoin you can accidentally send funds to an invalid address and the money becomes lost in a void forever.
@alex
Pretty sure that problem of sending BTC to a mistyped address was solved years ago, no?
@valleyforge @uoya
@dsfgs @valleyforge @uoya How? As long as it’s the right length and character set, all addresses are valid. It’s just that most don’t have a private key held by a person. There’s no way to tell.
@mittimithai @dsfgs @alex @uoya so its basically the same system as credit card numbers
@mittimithai @valleyforge @dsfgs @uoya Parity digits would fix the problem, but I can’t find any info about whether bitcoin addresses actually use them.
@mittimithai @dsfgs @uoya @valleyforge Seems like maybe it does:
Several of the characters inside a Bitcoin invoice are used as a checksum so that typographical errors can be automatically found and rejected. The checksum also allows Bitcoin software to confirm that a 33-character (or shorter) invoice is in fact valid and isn’t simply an invoice with a missing character.
@alex
Are these checks for all the three types of addresses?
The above resource was not clear.
@mittimithai @valleyforge @uoya
@valleyforge @dsfgs @alex @uoya you could send a payment to a an address that no one owns in principle, but client applications make that difficult for the user to do (and that’s easy functionality to make in an application). Credit cards are centralized so it is impossible to do there