Author: ZmnSCPxj 2022-03-22 16:47:33
Published on: 2022-03-22T16:47:33+00:00
In the given context, Russell and ZmnSCPxj are discussing a way to make referencing microcodes less complicated. ZmnSCPxj suggests that since each microcode represents a language based on the current OG Bitcoin SCRIPT language, they could replace Tapscript versions entirely. Every Tapscript version would be a slot for a microcode, and the current OG Bitcoin SCRIPT would be just one of those slots, i.e., `0xc2`. Filled slots cannot be changed, but new microcodes can use some currently-empty Tapscript version slot and have it properly defined in a microcode introduction outpoint. This approach would limit them to only 255 new microcodes, but it would bring down the cost of indicating a microcode to just one byte, which is already required currently anyway. It is important to note that microcodes represent an entire language that extends beyond OG Bitcoin SCRIPT and not individual operations within that language.
Updated on: 2023-06-15T18:19:33.214152+00:00