blob: 8234770241c24f11754e7d379befd4b4d7141131 (
plain)
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
|
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 <bgroff@lavabit.com>) id 1QX4aT-0005jO-Fc
for bitcoin-development@lists.sourceforge.net;
Thu, 16 Jun 2011 04:53:49 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of lavabit.com
designates 72.249.41.33 as permitted sender)
client-ip=72.249.41.33; envelope-from=bgroff@lavabit.com;
helo=karen.lavabit.com;
Received: from karen.lavabit.com ([72.249.41.33])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1QX4aQ-0000mk-Mo for bitcoin-development@lists.sourceforge.net;
Thu, 16 Jun 2011 04:53:49 +0000
Received: from a.earth.lavabit.com (a.earth.lavabit.com [192.168.111.10])
by karen.lavabit.com (Postfix) with ESMTP id 0A39111C010
for <bitcoin-development@lists.sourceforge.net>;
Wed, 15 Jun 2011 23:53:41 -0500 (CDT)
Received: from lavabit.com (s214856783.online.de [87.106.138.84])
by lavabit.com with ESMTP id L6DD4Z4VJRPY
for <bitcoin-development@lists.sourceforge.net>;
Wed, 15 Jun 2011 23:53:41 -0500
Received: from 87.106.138.84 (SquirrelMail authenticated user bgroff)
by lavabit.com with HTTP; Thu, 16 Jun 2011 00:53:40 -0400 (EDT)
Message-ID: <18440.87.106.138.84.1308200020.squirrel@lavabit.com>
Date: Thu, 16 Jun 2011 00:53:40 -0400 (EDT)
From: bgroff@lavabit.com
To: bitcoin-development@lists.sourceforge.net
User-Agent: SquirrelMail/1.4.13
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.4 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
X-Headers-End: 1QX4aQ-0000mk-Mo
Subject: [Bitcoin-development] [PULL] Add scriptPubKey enforced sendescrow
and redeemescrow API calls
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, 16 Jun 2011 04:53:49 -0000
I have a pull request here:
https://github.com/bitcoin/bitcoin/pull/319
From the README:
Bitcoin "escrow" are coins that are under the control of multiple
parties. The initial implementation allows n parties to vote, with
k good signatures needed (k <=3D n).
This eliminates single points of failure and reduces the trust required
in many transaction use cases.
Use cases include Escrow (without trusting the escrow agent with the
coins), immediate payment and funds locked with multi-party signatures.
This was inspired by https://forum.bitcoin.org/index.php?topic=3D8821.0 a=
nd
https://forum.bitcoin.org/index.php?topic=3D4723.msg68804 .
Feedback on the pull is very much appreciated.
|
