From: Justus Ranvier <justus@openbitcoinprivacyproject•org>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Bitcoin-development] Reusable payment codes
Date: Thu, 22 Oct 2015 17:01:10 -0500 [thread overview]
Message-ID: <56295CA6.4080208@openbitcoinprivacyproject.org> (raw)
In-Reply-To: <201510222147.28878.luke@dashjr.org>
[-- Attachment #1.1: Type: text/plain, Size: 1469 bytes --]
On 22/10/15 16:47, Luke Dashjr wrote:
> Well, I strongly disagree with adopting the BIP as it stands.
That's fine. Nobody is required to adopt an informational BIP if they do
not wish to do so.
> No, those are not network-level changes. They are mere software changes that
> can be deployed along with the rest of the proposal.
They are "mere software changes" outside the control of the users and
wallet developers who may wish to use and implement payment codes, so
are indistinguishable from a network-level change.
> "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.
Since Bitcoin Core 0.11, 80 byte OP_RETURN transactions are standard, so
that's what payment codes use:
https://github.com/bitcoin/bitcoin/commit/fcf646c
Whether or not it "should" have an influence, it is an absolute fact
that Bitcoin users are affected by it.
A user whose transactions are not relayed or mined doesn't care about
the politics surrounding node policy.
Designing standards without putting the needs of its intended users
first is a great way to see the standard fail.
> Such changes should not be made until there is a standard for them.
Have you ever heard the term "permissionless innovation" by chance?
Particularly in reference to Bitcoin?
If you don't like payment codes, then don't use them.
[-- Attachment #1.2: 0xEAD9E623.asc --]
[-- Type: application/pgp-keys, Size: 18729 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2015-10-22 22:01 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
2015-10-22 22:01 ` Justus Ranvier [this message]
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=56295CA6.4080208@openbitcoinprivacyproject.org \
--to=justus@openbitcoinprivacyproject$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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