public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Small update to BIP 62
Date: Mon, 8 Sep 2014 01:31:45 +0200	[thread overview]
Message-ID: <CAPg+sBiGWAtToC+vmbtiHk13gq3oGEc4-eoAcGtzbSY=Tr+6XA@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBh5TXhKM_oxQpHUw-kLiQmyxCTO4nAO2jbnLUEQb=bdBA@mail.gmail.com>

On Wed, Sep 3, 2014 at 6:34 PM, Pieter Wuille <pieter.wuille@gmail.com> wrote:
> On Mon, Sep 1, 2014 at 10:48 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
>> Not related to this change but the definition of rule 4 may not be
>> sufficiently specific-- without a definition someone could reasonably
>> reach a different conclusion about OP_1NEGATE being a "push
>> operation", or might even decide any operation which added to the
>> stack was a "push operation".
>
> Good catch - I'll write an update soon.

>> Perhaps the rules should be reordered so that the applicable to all
>> transactions ones are contiguous and first?
> Ok.

>>> The first six and part of the seventh can be fixed by extra consensus rules.
>>
>> This should clarify that the scriptPubkey can still specify rules that
>> are inherently malleable [...]
> I'll try to reword.

I've sent out a new pull request
(https://github.com/bitcoin/bips/pull/102/files) that:
* Changes the order of the rules.
* Adds more reference documentation about minimal pushes and number encodings.
* Clarified that extra consensus rules cannot prevent someone from
creating outputs whose spending transactions will be malleable.

I haven't changed which rules are mandatory in v3, so this is a pure
clarification & reorganization of the text.

Any comments?

-- 
Pieter



  reply	other threads:[~2014-09-07 23:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 15:14 [Bitcoin-development] Small update to BIP 62 Pieter Wuille
2014-07-18 15:39 ` Mike Hearn
2014-07-18 15:45   ` Pieter Wuille
2014-07-18 17:25     ` Pieter Wuille
2014-07-18 18:10       ` Pieter Wuille
2014-07-18 20:56   ` Wladimir
2014-07-18 22:03     ` Aaron Voisine
2014-07-19  1:28       ` Gregory Maxwell
2014-07-19  4:38         ` Aaron Voisine
2014-07-19  6:56           ` Gregory Maxwell
2014-07-19  8:34             ` Aaron Voisine
2014-07-19 19:08             ` Aaron Voisine
2014-07-19 14:46     ` Pieter Wuille
2014-07-18 20:51 ` Wladimir
2014-09-01 20:48 ` Gregory Maxwell
2014-09-03 16:34   ` Pieter Wuille
2014-09-07 23:31     ` Pieter Wuille [this message]
2014-09-12 16:35       ` Pieter Wuille
2014-09-13 22:45         ` Pieter Wuille

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='CAPg+sBiGWAtToC+vmbtiHk13gq3oGEc4-eoAcGtzbSY=Tr+6XA@mail.gmail.com' \
    --to=pieter.wuille@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gmaxwell@gmail.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