Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id AAABCB10 for ; Thu, 7 Sep 2017 18:03:08 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail148101.authsmtp.com (outmail148101.authsmtp.com [62.13.148.101]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2695A8A for ; Thu, 7 Sep 2017 18:03:07 +0000 (UTC) Received: from mail-c247.authsmtp.com (mail-c247.authsmtp.com [62.13.128.247]) by punt22.authsmtp.com (8.14.2/8.14.2/) with ESMTP id v87I36VF040236; Thu, 7 Sep 2017 19:03:06 +0100 (BST) Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com [52.5.185.120]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id v87I33V1021035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Sep 2017 19:03:04 +0100 (BST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by petertodd.org (Postfix) with ESMTPSA id 194344012D; Thu, 7 Sep 2017 18:03:03 +0000 (UTC) Received: by localhost (Postfix, from userid 1000) id DB4C9202B4; Thu, 7 Sep 2017 14:02:56 -0400 (EDT) Date: Thu, 7 Sep 2017 14:02:56 -0400 From: Peter Todd To: Pavol Rusnak , Bitcoin Protocol Discussion Message-ID: <20170907180256.GB13727@fedora-23-dvm> References: <0d405f5d-c0a4-bad7-b6c3-08ba4424bf17@satoshilabs.com> <200b706a-f6ac-479a-2dce-fd66fe943949@satoshilabs.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) X-Server-Quench: cbdab9a1-93f6-11e7-b1e8-0015176ca198 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdgUUC1AEAgsB AmEbWl1eUF57WWc7 bghPaBtcak9QXgdq T0pMXVMcUg1veB8C YB8eUBhydAAIcHh4 ZwgxDCQKDk0rdFt0 QRhSCGwHMGB9OmFK WF1YdwJRcQRMLU5E Y1gxNiYHcQ5VPz4z GA41ejw8IwAXED5S WgYWJFZACWsbAjM6 Sx0OVS4iB0wMQyQh JgAnLVhUEkELN0wu eVUmQxoyEidXUVc8 V15EBCtUO0Jp X-Authentic-SMTP: 61633532353630.1038:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 52.5.185.120/25 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Status: No, score=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Proposal: Extended serialization format for BIP-32 wallets X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 18:03:08 -0000 --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--