From: Mike Hearn <mike@plan99•net>
To: slush <slush@centrum•cz>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Electrum 2.0 has been tagged
Date: Thu, 12 Mar 2015 09:47:56 -0700 [thread overview]
Message-ID: <CANEZrP2AhCfks7Q+16PHGB0ZEeWwbdbbQM_xj3ebrkgDBgbosg@mail.gmail.com> (raw)
In-Reply-To: <CAJna-HhHkmOTqNW2R6=Cih+tM_Eeu5o1LBxA4ZNzp-6vm1p6fg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
>
> 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.
WRT version number I have no real strong feelings about this. But
representing short pieces of binary data as words is so convenient, it
seems likely that it could be similar to addresses: people find other uses
for this mechanism beyond just storing a raw private key. Bitcoin addresses
have versions and that's proven to be useful several times, even though in
theory an address is "just" a hash of a pubkey.
[-- Attachment #2: Type: text/html, Size: 1323 bytes --]
next prev parent reply other threads:[~2015-03-12 16:48 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 15:23 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 [this message]
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
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=CANEZrP2AhCfks7Q+16PHGB0ZEeWwbdbbQM_xj3ebrkgDBgbosg@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=slush@centrum$(echo .)cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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