From: vv01f <vv01f@riseup•net>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Export format for xpub
Date: Mon, 02 Feb 2015 15:47:44 +0100 [thread overview]
Message-ID: <54CF8E10.5040402@riseup.net> (raw)
In-Reply-To: <mao0u5$gbu$1@ger.gmane.org>
On 02.02.2015 15:17, Andreas Schildbach wrote:
>> Uff, I would expect YYYYMMDD there so it's human readable as well.
>
> Those strings are not meant to be read by humans. YYYYMMDD is more
> complicated than necessary, given that Bitcoin deals with seconds since
> epoch everywhere.
First that is a pitty .. as its simply a waste of storage.
but back to Pavol's point: IMHO no harm to anything, as Bitcoin never
has any valid timestamp below ~1230768000 (jan2009) and thus will always
have 10 digits.. you can easily identify 8 char long timestamp as the
proposed format.
And there never is anything wrong with having a transparent, human
readable option - especially when it saves 2 bytes in e.g. qr-codes.
next prev parent reply other threads:[~2015-02-02 14:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 8:56 Levin Keller
2015-02-02 11:33 ` Mike Hearn
2015-02-02 12:38 ` Andreas Schildbach
2015-02-02 12:59 ` Pavol Rusnak
2015-02-02 14:17 ` Andreas Schildbach
2015-02-02 14:47 ` vv01f [this message]
2015-02-03 0:02 ` Andreas Schildbach
2015-02-02 14:56 ` Pavol Rusnak
2015-02-03 0:05 ` Andreas Schildbach
2015-02-03 0:22 ` Pavol Rusnak
2015-02-03 9:33 ` Levin Keller
2015-02-03 10:10 ` Pavol Rusnak
2015-02-03 10:37 ` Andreas Schildbach
2015-02-03 10:44 ` Pavol Rusnak
2015-02-03 10:35 ` Andreas Schildbach
2015-02-03 10:34 ` Andreas Schildbach
2015-02-02 12:57 ` Pavol Rusnak
2015-02-02 11:38 ` Wladimir
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=54CF8E10.5040402@riseup.net \
--to=vv01f@riseup$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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