DireMunchkin

GN nostr 😴

Interesting proposal from Majorian here: https://xcancel.com/MajorianBTC/status/1983205211901448330 As an alternative to BIP-444 it would just reduce the max size of OP_RETURN to 83 bytes by consensus. Unlike BIP-444 it's permanent, not temporary, but it does not address any other form of spam / data carrying on Bitcoin. (I.E inscriptions.) My 5 sats: I'm a bit uncomfortable with some aspects of BIP-444: It being a expiring soft fork is a first, and I don't like novel changes. The reactive activation scares the shit of out me. This change is a lot simpler and less risky. On the other hand it will not solve the spam problem - Main thing is Inscriptions are still in after this hypothetical fork. So this seems a bit insufficient in that regard.

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qpq0r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7s85uvay nostr:nprofile1qyt8wumn8ghj7ct8vaezumn0wd68ytnvv9hxgtcpz9mhxue69uhkummnw3ezumrpdejz7qpqwf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgshcqyxr The Syncthing-Fork app has been taken over by a new developer of unknown provenance. See thread here for details: https://forum.syncthing.net/t/does-anyone-know-why-syncthing-fork-is-no-longer-available-on-github/25661/1 You may want to pause signing the updates from there until the situation has been clarified.