public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wendell <w@grabhive.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] An "app store" and non-network transaction fees
Date: Fri, 18 Oct 2013 13:56:09 +0200	[thread overview]
Message-ID: <603C4126-241E-41BE-8C01-D8D390B0F725@grabhive.com> (raw)
In-Reply-To: <CANEZrP1zAJ0bQHsqKgH=L4BpgE_kHGKNh=+mv=Tk++7OWA4C2g@mail.gmail.com>

We've gone ahead and pushed a v1 API for this idea:
https://bitcointalk.org/index.php?topic=313352

No fees yet, just the basics.

-wendell

grabhive.com | twitter.com/grabhive | gpg: 6C0C9411

On Sep 5, 2013, at 10:26 AM, Mike Hearn wrote:

> Hey Wendell,
> 
> Interesting idea you have there!




      parent reply	other threads:[~2013-10-18 12:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 19:47 [Bitcoin-development] An "app store" and non-network transaction fees Wendell
2013-09-05  8:26 ` Mike Hearn
2013-09-05 10:04   ` Wendell
2013-09-05 10:14     ` Mike Hearn
2013-09-05 12:09       ` Wendell
2013-09-05 12:49         ` Mike Hearn
2013-10-18 11:56   ` Wendell [this message]

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=603C4126-241E-41BE-8C01-D8D390B0F725@grabhive.com \
    --to=w@grabhive.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=mike@plan99.net \
    /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