📅 Original date posted:2015-03-12
📝 Original message:Den 12 mar 2015 19:52 skrev "Andreas Schildbach" <andreas at schildbach.de>:
>
> I'm afraid this will never fly. Wallets are just too different and
> that's a good thing! For example, by design choice Bitcoin Wallet and
> bitcoinj doesn't support multiple accounts. How would it ever import
> wallets from MultiBit or Mycelium?
I think I covered that with the "importing wallet says what sections it
supports" part. Then you'd only ask for the library to give you the
addresses from the first branch in the main HD wallet. The user would be
told that you by design can't manage the other parts. The user would be
alerted and get the recommendation to send the funds over manually if they
want to switch their wallet. The user might however just want to export
that one single branch if he's a "power user", so he would proceed to use
it that way.
At export, I recommend the wallet will tell the user what extensions and
standards are in use (and which are necessary to recover how much of their
funds in the target wallet). The user would be asked to confirm that the
target wallet client supports these. The user should be given the option to
hand the list of supported functionality in the target wallet (like a list
of BIP numbers?), and tell the wallet to move the funds around so that the
target wallet can successfully import everything and recover all funds.
Actually, thinking about it I think what we really need first is a standard
synchronization / transition protocol. Right now we don't have more than
the address label syncing plugin for Electrum. We need something for
wallets to synchronize state, with the option for having one wallet tell
the other how to send over all funds (for when they use completely
different standards for managing funds). As the most simple option, the
target wallet would provide a list of addresses to the sending wallet when
you switch (this would satisfy Bryan's request).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150312/75ba39b6/attachment.html>;
Natanael [ARCHIVE] /
npub179…lpmjt
2023-06-07 15:31:33
in reply to nevent1q…sphw
Author Public Key
npub1798ncudyucap9jzzujjsgufx8tdykm8auzfledjcs6f6wf4ekqvq8lpmjtPublished at
2023-06-07 15:31:33Event JSON
{
"id": "9e6a5a7358bdd0cc4850c10316a4b5dc6ff126ce6c28cf716e8e0f7b7e3f3c79",
"pubkey": "f14f3c71a4e63a12c842e4a50471263ada4b6cfde093fcb6588693a726b9b018",
"created_at": 1686151893,
"kind": 1,
"tags": [
[
"e",
"bf192ab1459041905386f8a0c7782f07de04af2932326a4e49fe0d6ce14ed93c",
"",
"root"
],
[
"e",
"99b1d7b2caf1e30885f35611aae59e54f9583c3e5bfc7b9a9a60151b0b54e889",
"",
"reply"
],
[
"p",
"3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc"
]
],
"content": "📅 Original date posted:2015-03-12\n📝 Original message:Den 12 mar 2015 19:52 skrev \"Andreas Schildbach\" \u003candreas at schildbach.de\u003e:\n\u003e\n\u003e I'm afraid this will never fly. Wallets are just too different and\n\u003e that's a good thing! For example, by design choice Bitcoin Wallet and\n\u003e bitcoinj doesn't support multiple accounts. How would it ever import\n\u003e wallets from MultiBit or Mycelium?\n\nI think I covered that with the \"importing wallet says what sections it\nsupports\" part. Then you'd only ask for the library to give you the\naddresses from the first branch in the main HD wallet. The user would be\ntold that you by design can't manage the other parts. The user would be\nalerted and get the recommendation to send the funds over manually if they\nwant to switch their wallet. The user might however just want to export\nthat one single branch if he's a \"power user\", so he would proceed to use\nit that way.\n\nAt export, I recommend the wallet will tell the user what extensions and\nstandards are in use (and which are necessary to recover how much of their\nfunds in the target wallet). The user would be asked to confirm that the\ntarget wallet client supports these. The user should be given the option to\nhand the list of supported functionality in the target wallet (like a list\nof BIP numbers?), and tell the wallet to move the funds around so that the\ntarget wallet can successfully import everything and recover all funds.\n\nActually, thinking about it I think what we really need first is a standard\nsynchronization / transition protocol. Right now we don't have more than\nthe address label syncing plugin for Electrum. We need something for\nwallets to synchronize state, with the option for having one wallet tell\nthe other how to send over all funds (for when they use completely\ndifferent standards for managing funds). As the most simple option, the\ntarget wallet would provide a list of addresses to the sending wallet when\nyou switch (this would satisfy Bryan's request).\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150312/75ba39b6/attachment.html\u003e",
"sig": "abd82a70d008d681ecd75467a5bd49d4a3ae942a1e8f4ad2a286a4c6e99ccabba4e289d3e382182f0e0308e2a650239347e2fea2d42b9623c678ad3e3ed1c2e9"
}