From: Johnson Lau <jl2012@xbt•hk>
To: Alex Nagy <optimiz3@hotmail•com>,
bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Cc: Gregory Maxwell <gmaxwell@gmail•com>
Subject: Re: [bitcoin-dev] P2WPKH Scripts, P2PKH Addresses, and Uncompressed Public Keys
Date: Tue, 29 Aug 2017 11:30:07 +0800 [thread overview]
Message-ID: <740F886F-6471-4418-A018-1A1B185744C3@xbt.hk> (raw)
In-Reply-To: <CY4PR1801MB181557B7331133954A3098DD809E0@CY4PR1801MB1815.namprd18.prod.outlook.com>
Yes it is allowed in TxOuts. And yes it is designed to save space. But the problem is Bob can’t assume Alice understands the new TxOuts format. If Bob really wants to save space this way, he should first ask for a new BIP173 address from Alice. Never try to convert a P2PKH address to a P2SH or BIP173 address without the consent of the recipient.
> On 29 Aug 2017, at 4:55 AM, Alex Nagy via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> 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 P2WPKH 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 Txes with many outputs.
>
next prev parent reply other threads:[~2017-08-29 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 15:29 Alex Nagy
[not found] ` <CAAS2fgT+HHg_xuuWuGrYcX0ALcBowmY-1Kt6-dzSBOwdcr08HQ@mail.gmail.com>
2017-08-28 17:06 ` [bitcoin-dev] Fwd: " Gregory Maxwell
2017-08-28 20:55 ` [bitcoin-dev] " Alex Nagy
2017-08-29 3:30 ` Johnson Lau [this message]
2017-09-04 13:51 ` Peter Todd
2017-08-28 21:33 ` Mark Friedenbach
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=740F886F-6471-4418-A018-1A1B185744C3@xbt.hk \
--to=jl2012@xbt$(echo .)hk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gmaxwell@gmail$(echo .)com \
--cc=optimiz3@hotmail$(echo .)com \
/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