-
By default, the My Trezor apps generates BTC addresses at (BIP 49)
m/**49**'/0'/0'/0/_x_
It generates LTC addresses at:
m/**49**'/2'/0'/0/_x_
It generates BCH addresses at
m/**44**'/145'/0'/0…
-
I used my Coinomi mnemonic, selected BTC, and the default BIP-44 works fine. Clicking on the BIP-84 tab, it also works fine. I can see the receiving addresses for the wallet both legacy (44) and segwi…
aleqx updated
6 years ago
-
I have a ledger nano s. I have used the device once to receive bitcoin. The device is set up to use multi-signature SEGWIT (P2SH). The nano crashed after I used chrome extension to delete a coin (FIDO…
-
Hi,
Waiting for a possible new BIP dedicated standard. BIP32 tab could add an option for using the P2WKH address following BIP-173?
-
When setting up a hardware wallet (eg Trezor) in a new electrum wallet (I'm on v3.0.2), you get to a section called "Derivation" that explains absolutely nothing about what it is, what it means, or wh…
-
Trezor [just implemented](https://blog.trezor.io/expanded-cryptos-cryptocurrency-support-firmware-1-6-0-3825b5853470) bech32 support for receiving address. Is there a way to use it with Electrum?
-
Please use the following constants for BIP49 xpub/xprv prefixes as per http://docs.electrum.org/en/latest/seedphrase.html#list-of-reserved-numbers
Bitcoin:
0x049d7878 yprv
0x049d7cb2 ypub
Bi…
-
For example set slider to 100 sat/byte and sign transaction (1 input, 2 outputs):
> Size: 168 bytes
> Fee: 0.00014236 (84 sat/byte)
Large 16 sat/byte difference.
Expected result - never lower th…
-
... because of how we hangle bip44/bip49 paths in extract_input_bip32_path/check_change_bip32_path of [signing.c](https://github.com/trezor/trezor-mcu/blob/master/firmware/signing.c)
-
BIP49 uses P2WPKH Nested In P2SH
This is also currently provided as an option in the BIP32 tab.
But BIP141 specifies several other formats for segwit addresses.
https://github.com/bitcoin/bip…