📅 Original date posted:2017-09-06
📝 Original message:On 08/30/2017 12:24 AM, shiva sitamraju via bitcoin-dev wrote:
> What would happen if you recover a wallet using seed words ?
> 1. Since there is no difference in seed words between segwit/non
> segwit, the wallet would discover both m/44' and m/49' accounts
> 2. Note that we cannot ask the user to choose an account he wants to
> operate on (Segwit/Non segwit). This is like asking him the HD
> derivation path and a really bad UI
> 3. The wallet now has to constantly monitor both m/44' and m/49'
> accounts for transactions
small nit with 3.
It seems to me that the wallet would perform initial discovery on m/44
and m/49, and then would find transactions at one or the other, so it
can then record the type somewhere and from then on need only monitor
one branch.
Still, I agree it is ugly, makes initial discovery up to 2x slower, etc.
> *- XPUB Derivation*
> This is something not addressed in the BIP yet.
>
> 1. Right now you can get an xpub balance/transaction history. With m/49'
> there is no way to know whether an xpub is from m/44' or m/49'
>
> 2. This breaks lots of things. Wallets like electrum/armory/mycelium
> <https://blog.trezor.io/using-mycelium-to-watch-your-trezor-accounts-a836dce0b954>support
> importing xpub as a watch only wallet. Also services like
> blockonomics/blockchain.info <http://blockchain.info>; use xpub for
> displaying balance/generating merchant addresses
>
> Looking forward to hearing your thoughts
speaking as author of tools hd-wallet-addrs and hd-wallet-derive, I
agree this is problematic.
would be great if xpub/xprv could somehow encode their absolute path in
wallet for tools to read. Users cannot be expected to know.
Dan Libby [ARCHIVE] /
npub1hm…jk43d
2023-06-07 18:05:17
in reply to nevent1q…8m44
Author Public Key
npub1hm38d5dwxdq5zxlnv2qdfk3flecptqwl7g7u62ja0tr92d0hmrusejk43dPublished at
2023-06-07 18:05:17Event JSON
{
"id": "5936aa4a6fd0f0be77db6ad0477d77bd79d216bbf1b63967313735b9fd5296b2",
"pubkey": "bee276d1ae3341411bf36280d4da29fe701581dff23dcd2a5d7ac65535f7d8f9",
"created_at": 1686161117,
"kind": 1,
"tags": [
[
"e",
"46b44a34d77fcd68c66c473be695da22e57d2f60e66adebec21f1b5ec82f088c",
"",
"root"
],
[
"e",
"45ba41987dd5e2bdea5a074f5f8b96690b0add0e6b572743d2d251e388cc09ce",
"",
"reply"
],
[
"p",
"73b22eae19475ecafd3ad7608b5964dd8c693ff3c22755e534ff815332ed7dde"
]
],
"content": "📅 Original date posted:2017-09-06\n📝 Original message:On 08/30/2017 12:24 AM, shiva sitamraju via bitcoin-dev wrote:\n\n\u003e What would happen if you recover a wallet using seed words ?\n\u003e 1. Since there is no difference in seed words between segwit/non\n\u003e segwit, the wallet would discover both m/44' and m/49' accounts\n\u003e 2. Note that we cannot ask the user to choose an account he wants to\n\u003e operate on (Segwit/Non segwit). This is like asking him the HD\n\u003e derivation path and a really bad UI\n\u003e 3. The wallet now has to constantly monitor both m/44' and m/49'\n\u003e accounts for transactions\n\nsmall nit with 3.\n\nIt seems to me that the wallet would perform initial discovery on m/44\nand m/49, and then would find transactions at one or the other, so it\ncan then record the type somewhere and from then on need only monitor\none branch.\n\nStill, I agree it is ugly, makes initial discovery up to 2x slower, etc.\n\n\u003e *- XPUB Derivation*\n\u003e This is something not addressed in the BIP yet.\n\u003e \n\u003e 1. Right now you can get an xpub balance/transaction history. With m/49'\n\u003e there is no way to know whether an xpub is from m/44' or m/49'\n\u003e \n\u003e 2. This breaks lots of things. Wallets like electrum/armory/mycelium\n\u003e \u003chttps://blog.trezor.io/using-mycelium-to-watch-your-trezor-accounts-a836dce0b954\u003esupport\n\u003e importing xpub as a watch only wallet. Also services like\n\u003e blockonomics/blockchain.info \u003chttp://blockchain.info\u003e use xpub for\n\u003e displaying balance/generating merchant addresses\n\u003e \n\u003e Looking forward to hearing your thoughts\n\nspeaking as author of tools hd-wallet-addrs and hd-wallet-derive, I\nagree this is problematic.\n\nwould be great if xpub/xprv could somehow encode their absolute path in\nwallet for tools to read. Users cannot be expected to know.",
"sig": "4a080b5e16db77a2db796a447d8ea1733af65c5b211c115281b935f85759a1be96fcd2ae3ead5ffdc8ce8e74cd272f4d753d60300d5c164de5fb4d9084e7c194"
}