Requesting BIP assignment; Flexible Transactions.



Summary:

In an email exchange between Tom and Peter Todd, they discuss the serialization order of tokens in transactions. Tom explains that the order is necessary to prevent multiple interpretations of data, while Peter suggests a "Some/None" flag to indicate omitted optional data. Tom points out that this argument does not apply to required fields. He also asks for explicit examples of hypothetical upgrades and how they would take advantage of an extensible format. Peter suggests using a format that extends the merkle tree down into transaction inputs and outputs, citing his previous arguments regarding segwit and hardware wallet txin proof use-case.


Updated on: 2023-06-11T20:03:12.914082+00:00