Not exactly. Matrix 2.0 relates to the protocol (Matrix) version, which has its major number incremented due to a bunch of, well, major changes/updates to make it much better. OIDC, sliding sync and native calls are some of the new things that comprise the 2.0 update.
The server implementations are somewhat orthogonal to this. Synapse (the original Python server) is still the main implementation, and is Matrix 2.0 ready.
Yeah withdraw cash from an ATM and use it. The system sucks, but it’s not trivial to change for a myriad of reasons.
There’s no real way to do it. Unless you know someone who can trade you XMR<->cash and you somehow convince your employer to (break laws and) pay you in those forms, you can’t avoid it. At some point, you’ll have to get money on a real bank account, which requires real information to open.
As far as I know, modern cards don’t just send your CC info to terminals, they do some form of a cryptographic handshake (probably a pubkey signature or similar) which gets confirmed by your bank. I believe Caveman was talking more about online shopping, where you have to enter your card number, expiration date, CVC and often your name too.
That’s why I love virtual card systems like MB NET. You just generate a random virtual card for every purchase (or a recurring one for each subscription vendor, for example) and move on. Your bank still knows what you’re doing, of course, but vendors can’t correlate anything. Preventing your bank from knowing where you’re spending your money is much harder, for very practical reasons: fraud detection. The only real way is to use a secure crypto coin like Monero, but very few places accept it and you still have to deal with volatility.
I still don’t think it’s there, but development hss been fast, so a lot has changed and improved in the last couple of months.