From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: Olaoluwa Osuntokun <laolu32@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Making OP_TRUE standard?
Date: Tue, 08 May 2018 23:02:37 -0400 [thread overview]
Message-ID: <YY-OE0cDxefaxLtsNo9HoEIVrpUpA_FR0-h1lVlc-w6iAKEQDq1UQLhRGBgrg23jzl0Tx4Fqap30q9cvw64aFBpV7AXLbzgWtF2gxX5rAaE=@protonmail.com> (raw)
In-Reply-To: <CAO3Pvs9e5_YR9A_nqxcHAO5KgSvoyNq9q3P5UKBHbfK+kfvkKA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
Good morning Olauluwa,
I believe P2WSH is larger due to the script hash commitment in the `scriptPubKey` as well as the actual script revelation in the `witnessScript`, whereas, a flat OP_TRUE in the `scriptPubKey` is much smaller and can be spent with an empty `scriptSig`. It seems this is the entirety of the reason to desire an isStandard OP_TRUE.
Regards,
ZmnSCPxj
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On May 9, 2018 8:24 AM, Olaoluwa Osuntokun via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> What are the downsides of just using p2wsh? This route can be rolled out immediately, while policy changes are pretty "fuzzy" and would require a near uniform rollout in order to ensure wide propagation of the commitment transactions.
>
> On Tue, May 8, 2018, 4:58 PM Rusty Russell via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>> Hi all,
>>
>> The largest problem we are having today with the lightning
>> protocol is trying to predict future fees. Eltoo solves this elegantly,
>> but meanwhile we would like to include a 546 satoshi OP_TRUE output in
>> commitment transactions so that we use minimal fees and then use CPFP
>> (which can't be done at the moment due to CSV delays on outputs).
>>
>> Unfortunately, we'd have to P2SH it at the moment as a raw 'OP_TRUE' is
>> non-standard. Are there any reasons not to suggest such a policy
>> change?
>>
>> Thanks!
>> Rusty.
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #2: Type: text/html, Size: 2914 bytes --]
next prev parent reply other threads:[~2018-05-09 3:02 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 [this message]
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
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='YY-OE0cDxefaxLtsNo9HoEIVrpUpA_FR0-h1lVlc-w6iAKEQDq1UQLhRGBgrg23jzl0Tx4Fqap30q9cvw64aFBpV7AXLbzgWtF2gxX5rAaE=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=laolu32@gmail$(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