Date: Thu, 7 Sep 2017 14:02:56 -0400
From: Peter Todd <pete@petertodd.org>
To: Pavol Rusnak <stick@satoshilabs.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20170907180256.GB13727@fedora-23-dvm>
References: <0d405f5d-c0a4-bad7-b6c3-08ba4424bf17@satoshilabs.com>
	<CA+_kfXLvTKwkuYmtt94OPUEPPwsEzhRoryy7srKMbLxYDxnmFA@mail.gmail.com>
	<200b706a-f6ac-479a-2dce-fd66fe943949@satoshilabs.com>
	<CA+_kfXL7bkV+PqR7GdQ9GdDz9AnEBoRXFCgYyJdMJQ8zuCKOEA@mail.gmail.com>
	<7bf726e1-f4e2-8d68-f934-671a0f2b9033@satoshilabs.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="i0/AhcQY5QxfSsSZ"
Content-Disposition: inline
In-Reply-To: <7bf726e1-f4e2-8d68-f934-671a0f2b9033@satoshilabs.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: Re: [bitcoin-dev] Proposal: Extended serialization format for
 BIP-32 wallets
Precedence: list


--i0/AhcQY5QxfSsSZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 07, 2017 at 06:37:19PM +0200, Pavol Rusnak via bitcoin-dev wrot=
e:
> On 07/09/17 18:30, Kabuto Samourai wrote:
> > Why not make this block height, rather than a timestamp?
>=20
> Blockheight depends on the chain. XPUB is not tied to particular
> chain/coin.
>=20
> Also there are already cryptocurrencies that do not use blockchain, but
> directed acyclic graph (DAG) for storing transactions. So it would not
> be obvious what number to use as a blockheight.
>=20
> OTOH all blockchains contain timestamps in their blocks, so we can use th=
at.

More to the point, even for the blockchains that don't contain timestamps in
their blocks, their blocks do exist in our spacetime continum and thus are
created at a specific point in time. :)

If someone does however come up with an example of a blockchain that does n=
ot
occupy our spacetime continum, I'd love to hear about it!

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--i0/AhcQY5QxfSsSZ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJZsYnRAAoJECSBQD2l8JH73JcIAIBlCh2aH4QE/JtpfaObO3Or
AqAMEnjSuOYmNed5gkyvHqPOI9vklpSgOXsqoLqHaSOD7MRY8vOcxnrQq6UrTQ01
WtY5YOqC87KQf62HPwkbEKNoNFkHwAR8acOcyhV5hbbX4vRqUkFzdAf0PoV0zYL0
9Ch4SO19IPYSAS6p4BP7MxAQ9s/1rUGbl5RpU5CTZRt6A4Jh2rpTbfiINieA5xIC
yZuAWrHx8fn9SRAjmw9JQIVBk0CUA7nBRTAEEVugM1Xudzu28RPxuWL7dBBzu3fe
j86e0UG8uEKh9hU4EvuEH3QB54Ea8cVOF7QwW2Ayhjqqu+uAP8Qz3iXUBkXSLcA=
=wPaj
-----END PGP SIGNATURE-----

--i0/AhcQY5QxfSsSZ--