By repeatedly adjusting default mempool policy to match what miners will accept anyway (large OP_RETURN uncapped because “they’ll just mine it via bypasses like Libre Relay, or direct APIs”), we...
One way I like to think about it is: Your node allows you to control YOUR experience of using Bitcoin, but it doesn't give any control over the network.
So the reason to run a node is really to verify your own transactions, not other people's.
But that cuts both ways. A node run by an exchange or a miner can't determine your experience of using or verifying Bitcoin either.
However all nodes agree to the consensus rules, so only changes to the consensus rules matter. Otherwise you can just run another client or an old version.
And to be honest I'm on the fence about BIP 110 because I feel like a lot of the time it's either framed dishonestly or a lot of supporters don't understand it. But it's BIP 110 which is actually changing OTHER people's experience of Bitcoin, i.e consensus rules, not the other way round.
So the reason to run a node is really to verify your own transactions, not other people's.
But that cuts both ways. A node run by an exchange or a miner can't determine your experience of using or verifying Bitcoin either.
However all nodes agree to the consensus rules, so only changes to the consensus rules matter. Otherwise you can just run another client or an old version.
And to be honest I'm on the fence about BIP 110 because I feel like a lot of the time it's either framed dishonestly or a lot of supporters don't understand it. But it's BIP 110 which is actually changing OTHER people's experience of Bitcoin, i.e consensus rules, not the other way round.
1
