From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Electrum 2.0 has been tagged
Date: Thu, 12 Mar 2015 19:51:14 +0100 [thread overview]
Message-ID: <mdsn73$qpn$1@ger.gmane.org> (raw)
In-Reply-To: <CAAt2M1_zVXnp_EjtZHiP9wSq+cERgibZ_C992zZHtv+Lpmgsfw@mail.gmail.com>
On 03/12/2015 07:27 PM, Natanael wrote:
>
> Den 12 mar 2015 17:48 skrev "Mike Hearn" <mike@plan99.net
> <mailto:mike@plan99.net>>:
>>>
>>> b) "Creation date" is just a short-term hack.
>>
>>
>> I agree, but we need things to be easy in the short term as well as
> the long term :)
>>
>> The long term solution is clearly to have the 12 word seed be an
> encryption key for a wallet backup with all associated metadata. We're
> heading in that direction one step at a time. Unfortunately it will take
> time for wallets to start working this way, and all the pieces to fall
> into place. Restoring from the block chain will be a semi regular
> operation for users until then.
>
> This have been mentioned a few times before, and what I think is
> necessary is to create a common file format that can be interpreted by a
> library which all wallets can use. I see it as similar as the work to
> create libconsensus for parsing the blockchain.
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?
Bitcoinj-based wallets could probably share the bitcoinj protobuf wallet
format (or whatever format we will be at the time of the "merge" – we
already have tons of requirements piling up!). This would mean bitcoinj
is the "consensus library equivalent" you were mentioning.
next prev parent reply other threads:[~2015-03-12 18:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 15:23 [Bitcoin-development] Electrum 2.0 has been tagged Thomas Voegtlin
2015-03-02 7:09 ` Andreas Schildbach
2015-03-02 15:37 ` Mike Hearn
2015-03-02 17:11 ` Jim
2015-03-11 14:58 ` Thomas Voegtlin
2015-03-11 15:31 ` Andreas Schildbach
2015-03-12 8:56 ` Thomas Voegtlin
2015-03-11 17:14 ` Mike Hearn
2015-03-11 19:04 ` Jim
2015-03-11 19:24 ` Ricardo Filipe
2015-03-11 19:46 ` Gregory Maxwell
2015-03-11 22:57 ` Aaron Voisine
2015-03-11 23:22 ` Mike Hearn
2015-03-11 23:50 ` devrandom
2015-03-11 23:54 ` Mike Hearn
2015-03-12 0:11 ` Gregory Maxwell
2015-03-12 2:41 ` devrandom
2015-03-12 4:09 ` Gregory Maxwell
2015-03-12 19:08 ` Bryan Bishop
2015-03-12 10:30 ` Andreas Schildbach
2015-03-12 10:28 ` Andreas Schildbach
2015-03-18 2:06 ` devrandom
2015-03-12 10:41 ` Andreas Schildbach
2015-03-12 3:43 ` slush
2015-03-12 16:47 ` Mike Hearn
2015-03-12 17:20 ` Gary Rowe
2015-03-12 17:42 ` Gary Rowe
2015-03-12 18:27 ` Natanael
2015-03-12 18:51 ` Andreas Schildbach [this message]
2015-03-12 19:14 ` Natanael
[not found] <1353069350.4360497.1426126034565.JavaMail.yahoo@mail.yahoo.com>
2015-03-12 2:16 ` Thy Shizzle
2015-03-12 3:59 ` Neill Miller
[not found] <372541993.4372759.1426123313134.JavaMail.yahoo@mail.yahoo.com>
2015-03-12 2:26 ` devrandom
2015-03-12 2:38 Thy Shizzle
2015-03-12 10:43 ` Andreas Schildbach
2015-03-12 4:21 Thy Shizzle
2015-03-12 11:51 ` Neill Miller
2015-03-12 12:59 ` Thy Shizzle
2015-03-12 16:39 ` devrandom
2015-03-12 5:12 Thy Shizzle
2015-03-12 5:25 ` Aaron Voisine
2015-03-12 5:58 Thy Shizzle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mdsn73$qpn$1@ger.gmane.org' \
--to=andreas@schildbach.de \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox