If you really want to understand the Bitcoin Core debate, I suggest you go and read the actual Pull Request on Github.

That’s exactly what I’ve done - and this thread will break it down for you. 🧵 Context: This PR proposes changes to Bitcoin Core by removing default limits on OP_RETURN - a part of transactions used to store data. Currently, Core only allows a small OP_RETURN per transaction. The change would allow much larger OP_RETURNs, making Core more permissive in what it relays.

BITCOIN WALLETS AND NODES.

All bitcoin wallets must connect to a node to fetch your balances and transaction history.

This can LEAK sensitive data to other people.

[THREAD 👇] By default, most bitcoin wallets connect to a third party node.

The problem is that you must leak your public keys and addresses to that node, so that they can tell you your balance and transaction history.

NEVER reuse #bitcoin addresses.
It is terrible for your privacy.

[THREAD👇] If I use the same address for everything, all my transaction history is linked to 1 address.

Anyone with that address can see how much bitcoin I have, and every transaction I have ever made.

It is as simple as putting it in a block explorer:

Here is the best bitcoin setup for Mac users.

Nothing but your Mac device is needed, other than an optional external SSD.

southernbitcoiner.com/bitcoin-mac/ It’s a simple, but powerful setup.

@bitcoincoreorg to verify your own transactions. No leaking your data to third parties.

@SparrowWallet as your wallet. It’s feature packed and can do everything a Bitcoiner needs.

@SamouraiWallet privacy tools are built into Sparrow.

How to use SeedSigner with Blue Wallet:

I cover:

1. SeedSigner settings
2. How to create a seed in SeedSigner
3. How to export wallet XPUB to Blue Wallet
4. How to receive bitcoin
5. How to send bitcoin (build and sign partially signed bitcoin transaction, or PSBT)