[trezor] User can't spend out from approved tspend

[alexlyp]

User reported seeing this error when attempting to spend an outpoint from an approved tspend while in Trezor mode.

https://github.com/decred/decrediton/blob/caca418f8a76ddcda9d3612166010af52069d662/app/helpers/trezor.js#L43

They mentioned Exodus having a similar issue so probably related to not handling the tspends properly.

[matheusd]

I guess that the underlying trezor firmware impl won't be able to recognize tspends due to their outputs being special and therefore it won't be able to spend them.

In particular, tspend outputs are not exactly standard outputs (they have an OP_TGEN tag at the start) and so it's likely the trezor firmware won't recreate the tspend to be able to spend from it.

cc @JoeGruffins

[chappjc]

I imagine Exodus would have a similar issue. Here's what it would see from dcrdata's Insight API: https://dcrdata.decred.org/insight/api/tx/f57f2f35abcfc58cb8d45da6315982610203c1335ee0d68b36240f22c24a557a and for a random address it pays to, the utxo response with the tgen pkscript: https://dcrdata.decred.org/insight/api/addrs/DscgnGYEohMrdpuB3RBsdRPgohx1Gd8WP46/utxo But unless both Decrediton and Exodus have the keys to the address in question, it's not likely to be related

[JoeGruffins]

Yes sorry for the delay. Current firmware cannot spend treasury type outputs.

[JoeGruffins]

I will get this working with custom firmware and create an issue then pr with trezor to make this possible with Trezor T. It should be a simple change*.

[JoeGruffins]

Have started the process to get this in the firmware: https://github.com/trezor/trezor-firmware/issues/2096

edit: They don't seem to be interested in implementing changes atm. Probably a few years from now.