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.