public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Justus Ranvier <justus@openbitcoinprivacyproject.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Bitcoin-development] Reusable payment codes
Date: Thu, 22 Oct 2015 21:22:48 -0400	[thread overview]
Message-ID: <20151023012248.GD22161@savin.petertodd.org> (raw)
In-Reply-To: <56294E12.60301@openbitcoinprivacyproject.org>

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

On Thu, Oct 22, 2015 at 03:58:58PM -0500, Justus Ranvier via bitcoin-dev wrote:
> On 22/10/15 15:43, Luke Dashjr wrote:
> > BIPs should in general not be 
> > designed around current software
> 
> I strongly disagree with this statement.
> 
> There is a version byte in the payment code specification for a reason.
> 
> Version 1 payment codes are designed to be deployable by wallet
> implementers today, without requiring them to wait on any network-level
> changes whatsoever, which includes IsStandard() redefinitions, or
> yet-to-be-invented-and-deployed filtering schemes.
> 
> As far as I know, multi-push OP_RETURN outputs are not standard
> transactions and so wallet users can not rely on transactions containing
> them to be relayed through the network, therefore any improvement to the
> protocol which requires that feature is not appropriate for version 1.

FWIW multi-push OP_RETURN outputs will be standard in v0.12.0:

https://github.com/bitcoin/bitcoin/pull/6424

-- 
'peter'[:-1]@petertodd.org
0000000000000000066dc6b040d8be42153f784df37745b46c4ad667e0788781

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]

  parent reply	other threads:[~2015-10-23  1:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22  5:53 [bitcoin-dev] [Bitcoin-development] Reusable payment codes Luke Dashjr
2015-10-22 14:55 ` Justus Ranvier
2015-10-22 20:43   ` Luke Dashjr
2015-10-22 20:58     ` Justus Ranvier
2015-10-22 21:47       ` Luke Dashjr
2015-10-22 22:01         ` Justus Ranvier
2015-10-23  1:22       ` Peter Todd [this message]
2015-10-23 15:57         ` Justus Ranvier
2015-10-22 21:05     ` Kristov Atlas

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=20151023012248.GD22161@savin.petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=justus@openbitcoinprivacyproject.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