public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP for Proof of Payment
Date: Sat, 6 Jun 2015 17:23:48 +0200	[thread overview]
Message-ID: <CAPg+sBg+rE-0cxMU480Fierq_dU+=93LBD+vDatGdcSkPbvjqA@mail.gmail.com> (raw)
In-Reply-To: <201506061518.19431.luke@dashjr.org>

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

On Sat, Jun 6, 2015 at 5:18 PM, Luke Dashjr <luke@dashjr.org> wrote:

> I also agree with Pieter, that this should *not* be so cleanly compatible
> with Bitcoin transactions. If you wish to share code, perhaps using an
> invalid opcode rather than OP_RETURN would be appropriate.


Using an invalid opcode would merely send funds into the void. It wouldn't
invalidate the transaction.

-- 
Pieter

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

  reply	other threads:[~2015-06-06 15:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-06 14:35 [Bitcoin-development] BIP for Proof of Payment Kalle Rosenbaum
2015-06-06 14:47 ` Pieter Wuille
2015-06-06 15:05   ` Kalle Rosenbaum
2015-06-06 15:13     ` Pieter Wuille
2015-06-06 16:20       ` Kalle Rosenbaum
2015-06-06 16:10     ` Tom Harding
2015-06-06 17:00       ` Kalle Rosenbaum
2015-06-06 21:25         ` Kalle Rosenbaum
2015-06-06 22:01           ` Luke Dashjr
2015-06-15  9:21           ` Kalle Rosenbaum
     [not found]             ` <CAPg+sBiWykR6RaHhbyYQbL=A5t1TmHgEmS_sC7jj9d3SUTMO9g@mail.gmail.com>
     [not found]               ` <CAPswA9zycU0pwZKaHU9J3Tvg=ovLJ8TZ9OH6ebTPONaRaiOE8g@mail.gmail.com>
2015-06-15 10:00                 ` Pieter Wuille
2015-06-15 11:59                   ` Kalle Rosenbaum
2015-06-16 14:31                     ` Pieter Wuille
2015-06-16 19:22                       ` Kalle Rosenbaum
2015-06-16 19:25                         ` Pieter Wuille
     [not found]                           ` <CAPswA9yFUAqFyNBFBnnwpT=B9RcdNssdjz-_KWbX5GuLM5Uyxw@mail.gmail.com>
2015-06-16 19:48                             ` Pieter Wuille
2015-06-17  9:51                               ` Kalle Rosenbaum
2015-06-21 14:39                                 ` Kalle Rosenbaum
     [not found]                                   ` <CAPswA9w8QaWV72UuGnitWWeDTr5MPKvzwrD5udmq_FQke-NGAQ@mail.gmail.com>
2015-07-24  6:55                                     ` [bitcoin-dev] " Kalle Rosenbaum
2015-07-27  8:14                                       ` Sriram Karra
     [not found]                                 ` <CABm2gDrickFojwmUi7GqAhSW5K0yTa_59VjKrY+wAXEq1MYUoA@mail.gmail.com>
2015-07-26 21:13                                   ` Kalle Rosenbaum
2015-07-27  9:08                                     ` Jorge Timón
2015-07-27 11:21                                       ` Kalle Rosenbaum
2015-06-16  5:26                   ` Tom Harding
2015-06-16 12:12                     ` Kalle Rosenbaum
2015-06-16 12:31                       ` Kalle Rosenbaum
2015-06-16 14:05                       ` Tom Harding
2015-06-16 16:22                         ` Kalle Rosenbaum
2015-06-06 15:18 ` Luke Dashjr
2015-06-06 15:23   ` Pieter Wuille [this message]
2015-06-06 15:32     ` Peter Todd
2015-06-06 16:35       ` Kalle Rosenbaum

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+sBg+rE-0cxMU480Fierq_dU+=93LBD+vDatGdcSkPbvjqA@mail.gmail.com' \
    --to=pieter.wuille@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=luke@dashjr.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