I guess that’s why most nodes are not running latest updates
It still makes me nervous tho
Discussion
It’s pretty normal that the majority doesn’t immediately update to the latest version. Like not buying the v1 of the newest console.
I use my node regularly and I think I’m still on 24 or 26.
Will you update your mempool policy to include the new changes?
Typically I wait and observe for months before updating or making changes to my node if nothing critical is happening.
And the great part is I don’t have to do anything for the foreseeable future if I don’t agree or I could just leave core and run something else.
Im not a “core simp” as you’d call it 😅 but I personally wouldn’t run knots only because I’ve seen Luke do and say many questionable things over the years idc if he’s the rain man of bitcoin code 😂 I don’t trust him.
Short answer, probably eventually.
I’m being retarded with the accusations but I think it proves my point- according to btcframe the *latest* core nodes 29.0.0 are only 5.52% of network. 28.1.0 is higher at 20%
Protest knots are about 5% with 7.3% total now.
So I’m not saying “democracy” I’m saying:
If the update is supposed to achieve a consistent mempool across the whole network- how will that be achieved with the 5-20% of nodes that update to latest core software?
I’d love to see other implementations especially with cooler UX and nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx has made it clear they are welcome to apply with OpenSats.