Date: Mon, 4 Sep 2017 09:51:35 -0400
From: Peter Todd <pete@petertodd.org>
To: Alex Nagy <optimiz3@hotmail.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20170904135135.GE1276@fedora-23-dvm>
References: <CY4PR1801MB181583C344B0993205D4B6C8809E0@CY4PR1801MB1815.namprd18.prod.outlook.com>
	<CAAS2fgT+HHg_xuuWuGrYcX0ALcBowmY-1Kt6-dzSBOwdcr08HQ@mail.gmail.com>
	<CY4PR1801MB181557B7331133954A3098DD809E0@CY4PR1801MB1815.namprd18.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="UoPmpPX/dBe4BELn"
Content-Disposition: inline
In-Reply-To: <CY4PR1801MB181557B7331133954A3098DD809E0@CY4PR1801MB1815.namprd18.prod.outlook.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: Gregory Maxwell <gmaxwell@gmail.com>
Subject: Re: [bitcoin-dev] P2WPKH Scripts, P2PKH Addresses,
 and Uncompressed Public Keys
Precedence: list


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

On Mon, Aug 28, 2017 at 08:55:47PM +0000, Alex Nagy via bitcoin-dev wrote:
> Thanks Gregory - to be clear should Native P2WPKH scripts only appear in =
redeem scripts?  From reading the various BIPs it had seemed like Native P2=
WPKH and Native P2WSH were also valid and identifiable if they were encoded=
 in TxOuts.  The theoretical use case for this would be saving bytes in Txe=
s with many outputs.

It's not a theoretical use-case: the two OpenTimestamps calendar servers I =
run
- {alice,bob}.btc.calendar.opentimestamps.org - use native P2WPKH segwit
outputs to keep transaction size to the absolute minimum possible; previous=
ly
they used bare CHECKSIG <pubkey> output scripts for the same reason.

I enabled support for it the moment segwit activated, so I'm probably the f=
irst
ever production user of P2WPKH on mainnet, and quite possibly, the first pe=
rson
to create P2WPKH outputs on mainnet for any reason.

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

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

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

iQEcBAEBCAAGBQJZrVplAAoJECSBQD2l8JH7p+YH/0VLxtZMvS6oKOCvGr8T26ss
7WdDj2v4NXEcabcriXZAoG8wiNc5+5TyCVuAFi7aB9HRUTxAY20aUDe/2lM5jEfJ
y0V3Hqq9DnJE9LChDpbKgUSnI5XpTh6YS2IBlchxH2N8vcnJQ6JxDRitZHNUxr89
Gxejl8zKotI/Da2BedJbnIijKbGc7iXv6MtdtETiIt24Z5r2gSoffrCVIQ46XLdv
/WlmrNtxRccdo9DEtpZRoTTQUAm7DPjvJzMHmwCZ+9T+p6n89QlJQwjxOKygtoCr
FgwPdtLm+nmvWCsRlfPheHPf63339excx8oQBXJLidFebbsz/gnpcY1NkX86XcI=
=BVZW
-----END PGP SIGNATURE-----

--UoPmpPX/dBe4BELn--