This changes the transactions such that some transactions will have a variable size payload after the locktime field. It also splits the uint32 version field into two uint16 fields, which allows creation of a type field for identifying which type of payload goes with the transaction.
We need to make sure that Trezor can support reading these, as well as creating DIP 3 special transactions for Masternodes. Without this support, our masternode owners will not be able to use Trezor for their collateral moving forward.
prusnak
commented
6 years ago
The next release of Dash will introduce special transactions as presented in DIP 2 : https://github.com/dashpay/dips/blob/master/dip-0002.md.
This changes the transactions such that some transactions will have a variable size payload after the locktime field. It also splits the uint32 version field into two uint16 fields, which allows creation of a type field for identifying which type of payload goes with the transaction.
We need to make sure that Trezor can support reading these, as well as creating DIP 3 special transactions for Masternodes. Without this support, our masternode owners will not be able to use Trezor for their collateral moving forward.