Treat wallet as a generic keystore #6

1. 
   davout commented at 12:29 pm on December 20, 2010: none

   Actually it would be even nicer if we could treat our wallet.dat file as a generic keystore, importing and exporting keys. This would allow merging and splitting of wallets as well, besides signatures as suggested above.

   See : http://www.bitcoin.org/smf/index.php?topic=2373.0

2. 
   cdecker commented at 1:34 pm on December 20, 2010: contributor

   We already have generic keystores on Linux machines, why not adapt Bitcoin to use them and provide a really simple one for systems that do not provide their own?
3. 
   gavinandresen commented at 1:45 pm on December 20, 2010: contributor

   See my python bitcointools for code that can read and write the key/value pairs in wallet.dat (fixwallet.py reads the wallet and writes out a new wallet, leaving out any keys that seem to be mis-formatted).

   Merging wallets is hard because you have to teach bitcoin to re-scan the block chain for transactions to or from keys you just imported.

4. 
   cdecker commented at 1:49 pm on December 20, 2010: contributor

   Just delete all the block data and redownload the block chain.
5. 
   davout commented at 5:32 pm on December 20, 2010: none

   Deletion is not necessary, doesn’t it already happen anyway when wallet is replaced ?
6. 
   mndrix commented at 6:00 pm on February 9, 2011: contributor

   Easy import and export of keys would make it easier for trusted vendors to sell Bitcoin stored-value cards (USB sticks, mini CDs, etc) with a private key on them. The buyer then just imports the private key from the card.

   Easy import/export also addresses parts of issue #2

7. 
   gasteve commented at 4:32 am on February 28, 2011: none

   Easy import/export is an important feature for the day when transactions are no longer free on the network. People won’t want to pay transaction fees when consolidating or moving btc value between different wallets they own. Also, easy import/export should be treated like moving (rather than copying) to prevent keys from ending up in multiple, concurrently active wallets (backup should be used for ensuring you don’t lose keys).

   I think I’ll create a separate issue for this (since it is straying from this topic).

   As for treating the wallet as a generic key store or using existing key store solutions, I think it’s better to stay away from that in the short term. That could pose quite a few technical and integration challenges, and if not done very carefully, could pose a security risk (you would be putting bitcoin users at the mercy of third party key storage solutions that may or may not be very well implemented).

8. 
   alexwaters commented at 6:46 am on September 6, 2011: contributor

   #220 wallet import and export should resolve this issue, please contribute to that thread.
9. alexwaters closed this on Sep 6, 2011

   ---

10. laanwj referenced this in commit b9e80983a5 on Sep 18, 2011
11. sipa referenced this in commit 16fbc0f281 on Jun 2, 2013
12. nelisky referenced this in commit 8b3530d21a on Aug 8, 2013
13. kac- referenced this in commit 5d63ba21c6 on Mar 25, 2014
14. justmoon referenced this in commit e40837da51 on Apr 7, 2014
15. kac- referenced this in commit 35f0a4e2e9 on Oct 8, 2014
16. braydonf referenced this in commit 508bedaae0 on May 10, 2016
17. AkioNak referenced this in commit bf226befaf on Jul 24, 2017
18. laanwj referenced this in commit b13a68e129 on Aug 2, 2017
19. fametrano referenced this in commit ecbd242045 on Aug 4, 2017
20. JeremyRubin referenced this in commit 7f378349b2 on Aug 9, 2017
21. MarcoFalke referenced this in commit 2151c25dca on Sep 29, 2017
22. Anfauglith referenced this in commit 222b328a4b on Oct 26, 2017
23. classesjack referenced this in commit a1f4b4cbcf on Jan 2, 2018
24. HashUnlimited referenced this in commit fb8585691c on Mar 9, 2018
25. KrzysiekJ referenced this in commit 5e670fdb0c on Mar 28, 2018
26. effectsToCause referenced this in commit c3686e6d08 on Jun 22, 2018
27. MarcoFalke referenced this in commit 4d550ffab6 on Jul 30, 2018
28. Empact referenced this in commit 2a3aa4350e on Aug 1, 2018
29. hashtobewild referenced this in commit f7d07449a3 on Aug 26, 2018
30. dooglus referenced this in commit f1f88bed2e on Oct 20, 2018
31. cryptapus referenced this in commit 545fadbc57 on Jan 12, 2019
32. DigiGreenCoin referenced this in commit 15e2eddfd7 on Oct 29, 2019
33. sipsorcery referenced this in commit e9c85bb139 on Nov 7, 2019
34. MarcoFalke referenced this in commit cf43f3f0a8 on Dec 5, 2019
35. Warchant referenced this in commit 7958da26e8 on Dec 31, 2019
36. laanwj referenced this in commit 66480821b3 on Feb 10, 2020
37. laanwj referenced this in commit 31bdd86631 on Jul 15, 2020
38. KolbyML referenced this in commit 574a08d376 on Sep 4, 2020
39. laanwj referenced this in commit 924a4ff7eb on Oct 29, 2020
40. jonasschnelli referenced this in commit c33662a0ea on Dec 2, 2020
41. laanwj referenced this in commit e520e091db on Jan 6, 2021
42. MarcoFalke referenced this in commit 590e49ccf2 on Apr 4, 2021
43. MarcoFalke referenced this in commit bce09da122 on Apr 28, 2021
44. fanquake referenced this in commit fa00bb2c5c on Apr 29, 2021
45. MarcoFalke referenced this in commit eb9a1fe037 on May 7, 2021
46. laanwj referenced this in commit ee9befe8b4 on May 12, 2021
47. MarcoFalke referenced this in commit c857148636 on May 15, 2021
48. rajarshimaitra referenced this in commit f991d5cf2e on Aug 5, 2021
49. DrahtBot locked this on Sep 8, 2021

Contributors
davout cdecker gavinandresen mndrix gasteve alexwaters

Labels
Brainstorming