public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Roy Badami <roy@gnomon.org.uk>
To: Jeff Garzik <jgarzik@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP 70 extension
Date: Tue, 24 Jun 2014 19:34:34 +0100	[thread overview]
Message-ID: <20140624183434.GG14815@giles.gnomon.org.uk> (raw)
In-Reply-To: <CAJHLa0Omiz+UhGjSKgYU7+b2YY7aN23w7o8CQntqMePFs7LkjA@mail.gmail.com>

On Tue, Jun 24, 2014 at 10:21:46AM -0400, Jeff Garzik wrote:
> On Tue, Jun 24, 2014 at 9:27 AM, Mike Hearn <mike@plan99.net> wrote:
> > Wallets would then be able to persist this data to disk and compete on cool visualisations for how much money you saved over time.
> 
> heh, this is a cool idea.
> 
> It also seems like it would be subject to instant inflation, as it's
> unprovable, and a rational economic actor may choose to exaggerate
> such numbers.  It also seems collectively rational by some points of
> view for all bitcoin actors to inflate this number.

Rather than offering discounts, how about offering automatic cashback?
I know they're kinda stupid, but I gather cashback deals are very
commonplace in the US and (probably as a result) not unheard of elsewhere.

So you add an optional cashback_to field to the Payment message,
distinct from but conceptually similar to the refund_to field.  The
wallet can tally up how much cashback is received, without having to
trust the merchants.

Much harder to game, AFAICS.

roy



  parent reply	other threads:[~2014-06-24 18:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 13:27 [Bitcoin-development] Proposed BIP 70 extension Mike Hearn
2014-06-24 14:21 ` Jeff Garzik
2014-06-24 14:24   ` Mike Hearn
2014-06-24 14:32     ` slush
2014-06-24 15:06       ` Mike Hearn
2014-06-24 15:15       ` Gmail
2014-06-24 15:48         ` Jeff Garzik
2014-06-24 19:00           ` Gmail
2014-06-24 19:34             ` Andy Alness
2014-06-24 20:12             ` Gavin Andresen
2014-06-24 20:28               ` Gmail
2014-06-25  8:25                 ` Mike Hearn
2014-06-25 13:33                   ` Jorge Timón
2014-06-25 18:10                     ` Jeff Garzik
2014-06-25 14:15                   ` slush
2014-06-25 16:03                     ` Gmail
2014-06-24 18:34   ` Roy Badami [this message]
2014-06-24 15:43 ` Andreas Schildbach
2014-06-24 15:59   ` Mike Hearn
2014-06-24 17:37 ` Drak

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=20140624183434.GG14815@giles.gnomon.org.uk \
    --to=roy@gnomon.org.uk \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@bitpay.com \
    /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