public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: xor <xor@freenetproject.org>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Contradiction in BIP65 text?
Date: Sat, 14 Nov 2015 23:47:23 +0100	[thread overview]
Message-ID: <1910992.nPu4WaYHE8@1337h4x0r> (raw)
In-Reply-To: <CADm_WcZnOXqcse1LC28ptLyxXJTtbv+RPMfrMamR4xZK3xcK8Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 944 bytes --]

On Friday, November 13, 2015 06:58:07 PM Jeff Garzik 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."

Oh, interesting, albeit that was not subject of my question.

My question in fact was whether *I* can use it to freeze *my* funds; because I 
think that would be an interesting feature for various purposes.
From the state of BIP65 I talked about, it is not even clear whether that is 
possible.

Your observation beyond that is a valid concern though.
So both should be addressed.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2015-11-14 22:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 21:48 [bitcoin-dev] Contradiction in BIP65 text? 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
2015-11-14 22:47   ` xor [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=1910992.nPu4WaYHE8@1337h4x0r \
    --to=xor@freenetproject.org \
    --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