-
@ Jordan S
2025-02-11 15:59:39
To clarify, of course you can implement anything hypothetically on something but it's usually more optimal to integrate the optimal code sets into the optimized technology.
Bitcoin needs to hone in into its primary purpose which is peer to peer digital cash because that's what it's most optimal use case is.
It needs to stop acting like it does everything in the most efficient manner.
And maybe drive chains change this perhaps but in practice Bitcoins supply cap prevents a lot of technological things from running especially when you need negative integers, and integers which exceeed 21 million.
Yes, I know decimalization but then you have to assign every sat to a use case, and inscribing information to the blockchain for file storage, Ordinals, and other use cases becomes more complex the more information you ascribe to a sat, and perhaps you could use headers, and checksums to differentiate implementations dedicated to a Sat, and even then there's a potential for headers to fail to differentiate since some headers might start with the same, or similar header.
Like let's say ticket Master uses The Ticket Header but also The New York Train station uses The Ticket header too, perhaps with an advanced checksum it could be counteracts, or with a protocol that forces headers assigned to sats to be differentiated like Ticket Masters header would TicketMaster-Tickets, and NYC would be NewYorkTrains - Tickets, or something like that.
Point is, let optimized technologies be built on the most optimal use case for it, and don't try to force bitcoin to be everything because it isn't everything, it's not optimized for everything.