Thread

I encourage you to read the code and verify for yourself. It’s not complicated code. I read the policy.cpp source code on GitHub and concluded that Knots 29.x uses virtually the same policy code as Core 29.x and adds a few filters that Core should have adopted to mitigate non-financial arbitrary data like inscriptions. Long-term, some of these filters would need occasional updates like a game of whack-a-mole if spammers keep changing their code (e.g. “tx.nLockTime == 21”), but the fact that a hack will be mitigated discourages people from doing it. It’s like locking your front door - that won’t stop a hardened criminal, but it will stop a lot of petty crime and encourage them to go to a different neighborhood. https://github.com/bitcoin/bitcoin/blob/29.x/src/policy/policy.cpp https://github.com/bitcoinknots/bitcoin/blob/29.x-knots/src/policy/policy.cpp