Author: Russell O'Connor 2022-03-22 16:28:21
Published on: 2022-03-22T16:28:21+00:00
In a recent email exchange, ZmnSCPxj clarified the use of specific microcodes in Tapscript. The use of these codes is opt-in and requires the use of a specific `0xce` Tapscript version as well as referring to the microcode through its hash. According to ZmnSCPxj, the only race condition occurs when reorganizing out a newly-defined microcode, which can be avoided by waiting for deep confirmation. Fullnodes may need to maintain multiple microcodes, and creating new ones is expensive due to JIT compilation and the requirement that fullnodes keep an index that cannot have items deleted. The advantage of using microcodes is that the size of the SCRIPT can be used as a proxy for CPU load, allowing for bounded CPU load and approximate processing needed without requiring a softfork to modify weight calculations in the future. While Russell suggested that something like Simplicity would make a better platform than Bitcoin Script, ZmnSCPxj argues that the use of specific microcodes is a viable solution to namespace management issues.
Updated on: 2023-06-15T18:19:22.741384+00:00