Posted by bramcohen
Mar 14, 2024/23:44 UTC
Bitcoin scripts possess an inherent communication mechanism through the transactions they are part of, allowing for the possibility of aggregating multiple smart Unspent Transaction Outputs (UTXOs) into a single, larger transaction. This aggregation facilitates a common ground for understanding through the use of free-form statements within the transactions. Additionally, the input list of a transaction can be utilized to enforce certain capabilities, suggesting that while special opcodes might be necessary for detailed discussions regarding these aspects, their implementation is feasible.
A notable distinction between Chia and Bitcoin lies in how their scripts interact with external references. In Chia's design, script execution is strictly internal, prohibiting any reference to external elements and only permitting the return of conditions. On the other hand, Bitcoin allows for limited direct references to the external world through assertions. These assertions enable Bitcoin scripts to directly assert facts about their transactions and other external factors, providing a functionality similar to the conditions returned by Chia scripts. Each approach has its advantages and disadvantages, but the tradition of Bitcoin scripts making direct assertions might be preferable for future developments in BTC Lisp.
TLDR
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project?
Give Feedback