|
|
|
|
|
by wyager
4129 days ago
|
|
> Bitcoin code, protocol and marshaling formats are a mess. Which is why people are working on e.g. Libconsensus. There are dozens of functional Bitcoin clients based on entirely different codebases, which indicates that it's entirely possible to start from scratch. >payments with a single token. While the Bitcoin transaction format is a bit inflexible, you're wrong about the assumptions it makes. Even from the beginning, there has been in-protocol support for more advanced transaction types, like escrow transactions. You can even use a lot of these transaction types right now! There are still some transaction script opcodes that haven't been fully enabled yet, but that's just a matter of tweaking the consensus rules once we're sure that the opcode was implemented correctly and won't have any bad side effects. This has happened several times already with no major problems. |
|
Writing a BIP to add a new opcode for every possible transaction type is not the answer. And still I don't see how multisig or P2SH can use something else than BTC tokens (colored coins require external asset registries).