Python-TREZOR: Do bech32/bc1 addresses work yet?

[Carlton Banks]

so I found this info about using bech32 addresses with python-trezor: https://github.com/trezor/python-trezor/blob/master/docs/EXAMPLES.rst#bitcoin-examples

Get first receiving address of first account for Bitcoin (Bech32 native SegWit P2WPKH):

trezorctl get_address --coin Bitcoin --script-type segwit --address "m/49'/0'/0'/0/0"

Get first receiving address of first account for Bitcoin (SegWit-in-P2SH):

trezorctl get_address --coin Bitcoin --script-type p2shsegwit --address "m/49'/0'/0'/0/0"

But in the tx signing section following, there's no mention of bech32. Anyone have any experience or knowledge of whether a Trezor will sign transactions spending outputs from bc1/bech32 addresses?

[1715142117]

1715142117

[1715142117]

1715142117

[1715142117]

1715142117

[1715142117]

1715142117

[1715142117]

1715142117

[Rath_]

As I replied you in TREZOR thread, you can already spend from bech32 address if you use Electrum. Since I am a member of TREZOR Telegram channel, I have decided to ask their team this question and it turns out that it is possible to spend from bc1 address using python-trezor but I'm still waiting for more detailed reply on how to do it. I have been waiting for about 2 hours, I will update my posts once I get instructions.

[Carlton Banks]

it turns out that it is possible to spend from bc1 address using python-trezor but I'm still waiting for more detailed reply on how to do it. I have been waiting for about 2 hours, I will update my posts once I get instructions.

Any updates then BitCryptex?

I was unsure whether I needed to use the BIP 49 or BIP 84 derivation path, or alternatively that some other argument needs to be supplied like when the address itself is queried (the python-trezor documentation seemed to imply that extra arguments can't be supplied to the trezorctl signing command).

[Rath_]

Any updates then BitCryptex?

I have just got a reply from stick. He has just altered the documentation.

You need to use BIP 84 derivation path which for native SegWit is: "m/84'/0'/0'/0/0"

[Carlton Banks]

Thanks BitCryptex (and stick of course)

I might put together a guide thread: Using TREZOR 1 on Qubes 4.0 if there's any interest. It's certainly taken a little configuring so that it works smoothly (Trezor Bridge service needs a little modifying to get it working, for example).



@mods: shouldn't there be a "Trezor" sub board in Alternative Clients? Or maybe just change the names so that it makes more sense, i.e. replace "Alternative Clients" with "BTC Wallets/Clients", then have separate subs for Bitcoin Core, Armory, Electrum, Trezor etc?