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: Thu, 5 Sep 2013 14:09:55 +0200 [thread overview]
Message-ID: <40424BD6-6EF1-454E-AA9F-6AF4C723A4BE@grabhive.com> (raw)
In-Reply-To: <CANEZrP3hrYZ5SYng=fknCqn_vg9gK4HTS7T-tdQNfc0MwZ5DtA@mail.gmail.com>
On Sep 5, 2013, at 12:14 PM, Mike Hearn wrote:
> On Thu, Sep 5, 2013 at 12:04 PM, Wendell <w@grabhive•com> wrote:
>> Funny you should mention it! I just mocked this idea up last week, though I assumed a cruder system of "voting" to an address that corresponds to a feature -- literally, voting with your wallet (for your wallet, ad infinitum). I watched your talk about assurance contracts and other "hidden" features, but am not entirely sure that I understood it enough to know how it would work in this context. Sorry for the persistent hand-holding requests, but some advice would be very welcome.
>
> Well, it's a bit complicated and needs some software development to do well. The best way to fund a complex project would be to raise the money using an assurance contr.... oh wait ;)
Well, let's assume that our "public good" is based on the 5-step model described here:
https://en.bitcoin.it/wiki/Contracts#Example_3:_Assurance_contracts
This good corresponds to something like "Facebook contact synchronization" and has a target of 50 BTC, though we also want to be able to take more if people are willing to give it.
From here, it is unfortunately a little over our collective heads; we have as of yet no experience with the scripting language. I suppose I'm trying to twist your arm for an example, and maybe an anecdote. How would we do it? Does it require the donors to do anything esoteric? I saw "but they do not broadcast it" -- does this happen automatically when coins are sent to that address, for example?
Confused but enthusiastic,
-wendell
grabhive.com | twitter.com/grabhive | gpg: 6C0C9411
next prev parent reply other threads:[~2013-09-05 12:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 19:47 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 [this message]
2013-09-05 12:49 ` Mike Hearn
2013-10-18 11:56 ` Wendell
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=40424BD6-6EF1-454E-AA9F-6AF4C723A4BE@grabhive.com \
--to=w@grabhive$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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