1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <wendel@314t.com>) id 1VHYjl-0008BS-7k
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Sep 2013 12:32:37 +0000
X-ACL-Warn:
Received: from mail-yh0-f47.google.com ([209.85.213.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VHYjj-00082D-Hm
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Sep 2013 12:32:37 +0000
Received: by mail-yh0-f47.google.com with SMTP id 29so477919yhl.20
for <bitcoin-development@lists.sourceforge.net>;
Thu, 05 Sep 2013 05:32:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:sender:subject:mime-version:content-type:from
:in-reply-to:date:cc:content-transfer-encoding:message-id:references
:to; bh=yBBC35htWjLaLJQ3AVdjytiGa+pe3sX7cjzoBc33pGk=;
b=OvxMlogPxEIj8B1K6+4dYPgeaneK6Qiv9Oh+M+trUU4nY6L5Qj079xWH1GFCvkwCLt
1r0BvNCaU2LP4k42uxBH9voB2h48zcJgVbIT96OgQXn/Ago+4tLfeJTiYkNf1SmuvCPt
iVFvw0tBMfP6ZlK6Kj4SEheFJohilkgG0SJ67t9k7R7RDzaDAgQiWWLC39zUx5d+9YEw
p/Q6C+k3V7mcYKWMdLHDdc3WFgaAPmLD7pBcgpQ92VSWOzn6E2A9gktl7T1pZBIwvLyS
GQACKyRg+VuL2pcTrhFdmV+n8bvNkR5XhPhtl0B8DjJs8JQymRgb1CoOspOxGMjmonUN
r4iQ==
X-Gm-Message-State: ALoCoQnCMXb+HTu+rztdzeNN3QdDkcQD0LopSpYj/oEJWexkEZM8etL46kTp1uGRfUYZMNZswlAS
X-Received: by 10.236.138.194 with SMTP id a42mr8125437yhj.58.1378383007344;
Thu, 05 Sep 2013 05:10:07 -0700 (PDT)
Received: from [127.0.0.1] (bolobolo2.torservers.net. [96.47.226.21])
by mx.google.com with ESMTPSA id
g22sm35466233yhm.26.1969.12.31.16.00.00
(version=TLSv1 cipher=RC4-SHA bits=128/128);
Thu, 05 Sep 2013 05:10:06 -0700 (PDT)
Sender: Wendell <wendel@314t.com>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Wendell <w@grabhive.com>
In-Reply-To: <CANEZrP3hrYZ5SYng=fknCqn_vg9gK4HTS7T-tdQNfc0MwZ5DtA@mail.gmail.com>
Date: Thu, 5 Sep 2013 14:09:55 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <40424BD6-6EF1-454E-AA9F-6AF4C723A4BE@grabhive.com>
References: <879EBFD7-3047-4ECD-B03B-941857F7970C@grabhive.com>
<CANEZrP1zAJ0bQHsqKgH=L4BpgE_kHGKNh=+mv=Tk++7OWA4C2g@mail.gmail.com>
<36036B83-CD26-497F-BC5A-FD69DAFF578C@grabhive.com>
<CANEZrP3hrYZ5SYng=fknCqn_vg9gK4HTS7T-tdQNfc0MwZ5DtA@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
X-Mailer: Apple Mail (2.1283)
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1VHYjj-00082D-Hm
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] An "app store" and non-network
transaction fees
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 05 Sep 2013 12:32:37 -0000
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.
>=20
> 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.
=46rom 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
|
