From: Anthony Towns <aj@erisian.com.au>
To: アルム カールヨハン <karl@dglab.com>,
"Bitcoin Protocol Discussion"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Simple lock/unlock mechanism
Date: Thu, 1 Mar 2018 08:30:44 +1000 [thread overview]
Message-ID: <20180228223044.GA31415@erisian.com.au> (raw)
In-Reply-To: <CALJw2w7BQcMEHDa=mx6Gf_JQP603D_hpPq1YN5Em1cfsr4BDAw@mail.gmail.com>
On Wed, Feb 28, 2018 at 04:34:18AM +0000, アルム カールヨハン via bitcoin-dev wrote:
> 1. Graftroot probably breaks this (someone could just sign the
> time-locked output with a script that has no time-lock).
Making the graftroot key be a 2-of-2 muSig with an independent third party
that commits to only signing CLTV scripts could avoid this. Making it
3-of-3 or 5-of-5 could be even better if you can find multiple independent
services that will do it.
Cheers,
aj
next prev parent reply other threads:[~2018-02-28 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 3:47 [bitcoin-dev] Simple lock/unlock mechanism アルム カールヨハン
2018-02-28 4:34 ` アルム カールヨハン
2018-02-28 22:30 ` Anthony Towns [this message]
2018-02-28 23:36 ` Adam Back
2018-03-01 5:11 ` アルム カールヨハン
2018-03-05 14:53 ` アルム カールヨハン
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=20180228223044.GA31415@erisian.com.au \
--to=aj@erisian.com.au \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=karl@dglab.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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