pull down to refresh
141 sats \ 21 replies \ @melvincarvalho 1 Dec 2024 \ on: Cobra says developers are working to activate CTV bitdevs
Bitcoin doesnt need a soft fork
Taproot brought a handful of unexpected consequences (ordinals, etc)....I wonder what unknown side-effects CTV will bring?
reply
Taproot didn't bring ordinals.
reply
Hmm...really?
why are the leading ordinal group named Taproot Wizards?
reply
Ordinals has nothing to do with Taproot. I guess you mean Inscriptions. Taproot didn't make them possible, Taproot made them possible cheaper.
reply
My understanding is that it's the other way around.
Segwit made them cheaper... and taproot made them possible.
Taproot loosened the scripting language... to allow for arbitrary data.
And segwit allowed for larger amounts of data overall (to make Lightning possible at a later date) as well as making data cheaper to add to blocks (up to 4mb total).
Then crypto people came along later to sell jpegs to idiots. They did it on ethereum, then it got old. Now they've tried it on Bitcoin... and eventually people will figure out it's dumb and move on. Each inscription created, much less sold, is someone losing money. Eventually they run out of money. Rare sats, ordinal numbering schemes, memecoins... they're all the same.
They each cost the 'buyer' in opportunity cost by overpaying greatly for certain sats.. leaving them with fewer sats. Eventually they run out and the nfts are forgotten about.
reply
No, Taproot just removed limits on script size. But you could store the same amount of data in multiple transactions instead of one.
And segwit allowed for larger amounts of data overall (to make Lightning possible at a later date)
Lightning didn't need larger blocks but the transaction malleability fix that SegWit included:
While transactions are signed, the signature does not currently cover all the data in a transaction that is hashed to create the transaction hash. Thus, while uncommon, it is possible for a node on the network to change a transaction you send in such a way that the hash is invalidated. Note that this just changes the hash; the output of the transaction remains the same and the bitcoins will go to their intended recipient.
Before SegWit, tx ids were malleable and thus a lightning node could lose track of its channel open tx (and any txs that depend on it) while it's getting confirmed.
It was witness data from Segwit fork “Ordinals were made possible by two updates to the Bitcoin Protocol: Segregated Witness (SegWit) in 2017 and Taproot in 2021. These updates expanded the amount of arbitrary data that could be stored on the blockchain, allowing for the inclusion of images, videos, and other media types. While these updates were not specifically intended for NFTs, they inadvertently provided the necessary infrastructure for ordinals and inscriptions to exist.”
reply
Segwit was activated in 2017
Taproot was activated in 2021
I accept that Taproot used features of Segwit in order to use Ordinals....however trying to claim that "Segwit didn't enable Ordinals" seems pretty suspect.
reply
I think you're confusing inscriptions with ordinals. Inscriptions use ordinals but ordinals didn't need SegWit or Taproot. Ordinals is just a "numbering scheme for satoshis that allows tracking and transferring individual sats", see docs.
100% agree
reply