Quote from: larry_vw_1955 on Today at 06:40:33 AM

Quote from: Felicity_Tide on Today at 05:50:28 AM

Whether we like it or not, the problem of scabiliity is not a topic that should be treated as a done deal.

the way its being worked on is like this:

https://www.msn.com/en-us/money/other/mastercard-launches-p2p-crypto-transactions-across-14-countries/ar-BB1nh8Kp

Global payments giant Mastercard just launched the first P2P pilot transaction of Mastercard Crypto Credential. This new service will allow users to send and receive crypto using aliases instead of blockchain addresses.

The way you could implement such a thing into Bitcoin would be like you could have DNS entries for a particular domain where you define one record for the alias you want to use, containing a signed BIP322 transaction. The record is being used as a challenge.

for example:

For Bitcoin.org

TXT record for "btc.challenge.alice": <BIP322 signed transaction which includes the address in the transaction body being sidned>

To be able to send bitcoin to alice@bitcoin.org

Now this presents two benefits:

1. You can have as many aliases for a domain as you want, just by replacing alice with some other name like bob, and this creates records with two different names
2. You can actually verify that alice@bitcoin.org owns an address like 14758AB.... because the signed transaction also includes the public key in the scriptsig/witness data.

Sure, it wouldn't be random aliases, but I imagine in order to fix that you'd be able to take the hash160 and a large enough dictionary list of words, and assign every 20 bits to a dictionary word.