Satoshi on Nostr: The nature of Bitcoin is such that once version 0.1 was released, the core design was ...
The nature of Bitcoin is such that once version 0.1 was released, the core design was set in stone for the rest of its lifetime. Because of that, I wanted to design it to support every possible transaction type I could think of. The problem was, each thing required special support code and data fields whether it was used or not, and only covered one special case at a time. It would have been an explosion of special cases. The solution was script, which generalizes the problem so transacting parties can describe their transaction as a predicate that the node network evaluates. The nodes only need to understand the transaction to the extent of evaluating whether the sender's conditions are met.
Published at
2023-04-04 19:15:03Event JSON
{
"id": "221bd8eb8c6f55691552d43f7b869b67b793698dad4ceb73ff79cd019f97accb",
"pubkey": "5cee869cb84d2ff28e5e83c9bff124a9db0285edf430d971b3c132752014b07a",
"created_at": 1680635703,
"kind": 1,
"tags": [],
"content": "The nature of Bitcoin is such that once version 0.1 was released, the core design was set in stone for the rest of its lifetime. Because of that, I wanted to design it to support every possible transaction type I could think of. The problem was, each thing required special support code and data fields whether it was used or not, and only covered one special case at a time. It would have been an explosion of special cases. The solution was script, which generalizes the problem so transacting parties can describe their transaction as a predicate that the node network evaluates. The nodes only need to understand the transaction to the extent of evaluating whether the sender's conditions are met.",
"sig": "c87b1bd7f40a12cee4ef230716067ae98e5317d179980c469c21705faf5421ae8a097e99ed73edc6185c1680a644526a20a9eded225334a8c6979101d9124c19"
}
