From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: Luke Dashjr <luke@dashjr•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Making OP_TRUE standard?
Date: Mon, 14 May 2018 21:22:26 -0400 [thread overview]
Message-ID: <pVpDgf56HrClum8YbXrgAgP3TUVGEEywi7aHPkNuRHSv0WweeISvFU8YBpfqsDc814KgwkMHGCSZVS-bh5609EvDUH-x4w9MvKz2ToK-J6s=@protonmail.com> (raw)
In-Reply-To: <201805100227.42217.luke@dashjr.org>
Good morning Luke,
> (Maybe it should be the first output
>
> instead of the last... Is there any legitimate reason one would have multiple
>
> such dummy outputs?)
None, but how about use of `SIGHASH_SINGLE` flag? If a dummy output is added as the first, would it not require adjustment of the inputs of the transaction?
In context you are discussing the transaction serialization, though, so perhaps `SIGHASH_SINGLE`, is unaffected?
Regards,
ZmnSCPxj
next prev parent reply other threads:[~2018-05-15 1:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 23:57 Rusty Russell
2018-05-09 0:24 ` Olaoluwa Osuntokun
2018-05-09 3:02 ` ZmnSCPxj
2018-05-10 2:08 ` Rusty Russell
2018-05-09 17:56 ` Johnson Lau
2018-05-09 19:27 ` Peter Todd
2018-05-09 20:19 ` Johnson Lau
2018-05-09 20:59 ` Peter Todd
2018-05-09 22:06 ` Olaoluwa Osuntokun
2018-05-10 2:06 ` Rusty Russell
2018-05-10 2:27 ` Luke Dashjr
2018-05-10 3:07 ` ZmnSCPxj
2018-05-15 1:22 ` ZmnSCPxj [this message]
2018-05-17 2:44 ` Rusty Russell
2018-05-17 10:28 ` ZmnSCPxj
2018-05-17 17:35 ` Christian Decker
2018-05-17 20:06 ` Jim Posen
2018-05-21 3:44 ` Rusty Russell
2018-05-21 3:56 ` Peter Todd
2018-05-30 2:47 ` Rusty Russell
2018-05-31 2:47 ` Rusty Russell
2018-05-21 14:20 ` Russell O'Connor
2018-05-10 9:33 ` Jorge Timón
2018-05-10 9:33 ` Jorge Timón
2018-05-10 9:43 ` Luke Dashjr
2018-05-11 2:44 ` ZmnSCPxj
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='pVpDgf56HrClum8YbXrgAgP3TUVGEEywi7aHPkNuRHSv0WweeISvFU8YBpfqsDc814KgwkMHGCSZVS-bh5609EvDUH-x4w9MvKz2ToK-J6s=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)org \
/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