
Everyone can agree that we need more decentralized block template construction. Core sees private tx broadcast as a threat to that (which is fair imo), which is part of why they are widening default policy rules. Most filter proponents are vocal ocean supporters. Ocean have already materially increased the number of entities (who are actually finding blocks) doing template construction with DATUM, currently I imagine most of these individuals are using knots, and interestingly many donât filter out all âspamâ. Knots has (iiuc) a single individual who decides what gets merged, and no doubt eventually there will be something he does / doesnât do that will be perceived as an artificial restriction on user choice. Ultimately, the only way miners will have sufficient choice without restriction will be if they can construct their own policy (with ease) and we have already seen an example of this (Knots Lua Pull) and a more recent BIP draft to do the same in Core (see mailing list, not received well) The (perceived) threat with anything like this, is that âactual censorshipâ is as easy as mandating the inclusion of a filter file, and template construction is sufficiently centralized currently that IMO this is a reasonable concern. Which brings us back to the point on which we have unanimous agreement: there is a pressing need to decentralize block template production. Any action to decentralize block template production should be celebrated. Knots Lua Implementation https://github.com/bitcoinknots/bitcoin/pull/119/files JS BIP Draft https://github.com/dr-bonez/bips/blob/mempool-policy-scripts/bip-mempool-policy-scripts.md