-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trezor cannot send to bech32 addresses #2976
Comments
Yes, that is expected. Electrum "segwit" seeds have native segwit outputs with BIP173 ("bech32") addresses. Lines 12 to 24 in 91ed74a
|
Oh, I did not read BIP173. It seems that it has not been accepted yet. Thanks. |
I can't send coins to the bc1-address. Tested on 088b1e6 and 91ed74a + your patch. By the way, is it good idea to use BIP173 by default while it is just a draft? |
It's likely not implemented in Trezor (or at least the Trezor plugin). I think this warrants a separate issue. |
I'll check it with your b1167e9 patch. |
It seems they are going to accept it, bech32 support was added to Bitcoin Core. |
I added this blind fix: 0df24d9 |
still failing after firmware update |
FYI, I finished my implementation of bech32 in TREZOR firmware trezor/trezor-mcu#236. It would need some changes to use a wallet with bech32 addresses with Trezor, but I think we don't want to go that way soon. Now I need a blockexplorer that shows the address. |
Blockchain.info shows bc-addresses if you click 'Show scripts & coinbase'. |
Thank you. It works (tested on Trezor 1.6). |
File -> New/Restore -> Standard wallet -> Create a new seed -> Segwit
I'm getting bc1-addresses, is it okay? I thought I should get 3-addresses.
The text was updated successfully, but these errors were encountered: