Of course, nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk is worried about fork futures because he knows that will effectively reveal the lack of support for his fork, just like it did for Segwit2X back in 2017.
OP return, was a third rail for our community and this was pushed through regardless of negative community sentiment that was present…….
Foolish move for sure as second order effects were never taken into account by Bitcoin Core as they lost 20% dominance………
This myopic view by Core has galvanized the community and don’t be surprised the support Luke receives because of this……
Pretty tragic that legitimate necessity for blown open op return never existed in first place and here we are……..
Node runners will never forget the failure to patch by Core that expanded the data set 100’s of gigabytes through inscriptions……
Inscriptions were harmful to Bitcoin and now we have blown open Op return that is also harmful to Bitcoin……
It seems that you are more worried for whatever reason ...
