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: Thu, 10 May 2018 22:44:13 -0400 [thread overview]
Message-ID: <85BPI8zj4VsPA41MQtIP9zozZlAgX-QOJerUTvQmAdL4bjdP8Ooh1jkZnks1I_Ce2nqK-bUTOXeNR3wnmeKR4Ml-hRTp9Uo_l7jx7F_GaNs=@protonmail.com> (raw)
In-Reply-To: <201805100943.29654.luke@dashjr.org>
Good morning Luke and list,
>
> (Aside, in case it wasn't clear on my previous email, the template-script idea
>
> would not make it mandatory to spend in the same block, but that the UTXO
>
> would merely cease to be valid after that block. So the 0-value output does
>
> not take up a UTXO db entry when left unused.)
Thank you for clearing this up. It seems, I misunderstood. So my earlier rumination, about having two options for Lightning, is incorrect.
For Lightning, we just need to add this 0-value OP_TRUE output always to transactions that require both side signatures (commitment, HTLC-timeout, HTLC-success), and it will always serve as a "hook" for adding more fees if needed.
Regards,
ZmnSCPxj
prev parent reply other threads:[~2018-05-11 2:44 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
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 [this message]
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='85BPI8zj4VsPA41MQtIP9zozZlAgX-QOJerUTvQmAdL4bjdP8Ooh1jkZnks1I_Ce2nqK-bUTOXeNR3wnmeKR4Ml-hRTp9Uo_l7jx7F_GaNs=@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