From: Luke Dashjr <luke@dashjr•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:47:27 +0000 [thread overview]
Message-ID: <201510222147.28878.luke@dashjr.org> (raw)
In-Reply-To: <56294E12.60301@openbitcoinprivacyproject.org>
On Thursday, October 22, 2015 8:58:58 PM Justus Ranvier wrote:
> I strongly disagree with this statement.
Well, I strongly disagree with adopting the BIP as it stands.
> 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.
No, those are not network-level changes. They are mere software changes that
can be deployed along with the rest of the proposal.
> 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.
"Standard" means defined in a BIP. To date, there are no standard
transactions using OP_RETURN period. IsStandard is a node policy that should
have no influence on future BIPs.
> When additional capabilities are deployed in the network such that
> Bitcoin users can rely on their existence, that would be a great time to
> specify a version 2 payment code that uses those features and encourage
> users to upgrade (which should be a fairly smooth process since their
> actual keys don't need to change).
Such changes should not be made until there is a standard for them.
Luke
next prev parent reply other threads:[~2015-10-22 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 5:53 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 [this message]
2015-10-22 22:01 ` Justus Ranvier
2015-10-23 1:22 ` Peter Todd
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=201510222147.28878.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=justus@openbitcoinprivacyproject$(echo .)org \
/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