SATD BITCOIN NODE POSTS A TRANSACTION-FILTER LANGUAGE — ITS OWN MANUAL SAYS FILTERING “CANNOT PREVENT CONFIRMATION” — THE NODE COUNTS FILTERED TRANSACTIONS MINED ANYWAY

A bitcoin full node written in Rust, called satd, now lets the person running it write rules for which transactions to hold back. The developer, bkeroack, posted the design to Delving Bitcoin on October 20, 2026. A rule can keep a transaction out of relay, out of the node's block templates, or both. It never changes what the node accepts as valid.

The useful part is what the manual admits up front. “Filtering cannot prevent confirmation; it can only decline to assist it.” There is no reject. A filtered transaction sits in a separate quarantine pool, 50 MB by default, and a command called getquarantineinfo reports how many of those held transactions were mined anyway and how much in fees the operator gave up by not mining them.

That turns the filter fight into something you can check instead of argue. If you think filters work, your own node will show you the count of filtered transactions confirming, block after block. The node also refuses to load a rule that would hold back Lightning enforcement transactions unless the operator sets allowdangerousfilters=1, because a broad relay filter can quietly stop a channel's penalty transaction from confirming.

This is a small project. The GitHub repo shows 8 stars and one main author, and the filter code has been in it since June 16, 2026. But the claim it makes about filtering is one any node runner can test. At the time of this writing, bitcoin was $82,890.