2 tweaked BIP 47 path
source | link

Technical testing discussions with functional experimental code and concerning this matter are posted here. NoodleDoodle is definitely pushing the state of the art of Monero for BIP 39 support with tight Trezor integration.

However, the current issue is the Trezor V0313 binary implementation of trezorctl on a Mac can't create Electrum seed words from BIP 39 seed words when there is a rubber-hose password (plausible deniability exists), see Experimental trezor firmware testing for a recent posting concerning this matter.

The 4th posting provides working examples as to how BIP 32/39/44 technology can be applied to translate between BIP 39 seed words and Electrum words with a "rubber-hose" password (e.g., "1234"). The test vector examples, starts with a brain wallet, uses a combination of libbitcoin (bx) code and Monero code. Bitcoin Explorer (bx) commands faithfully reproduces BIP 44 keys and addresses from BIP 39 seeds that Trezor Web Application, Jaxx, including numerous altcoins.

NoodleDoodle desires not to apply BIP 44 paths. However, I can't yet independently reproduce NoodleDoodle's m/1'/2'/3'/4'/n' path results for (spend key and Monero stealth address) he claimed the V0313 trezorctl implements - when I apply bx, and a homegrown version of ./xmr built upon Monero foundations that matches results from Cryptonote Address Test.

An Exodus developer is leaning towards the application of BIP 47 instead of BIP 44. I'll provide a posting for a potential BIP 47 path ( e.g., m/47'/128’/(identity' or account’n’)/n'' where a hardened n = 0 through 2147483647 ) for four Monero test vectors, with and without a rubber-hose password for n' = 0 and 255. Wallet end users should only need to record one set of seed words to reconstitute their multi-currency wallets, not two or more. Harmonization between Electrum seed words and BIP 39 seed words is sorely needed.

Electrum seed words afford portability of Monero wallets across Monero hard forks, e.g., migration from Hydrogen Helix to a mandatory Ring CT Monero network capability. It is possible to make BIP 39 and Electrum seeds co-exist with BIP 39 as the basis for key synthesis. Like it or not, BIP 39 has a much stronger foothold in the HD multi-currency hardware wallet vendors (e.g., Trezor, Keepkey, Ledger), and HD multi-currency GUI cryptocurrency wallet providers than Electrum seed words (that are yes invertible, unlike BIP 39).

Technical testing discussions with functional experimental code and concerning this matter are posted here. NoodleDoodle is definitely pushing the state of the art of Monero for BIP 39 support with tight Trezor integration.

However, the current issue is the Trezor V0313 binary implementation of trezorctl on a Mac can't create Electrum seed words from BIP 39 seed words when there is a rubber-hose password (plausible deniability exists), see Experimental trezor firmware testing for a recent posting concerning this matter.

The 4th posting provides working examples as to how BIP 32/39/44 technology can be applied to translate between BIP 39 seed words and Electrum words with a "rubber-hose" password (e.g., "1234"). The test vector examples, starts with a brain wallet, uses a combination of libbitcoin (bx) code and Monero code. Bitcoin Explorer (bx) commands faithfully reproduces BIP 44 keys and addresses from BIP 39 seeds that Trezor Web Application, Jaxx, including numerous altcoins.

NoodleDoodle desires not to apply BIP 44 paths. However, I can't yet independently reproduce NoodleDoodle's m/1'/2'/3'/4'/n' path results for (spend key and Monero stealth address) he claimed the V0313 trezorctl implements - when I apply bx, and a homegrown version of ./xmr built upon Monero foundations that matches results from Cryptonote Address Test.

An Exodus developer is leaning towards the application of BIP 47 instead of BIP 44. I'll provide a posting for a potential BIP 47 path ( e.g., m/47'/128’/(identity' or account’)/n' where a hardened n = 0 through 2147483647 ) for four Monero test vectors, with and without a rubber-hose password for n' = 0 and 255. Wallet end users should only need to record one set of seed words to reconstitute their multi-currency wallets, not two or more. Harmonization between Electrum seed words and BIP 39 seed words is sorely needed.

Electrum seed words afford portability of Monero wallets across Monero hard forks, e.g., migration from Hydrogen Helix to a mandatory Ring CT Monero network capability. It is possible to make BIP 39 and Electrum seeds co-exist with BIP 39 as the basis for key synthesis. Like it or not, BIP 39 has a much stronger foothold in the HD multi-currency hardware wallet vendors (e.g., Trezor, Keepkey, Ledger), and HD multi-currency GUI cryptocurrency wallet providers than Electrum seed words (that are yes invertible, unlike BIP 39).

Technical testing discussions with functional experimental code and concerning this matter are posted here. NoodleDoodle is definitely pushing the state of the art of Monero for BIP 39 support with tight Trezor integration.

However, the current issue is the Trezor V0313 binary implementation of trezorctl on a Mac can't create Electrum seed words from BIP 39 seed words when there is a rubber-hose password (plausible deniability exists), see Experimental trezor firmware testing for a recent posting concerning this matter.

The 4th posting provides working examples as to how BIP 32/39/44 technology can be applied to translate between BIP 39 seed words and Electrum words with a "rubber-hose" password (e.g., "1234"). The test vector examples, starts with a brain wallet, uses a combination of libbitcoin (bx) code and Monero code. Bitcoin Explorer (bx) commands faithfully reproduces BIP 44 keys and addresses from BIP 39 seeds that Trezor Web Application, Jaxx, including numerous altcoins.

NoodleDoodle desires not to apply BIP 44 paths. However, I can't yet independently reproduce NoodleDoodle's m/1'/2'/3'/4'/n' path results for (spend key and Monero stealth address) he claimed the V0313 trezorctl implements - when I apply bx, and a homegrown version of ./xmr built upon Monero foundations that matches results from Cryptonote Address Test.

An Exodus developer is leaning towards the application of BIP 47 instead of BIP 44. I'll provide a posting for a potential BIP 47 path ( e.g., m/47'/128’/(identity' or n’)' where a hardened n = 0 through 2147483647 ) for four Monero test vectors, with and without a rubber-hose password for n' = 0 and 255. Wallet end users should only need to record one set of seed words to reconstitute their multi-currency wallets, not two or more. Harmonization between Electrum seed words and BIP 39 seed words is sorely needed.

Electrum seed words afford portability of Monero wallets across Monero hard forks, e.g., migration from Hydrogen Helix to a mandatory Ring CT Monero network capability. It is possible to make BIP 39 and Electrum seeds co-exist with BIP 39 as the basis for key synthesis. Like it or not, BIP 39 has a much stronger foothold in the HD multi-currency hardware wallet vendors (e.g., Trezor, Keepkey, Ledger), and HD multi-currency GUI cryptocurrency wallet providers than Electrum seed words (that are yes invertible, unlike BIP 39).

1
source | link

Technical testing discussions with functional experimental code and concerning this matter are posted here. NoodleDoodle is definitely pushing the state of the art of Monero for BIP 39 support with tight Trezor integration.

However, the current issue is the Trezor V0313 binary implementation of trezorctl on a Mac can't create Electrum seed words from BIP 39 seed words when there is a rubber-hose password (plausible deniability exists), see Experimental trezor firmware testing for a recent posting concerning this matter.

The 4th posting provides working examples as to how BIP 32/39/44 technology can be applied to translate between BIP 39 seed words and Electrum words with a "rubber-hose" password (e.g., "1234"). The test vector examples, starts with a brain wallet, uses a combination of libbitcoin (bx) code and Monero code. Bitcoin Explorer (bx) commands faithfully reproduces BIP 44 keys and addresses from BIP 39 seeds that Trezor Web Application, Jaxx, including numerous altcoins.

NoodleDoodle desires not to apply BIP 44 paths. However, I can't yet independently reproduce NoodleDoodle's m/1'/2'/3'/4'/n' path results for (spend key and Monero stealth address) he claimed the V0313 trezorctl implements - when I apply bx, and a homegrown version of ./xmr built upon Monero foundations that matches results from Cryptonote Address Test.

An Exodus developer is leaning towards the application of BIP 47 instead of BIP 44. I'll provide a posting for a potential BIP 47 path ( e.g., m/47'/128’/(identity' or account’)/n' where a hardened n = 0 through 2147483647 ) for four Monero test vectors, with and without a rubber-hose password for n' = 0 and 255. Wallet end users should only need to record one set of seed words to reconstitute their multi-currency wallets, not two or more. Harmonization between Electrum seed words and BIP 39 seed words is sorely needed.

Electrum seed words afford portability of Monero wallets across Monero hard forks, e.g., migration from Hydrogen Helix to a mandatory Ring CT Monero network capability. It is possible to make BIP 39 and Electrum seeds co-exist with BIP 39 as the basis for key synthesis. Like it or not, BIP 39 has a much stronger foothold in the HD multi-currency hardware wallet vendors (e.g., Trezor, Keepkey, Ledger), and HD multi-currency GUI cryptocurrency wallet providers than Electrum seed words (that are yes invertible, unlike BIP 39).