Notable changesNotable changes

Default configuration changesDefault configuration changes

• When -dbcache is not set explicitly, Bitcoin Knots now chooses a RAM-aware default between 100 MiB and 2 GiB. The selected -dbcache value is still used for both IBD and steady-state operation and unused mempool allocation may be shared with this cache. In environments with external memory limits (e.g. containers), automatic sizing may not match effective limits. The previous behavior can be restored by setting -dbcache explicitly. (bitcoin#34641)

New spam filtersNew spam filters

• Transactions creating outputs with a value less than the expected value to spend them (ie, "dust") are now treated by policy as if those outputs had a value at least meeting that threshold by having their effective fees reduced by the difference. This only affects transactions otherwise allowed by your node policy (it does not expand the range of accepted transactions), so typically this only applies to datacarrier or anchor outputs. It is enabled by default, and can be disabled with subdustfeepenalty=0 (or the GUI option) in your configuration. (knots#272)
• Datacarrier policy options now match a newer variation of spam designed to bypass the prior implementation. (knots#292)

New featuresNew features

• The sweepprivkeys RPC method now looks for segwit (p2wpkh) and taproot (p2tr) UTXOs, in addition to the older p2pk and p2pkh formats. (knots#296)
• "Sweep private key" dialog added to the GUI (File menu) for easy access. (knots#297)

P2P and network changesP2P and network changes

• Tor hidden services that are created automatically by Bitcoin Knots will have PoW defenses enabled if the Tor daemon supports that. (bitcoin#33414)