From: Gregory Maxwell <gmaxwell@gmail•com>
To: xor@freenetproject•org
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Contradiction in BIP65 text?
Date: Fri, 13 Nov 2015 21:53:57 +0000 [thread overview]
Message-ID: <CAAS2fgQaUX92YUcO=WsC4rhkV3OsCXsSk6aJJ9m3V0vKMuC2FA@mail.gmail.com> (raw)
In-Reply-To: <1581446.3ZPnhFUSFq@1337h4x0r>
On Fri, Nov 13, 2015 at 9:48 PM, xor via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> BIP65 [1] says this:
>> Motivation
>> [...]
>> However, the nLockTime field can't prove that it is impossible to spend a
>> transaction output until some time in the future, as there is no way to
>> know if a valid signature for a different transaction spending that output
>> has been created.
>
> I'd interpret "can't prove that it is impossible to spend" = cannot be used
> for freezing funds.
>
> Then later, at "Motivation", it says:
>> Freezing Funds
>>
>> In addition to using cold storage, hardware wallets, and P2SH multisig
>> outputs to control funds, now funds can be frozen in UTXOs directly on the
>> blockchain.
>
> This clearly says that funds can be frozen.
> Can the BIP65-thing be used to freeze funds or can it not be?
>
> Notice: I am by no means someone who is able to read Bitcoin script. I'm
> rather an end user. So maybe I'm misinterpreting the document?
> I'm nevertheless trying to provide a "neutral" review from an outsider who's
> trying to understand whats new in 0.11.2.
> You may want to discard my opinion if you think that BIP65 is aimed at an
> audience with more experience.
The first text is explaining nlocktime without BIP65 in order to
explain the reason for having BIP65.
next prev parent reply other threads:[~2015-11-13 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 21:48 xor
2015-11-13 21:53 ` Gregory Maxwell [this message]
2015-11-13 22:08 ` xor
2015-11-13 23:58 ` Jeff Garzik
2015-11-14 0:29 ` Gregory Maxwell
2015-11-14 22:47 ` xor
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='CAAS2fgQaUX92YUcO=WsC4rhkV3OsCXsSk6aJJ9m3V0vKMuC2FA@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=xor@freenetproject$(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