A lot going on here, i am learning too.
tension between Bitcoin Core and Bitcoin Knots stems from ideological and technical disagreements within the Bitcoin community, particularly around mempool policies and transaction filtering, such as handling Ordinals and inscriptions.
Oh yeah I'm aware of that, I've done a lot of thinking about it. I was confused about the rest I guess.
it’s relevant to note that Counterparty relies on OP_RETURN to embed data for its tokens and smart contracts on Bitcoin’s blockchain. Core’s v30 changes could make it easier for Counterparty transactions to propagate, while Knots’ stricter policies (e.g., datacarrier=0) could filter them out, potentially affecting Counterparty’s usability on Knots-run nodes. This aligns with the broader debate about data-heavy transactions, where Knots aims to limit what Core permits.
Knots' default for datacarrier is either 42 or 83, can't remember which. They ensure they will always keep it configurable. I run mine at 160. Knots is just better.
It respects user choice, and therefore has greater respect for property rights.
you are ignoring parts of the mempool to your own detriment that are just going to get propagated and confirmed by people who don't have a mental disability https://video.nostr.build/ef064c7537936b458d4ae7307f0f0a169de7e333c9003195200d69ec9e135a84.mp4
Always uping our game...
Learn or get left behind
