From: Gregory Maxwell <gmaxwell@gmail•com>
To: Jeff Garzik <jgarzik@gmail•com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Contradiction in BIP65 text?
Date: Sat, 14 Nov 2015 00:29:51 +0000 [thread overview]
Message-ID: <CAAS2fgR1RcteCd-RZzi1bUjEsFRVi7DduDBiUkg6+RgHzuL+-Q@mail.gmail.com> (raw)
In-Reply-To: <CADm_WcZnOXqcse1LC28ptLyxXJTtbv+RPMfrMamR4xZK3xcK8Q@mail.gmail.com>
On Fri, Nov 13, 2015 at 11:58 PM, Jeff Garzik via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> On Fri, Nov 13, 2015 at 4:48 PM, xor via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
>>
>> This clearly says that funds can be frozen.
>> Can the BIP65-thing be used to freeze funds or can it not be?
> This language definitely trips up or worries several folks - it's been
> mentioned a few times before.
>
> The user _chooses_ to freeze _their own_ funds. It is not an unwilling act
> of force, which many assume when they see the phrase "freeze funds."
The most frequent related point of confusion I see is that people have
a dangerously wrong mental model of how scrpitpubkeys work.
It seems people think that wallets will infer whatever they can
possibly spend and display that. This is not how wallets work, and if
any wallet were ever created like that its users would immediately go
broke (and it's author should be taken out and shot. :) ).
Rather, wallets must only display funds paid to scriptpubkeys (also
addresses) they actually generated or, at least, would have generated.
Otherwise someone can just create a 1 of 2 {them, you} multisig and
then claw back the coins after you think you've been paid.
As such there is no risk of anyone sneaking in CLTV locked funds for
on you except by virtue of spectacular software bugs that would likely
cause you to destroy funds in a zillion other ways first.
next prev parent reply other threads:[~2015-11-14 0:29 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
2015-11-13 22:08 ` xor
2015-11-13 23:58 ` Jeff Garzik
2015-11-14 0:29 ` Gregory Maxwell [this message]
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=CAAS2fgR1RcteCd-RZzi1bUjEsFRVi7DduDBiUkg6+RgHzuL+-Q@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jgarzik@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