{"type":"rich","version":"1.0","author_name":"npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7","author_url":"https://nostr.ae/npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-03-12\n📝 Original message:On 03/12/2015 07:27 PM, Natanael wrote:\n\u003e \n\u003e Den 12 mar 2015 17:48 skrev \"Mike Hearn\" \u003cmike at plan99.net\n\u003e \u003cmailto:mike at plan99.net\u003e\u003e:\n\u003e\u003e\u003e\n\u003e\u003e\u003e b) \"Creation date\" is just a short-term hack.\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e I agree, but we need things to be easy in the short term as well as\n\u003e the long term :) \n\u003e\u003e\n\u003e\u003e The long term solution is clearly to have the 12 word seed be an\n\u003e encryption key for a wallet backup with all associated metadata. We're\n\u003e heading in that direction one step at a time. Unfortunately it will take\n\u003e time for wallets to start working this way, and all the pieces to fall\n\u003e into place. Restoring from the block chain will be a semi regular\n\u003e operation for users until then.\n\u003e \n\u003e This have been mentioned a few times before, and what I think is\n\u003e necessary is to create a common file format that can be interpreted by a\n\u003e library which all wallets can use. I see it as similar as the work to\n\u003e create libconsensus for parsing the blockchain.\n\n\nI'm afraid this will never fly. Wallets are just too different and\nthat's a good thing! For example, by design choice Bitcoin Wallet and\nbitcoinj doesn't support multiple accounts. How would it ever import\nwallets from MultiBit or Mycelium?\n\nBitcoinj-based wallets could probably share the bitcoinj protobuf wallet\nformat (or whatever format we will be at the time of the \"merge\" – we\nalready have tons of requirements piling up!). This would mean bitcoinj\nis the \"consensus library equivalent\" you were mentioning."}