📅 Original date posted:2016-05-14
📝 Original message:Am 14.05.2016 um 10:16 schrieb Jonas Schnelli via bitcoin-dev:
>
> Importing a bip32 wallet (bip44 or not) is still an expert job IMO.
> Also importing can lead to bad security practice (especially without a
> sweep).
One important use case is importing xpubs for watch-only accounts. This
is necessary for hardware wallets and there are other valid use cases
for this.
>
> Users will send around xpriv or import an seed over a compromised
> computer to a cold storage, etc.
>
> I don't think users want to import private keys.
> They probably want to import the transaction history and send all funds
> covered by that seed to a new wallet.
>
Yes, in general it is not a good idea to import private keys and many
wallets don't even have an option to give out the xprv (except
indirectly via the backup mechanism). But even when sweeping a
bip-44+segwit wallet you need to know where the segwit addresses are.
Jochen
Jochen Hoenicke [ARCHIVE] /
npub1tu…dca6f
2023-06-07 17:50:42
in reply to nevent1q…h9sj
Author Public Key
npub1tue9u2scw5pe77vn4fz0464zz0387gm0zwy2zjhqg2yap36zhj2s4dca6fSeen on
wss://relay.nostr.bandPublished at
2023-06-07 17:50:42Event JSON
{
"id": "c382674df7a1b59b109071f9b6d4557025a0dd01bd4aa08af3681e2fac8b1ac9",
"pubkey": "5f325e2a1875039f7993aa44faeaa213e27f236f1388a14ae04289d0c742bc95",
"created_at": 1686160242,
"kind": 1,
"tags": [
[
"e",
"dde2d1a2608d8708981e63f6426a506001e25543a593f3cfcddbdaafeb9e6b7d",
"",
"root"
],
[
"e",
"1398c89aa46d67dd3773b90808ccf45514ffeabb96b805d037e8fa2d409be377",
"",
"reply"
],
[
"p",
"9a463e0fab8963b013698c15a0f2449d19c97f3b88458e5874095b5006df9a0c"
]
],
"content": "📅 Original date posted:2016-05-14\n📝 Original message:Am 14.05.2016 um 10:16 schrieb Jonas Schnelli via bitcoin-dev:\n\u003e \n\u003e Importing a bip32 wallet (bip44 or not) is still an expert job IMO.\n\u003e Also importing can lead to bad security practice (especially without a\n\u003e sweep).\n\nOne important use case is importing xpubs for watch-only accounts. This\nis necessary for hardware wallets and there are other valid use cases\nfor this.\n\n\u003e \n\u003e Users will send around xpriv or import an seed over a compromised\n\u003e computer to a cold storage, etc.\n\u003e\n\u003e I don't think users want to import private keys.\n\u003e They probably want to import the transaction history and send all funds\n\u003e covered by that seed to a new wallet.\n\u003e\n\nYes, in general it is not a good idea to import private keys and many\nwallets don't even have an option to give out the xprv (except\nindirectly via the backup mechanism). But even when sweeping a\nbip-44+segwit wallet you need to know where the segwit addresses are.\n\n Jochen",
"sig": "4dbfe56d6f179db65dcea3de2374108037278b899e200b9bcb4581364456089ed8006614358eec45ca0a5037ce61419906f40c949dbc6bd53a456632921c03ea"
}