From: アルム カールヨハン <karl@dglab.com>
To: Anthony Towns <aj@erisian.com.au>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Simple lock/unlock mechanism
Date: Mon, 5 Mar 2018 14:53:16 +0000 [thread overview]
Message-ID: <CALJw2w4Rcqw_G1eaMiiSkYyCLqRnx8wQvKpaHyPJKvOyRR3LWg@mail.gmail.com> (raw)
In-Reply-To: <CALJw2w5TqjYVAEUVMa9BVaqscoqXAs3xD65vP3kMfxmPTqD9Eg@mail.gmail.com>
On Thu, Mar 1, 2018 at 5:11 AM, アルム カールヨハン <karl@dglab.com> wrote:
> That kind of defeats the purpose. If you go through the trouble of
> doing that, you can just do multisig and skip the freezing part
> entirely. A robber would have to get you and the cosigner to sign in
> both cases, and the CLTV could be overridden with graftroot.
I think I'm confused on this. To use graftroot it has to be a pubkey,
not a p2sh thing.
-Kalle.
prev parent reply other threads:[~2018-03-05 14:53 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
2018-02-28 23:36 ` Adam Back
2018-03-01 5:11 ` アルム カールヨハン
2018-03-05 14:53 ` アルム カールヨハン [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=CALJw2w4Rcqw_G1eaMiiSkYyCLqRnx8wQvKpaHyPJKvOyRR3LWg@mail.gmail.com \
--to=karl@dglab.com \
--cc=aj@erisian.com.au \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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