Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V1HnJ-0000wp-45 for bitcoin-development@lists.sourceforge.net; Mon, 22 Jul 2013 15:13:01 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.175 as permitted sender) client-ip=209.85.217.175; envelope-from=melvincarvalho@gmail.com; helo=mail-lb0-f175.google.com; Received: from mail-lb0-f175.google.com ([209.85.217.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1V1HnF-0001ZE-Nz for bitcoin-development@lists.sourceforge.net; Mon, 22 Jul 2013 15:13:01 +0000 Received: by mail-lb0-f175.google.com with SMTP id r10so5364401lbi.20 for ; Mon, 22 Jul 2013 08:12:50 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.4.65 with SMTP id i1mr12822879lai.21.1374505970816; Mon, 22 Jul 2013 08:12:50 -0700 (PDT) Received: by 10.112.59.193 with HTTP; Mon, 22 Jul 2013 08:12:50 -0700 (PDT) In-Reply-To: <20130722144458.GA22993@vps7135.xlshosting.net> References: <20130722144458.GA22993@vps7135.xlshosting.net> Date: Mon, 22 Jul 2013 17:12:50 +0200 Message-ID: From: Melvin Carvalho To: Pieter Wuille Content-Type: multipart/alternative; boundary=089e0149338021dc4004e21b1c8f X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (melvincarvalho[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1V1HnF-0001ZE-Nz Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] [RFC] Standard for private keys with birth timestamp X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 15:13:01 -0000 --089e0149338021dc4004e21b1c8f Content-Type: text/plain; charset=ISO-8859-1 On 22 July 2013 16:44, Pieter Wuille wrote: > Hello, > > I should have brought up this suggestion before, as there seems to be > relevant other work. > > I'd like to propose encoding keys data (whatever type) with a birth > timestamp as: > * @ > > The reason for not incorporating this inside the key serialization (for > example BIP32), is because > birth timestamps are more generally a property of an address, rather than > the key it is derived from. > For one, it is useful for non-extended standard serialized private keys, > but for P2SH addresses, > the "private key" is really the actual scriptPubKey, but birth data is > equally useful for this. > > Reason for choosing the '@' character: it's not present in the base58, > hex, or base64 encodings that > are typically used for key/script data. > > One downside is that this means no checksum-protection for the timestamp, > but the advantage is > increased genericity. It's also longer than using a binary encoding, but > this is an optional > part anyway, and I think "human typing" is already fairly hard anyway. > Is there a BIP for this? @ is normally used in conjunction with things other than a time stamp ... You may want to look at RFC 4151 http://www.ietf.org/rfc/rfc4151.txt They had an idea on adding time stamps to identifiers. First impression is that the sacrifice in opacity does not seem to justify the utility. > > -- > Pieter > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --089e0149338021dc4004e21b1c8f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On 22 July 2013 16:44, Pieter Wuille <pieter.wuille@gmail.c= om> wrote:
Hello,

I should have brought up this suggestion before, as there seems to be relev= ant other work.

I'd like to propose encoding keys data (whatever type) with a birth tim= estamp as:
=A0* <serialized key>@<unix timestamp in decimal>

The reason for not incorporating this inside the key serialization (for exa= mple BIP32), is because
birth timestamps are more generally a property of an address, rather than t= he key it is derived from.
For one, it is useful for non-extended standard serialized private keys, bu= t for P2SH addresses,
the "private key" is really the actual scriptPubKey, but birth da= ta is equally useful for this.

Reason for choosing the '@' character: it's not present in the = base58, hex, or base64 encodings that
are typically used for key/script data.

One downside is that this means no checksum-protection for the timestamp, b= ut the advantage is
increased genericity. It's also longer than using a binary encoding, bu= t this is an optional
part anyway, and I think "human typing" is already fairly hard an= yway.

Is there a BIP for this?

<= /div>
@ is normally used in conjunction with things other than a time s= tamp ...

You may want to look at RFC 4151

http://www.ietf.org/rfc/rfc4151.txt

=
They had an idea on adding time stamps to identifiers.=A0
First impression is that the sacrifice in opacity does not seem = to justify the utility.
=A0

--
Pieter


---------------------------------------------------------------------------= ---
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gam= pad/clk?id=3D48808831&iu=3D/4140/ostg.clktrk
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--089e0149338021dc4004e21b1c8f--