public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99•net>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Small update to BIP 62
Date: Fri, 18 Jul 2014 17:39:56 +0200	[thread overview]
Message-ID: <CANEZrP3fA3gZ5u6yViBZpdTYxyFvZT=uOTDEnL797OueXf-16g@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBiTURdRAZbyk3guF5YzAAQebo8yY_TuXHUKYDEdLjDUdQ@mail.gmail.com>

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

The rationale doesn't seem to apply to rule #4, what's so special about
that one?

Although I agree not having to support all of DER is nice, in practice I
think all implementations do and libraries to parse DER are widespread.
Given that the last time we modified tx rules without bumping version
numbers we managed to break the only functioning iPhone client, I've become
a big fan of backwards compatibility: seems the default choice should be to
preserve compatibility over technical niceness until the old versions have
been fully phased out.

[-- Attachment #2: Type: text/html, Size: 608 bytes --]

  reply	other threads:[~2014-07-18 15:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 15:14 Pieter Wuille
2014-07-18 15:39 ` Mike Hearn [this message]
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
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='CANEZrP3fA3gZ5u6yViBZpdTYxyFvZT=uOTDEnL797OueXf-16g@mail.gmail.com' \
    --to=mike@plan99$(echo .)net \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=pieter.wuille@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