Version 29.1 won't work either, nor will 29, 28, 27, 26, 25, or any other version.
If you want your node to behave like Bitcoin Core 25 before the bug was found, you can only run knots.
What many people don't understand is that Core cannot filter the segwit discount and that datacarrier=0 does not work since version 25.
That's why we use Knots.
https://www.wiz.io/vulnerability-database/cve/cve-2023-50428
Version 29.1 won't work either, nor will 29, 28, 27, 26, 25, or any other version.
If you want your node to behave like Bitcoin Core 25 before the bug was found, you can only run knots.
I am just a bit afraid of running LN over knots, are my concerns nonsense?
I run cln with knots 29.1. There is one default filter you need to turn off I believe.
Which one is it?
This I think
blocksonly=0
permitbareanchor=1
I have setup a node with knots 29.1 and lnd 19.3 and so far no problem at all without any of those lines, are you running a baremetal node or something like umbrel and start9?
Start9. I just follow groks recommendations. I was told the ephemeral dust filter may cause problems with closures.
1. blocksonly=0 - Disables blocks-only mode (default 1 in Knots) to enable transaction relay and mempool, crucial for CLN’s channel funding and on-chain ops.
2. permitbareanchor=1 - Allows zero-fee ephemeral anchor outputs (default 0) for efficient Lightning channel funding.
Pardon me for being an ignorant retard, it seems based on nostr:nprofile1qqsd3fhv7rped64g77dyf9l7ndmae9mkxdz37099cc6wyzr9jytxg7cpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzamhxue69uhkummnw3ezuendwsh8w6t69e3xj7spr3mhxue69uhkummnw3ezumt4w35ku7thv9kxcet59e3k7mg9wx67f's article that using knots in the long run may lead to edits to the ledger to remove illegal data. If this is the case we may be choosing between a douche bag and a turd sandwich. (in terms of code, not people)
If the ledger is not immutable then we lose a major piece of what makes bitcoin bitcoin.
I am trying to wrap my head around this still. It seems like there may need to be a third path. It definitely is difficult to audit dashjrs code since the git commits are sort of squashed (from what I have read elsewhere) and he is just one dev after all.
Is this what a DAO is for? Am I getting into shitcoin territory?
100% Knots is not Luke’s goal. He is actually supporting and encouraging new implementations. Don’t look at Knots as the final destination. It’s a bomb shelter that we all need to squeeze into until we can rebuild.