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
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <etotheipi@gmail.com>) id 1XCbls-000176-Tp
for bitcoin-development@lists.sourceforge.net;
Wed, 30 Jul 2014 21:50:52 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.51 as permitted sender)
client-ip=209.85.192.51; envelope-from=etotheipi@gmail.com;
helo=mail-qg0-f51.google.com;
Received: from mail-qg0-f51.google.com ([209.85.192.51])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XCblr-0006YN-Ij
for bitcoin-development@lists.sourceforge.net;
Wed, 30 Jul 2014 21:50:52 +0000
Received: by mail-qg0-f51.google.com with SMTP id a108so2714402qge.24
for <bitcoin-development@lists.sourceforge.net>;
Wed, 30 Jul 2014 14:50:46 -0700 (PDT)
X-Received: by 10.224.137.135 with SMTP id w7mr11582559qat.52.1406757046046;
Wed, 30 Jul 2014 14:50:46 -0700 (PDT)
Received: from [192.168.1.85] (c-76-111-96-126.hsd1.md.comcast.net.
[76.111.96.126])
by mx.google.com with ESMTPSA id n3sm6051245qai.14.2014.07.30.14.50.44
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Wed, 30 Jul 2014 14:50:45 -0700 (PDT)
Message-ID: <53D9689E.4040707@gmail.com>
Date: Wed, 30 Jul 2014 17:50:22 -0400
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative;
boundary="------------030108010808010808040702"
X-Spam-Score: -0.6 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(etotheipi[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1XCblr-0006YN-Ij
Subject: [Bitcoin-development] [ANN] Armory 0.92 with Decentralized
Multi-sig and Simulfunding
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: Wed, 30 Jul 2014 21:50:53 -0000
This is a multi-part message in MIME format.
--------------030108010808010808040702
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Hi Everyone,
The Armory team is pleased to announce the official release of our
decentralized multi-signature interface, called "Lockboxes". It is a
"true" multi-signature transaction interface:
* Decentralized multi-sig (no third-party servers or signers needed)
* Any multi-sig from 1-of-2 up to 7-of-7
* Any or all of the signing devices can be *offline*
* All private keys can be generated and managed independently
* Works with existing Armory wallets
* Simultaneous funding ("simulfunding") features for escrow and
contracts (basically CoinJoin)
* All wrapped up in a nice graphical user interface!
Armory 0.92 includes a GUI for creating, funding and spending from
multi-signature lockboxes, anything from 1-of-2 up to 7-of-7. All
private keys can be generated independently and never have to be
co-located. Most importantly, any number of the signing keys can be
created and managed on offline computers! Also, all transaction and
signature data is communicated directly between parties/devices using
ASCII-armored blocks of text, so no third-party servers/services are
needed (though, in the future, we hope to provide an optional service to
help synchronize the data between parties).
The release also includes the ability to do simultaneous funding
("simulfunding") which is basically CoinJoin through a GUI, but intended
to be used for contracts and escrow. Each party creates a "promissory
note" (which is basically just a list of UTXOs and a change address),
and those can be merged into a single transaction to be signed by all
funders. Either all contributions are made simutaneously, or none of
them are. There is no other outcome. This means that no trust is
required between the simulfunders. It is a basic contract enforced by
the bitcoin network itself.
Simulfunding would normally be used in conjuction with multi-signature
lockboxes -- two parties that don't trust each other together create a
lockbox, and then simultaneously fund it (and subsequently spend it)
according to some agreement. However, it can actually be used to
simulfund any address. To promote this feature, Armory Technologies Inc
is offering to match up to 20 BTC in donations to the EFF, FSF, College
Crypto Network, Chamber of Digital Commerce, and the Bitcoin Foundation
(and hopefully wikipedia, as a late addition to the list). We posted
a list of ATI "promissory notes" for matching donations on our
website: https://bitcoinarmory.com/donation-match-list/
We're very excited about this release, which has been in testing for
over three months, and we've been using for management of company funds
between officers for the last two months. We have not seen anything
else that comes close to matching the flexibility and security afforded
by it (and without being exceptionally inconvenient!). See our
tutorials, and especially the FAQ at the end:
https://bitcoinarmory.com/about/using-lockboxes
https://bitcoinarmory.com/about/using-lockboxes/#faq
We hope that people will try it out and provide feedback. Maybe even
match some donations! We've already matched 3 BTC so far and it was
announced less than 24 hours ago.
Cheers,
-Alan
------
Press Release:
http://finance.yahoo.com/news/armory-releases-first-decentralized-multi-233500704.html
------
Changelog:
*VERSION 0.92**
**Released July 29, 2014**
*
- *Multi-Signature Lockboxes!*
Full-featured interface for creating multi-signature addresses,
putting money into them, and collecting signatures to spend them.
See our tutorials at:
https://bitcoinarmory.com/about/using-lockboxes/
- *Simulfunding for Addresses and Lockboxes*
Use the "Multi-Sig" menu to do prepare simulfunding to any
arbitrary address. Or click on the "Simul" checkbox in the
lockbox manager if you are simulfunding a lockbox. As a promotion
for this feature we are matching up to 20 BTC worth donations
to organizations that support Bitcoin, digital security, online
freedoms, and open-source software. See our donation list (with
instructions): https://bitcoinarmory.com/about/donation-match-list
- *Improved Mac/OSX Stability*
We merged a couple Qt4 patches that dramatically improved
compatibility on OSX 10.7 and newer. Should work with the
upcoming release of OSX 10.10.
- *Armory Daemon/API Upgrades (Beta)*
The Armory API has been upgraded substantially since version 0.91.
This version has tons of new functionality matching bitcoind,
as well as unique functionality including lockbox operations.
Plan to have complete functionality implemented and tested by
version 0.93.
- *Upgraded Transaction History Export to CSV*
Added running balance reporting for individual and all wallets.
Also fixed a bug where internal transfers within wallets were
not being reported properly.
- *Root PUBLIC Key Export*
You can now export just the root public key data that allows
you to reconstruct your watching-only wallet. It is five lines
that are easily printed or copied by hand. Could be used to
provide someone a chain of addresses for multiple payments.
--------------030108010808010808040702
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Everyone,<br>
<br>
The Armory team is pleased to announce the official release of our
decentralized multi-signature interface, called "Lockboxes". It is
a "true" multi-signature transaction interface:<br>
<ul>
<li>Decentralized multi-sig (no third-party servers or signers
needed)</li>
<li>Any multi-sig from 1-of-2 up to 7-of-7</li>
<li>Any or all of the signing devices can be *offline*</li>
<li>All private keys can be generated and managed independently</li>
<li>Works with existing Armory wallets<br>
</li>
<li>Simultaneous funding ("simulfunding") features for escrow and
contracts (basically CoinJoin)<br>
</li>
<li>All wrapped up in a nice graphical user interface!<br>
</li>
</ul>
Armory 0.92 includes a GUI for creating, funding and spending from
multi-signature lockboxes, anything from 1-of-2 up to 7-of-7. All
private keys can be generated independently and never have to be
co-located. Most importantly, any number of the signing keys can
be created and managed on offline computers! Also, all transaction
and signature data is communicated directly between parties/devices
using ASCII-armored blocks of text, so no third-party
servers/services are needed (though, in the future, we hope to
provide an optional service to help synchronize the data between
parties).<br>
<br>
The release also includes the ability to do simultaneous funding
("simulfunding") which is basically CoinJoin through a GUI, but
intended to be used for contracts and escrow. Each party creates a
"promissory note" (which is basically just a list of UTXOs and a
change address), and those can be merged into a single transaction
to be signed by all funders. Either all contributions are made
simutaneously, or none of them are. There is no other outcome.
This means that no trust is required between the simulfunders. It
is a basic contract enforced by the bitcoin network itself.<br>
<br>
Simulfunding would normally be used in conjuction with
multi-signature lockboxes -- two parties that don't trust each other
together create a lockbox, and then simultaneously fund it (and
subsequently spend it) according to some agreement. However, it can
actually be used to simulfund any address. To promote this feature,
Armory Technologies Inc is offering to match up to 20 BTC in
donations to the EFF, FSF, College Crypto Network, Chamber of
Digital Commerce, and the Bitcoin Foundation (and hopefully
wikipedia, as a late addition to the list). We posted a list of
ATI "promissory notes" for matching donations on our website:
<a class="moz-txt-link-freetext" href="https://bitcoinarmory.com/donation-match-list/">https://bitcoinarmory.com/donation-match-list/</a><br>
<br>
We're very excited about this release, which has been in testing for
over three months, and we've been using for management of company
funds between officers for the last two months. We have not seen
anything else that comes close to matching the flexibility and
security afforded by it (and without being exceptionally
inconvenient!). See our tutorials, and especially the FAQ at the
end: <br>
<br>
<a class="moz-txt-link-freetext" href="https://bitcoinarmory.com/about/using-lockboxes">https://bitcoinarmory.com/about/using-lockboxes</a><br>
<a class="moz-txt-link-freetext" href="https://bitcoinarmory.com/about/using-lockboxes/#faq">https://bitcoinarmory.com/about/using-lockboxes/#faq</a><br>
<br>
We hope that people will try it out and provide feedback. Maybe
even match some donations! We've already matched 3 BTC so far and
it was announced less than 24 hours ago. <br>
<br>
Cheers,<br>
-Alan<br>
<br>
<br>
------<br>
Press Release:
<a class="moz-txt-link-freetext" href="http://finance.yahoo.com/news/armory-releases-first-decentralized-multi-233500704.html">http://finance.yahoo.com/news/armory-releases-first-decentralized-multi-233500704.html</a><br>
------<br>
Changelog:<br>
<br>
<b>VERSION 0.92</b><b><br>
</b><b>Released July 29, 2014</b><b><br>
</b><br>
<br>
- <b>Multi-Signature Lockboxes!</b><br>
Full-featured interface for creating multi-signature
addresses,<br>
putting money into them, and collecting signatures to
spend them.<br>
See our tutorials at:
<a class="moz-txt-link-freetext" href="https://bitcoinarmory.com/about/using-lockboxes/">https://bitcoinarmory.com/about/using-lockboxes/</a><br>
<br>
- <b>Simulfunding for Addresses and Lockboxes</b><br>
Use the "Multi-Sig" menu to do prepare simulfunding to any<br>
arbitrary address. Or click on the "Simul" checkbox in
the<br>
lockbox manager if you are simulfunding a lockbox. As a
promotion<br>
for this feature we are matching up to 20 BTC worth
donations<br>
to organizations that support Bitcoin, digital security,
online<br>
freedoms, and open-source software. See our donation list
(with<br>
instructions):
<a class="moz-txt-link-freetext" href="https://bitcoinarmory.com/about/donation-match-list">https://bitcoinarmory.com/about/donation-match-list</a><br>
<br>
- <b>Improved Mac/OSX Stability</b><br>
We merged a couple Qt4 patches that dramatically improved<br>
compatibility on OSX 10.7 and newer. Should work with the<br>
upcoming release of OSX 10.10.<br>
<br>
- <b>Armory Daemon/API Upgrades (Beta)</b><br>
The Armory API has been upgraded substantially since
version 0.91.<br>
This version has tons of new functionality matching
bitcoind,<br>
as well as unique functionality including lockbox
operations.<br>
Plan to have complete functionality implemented and tested
by<br>
version 0.93.<br>
<br>
- <b>Upgraded Transaction History Export to CSV</b><br>
Added running balance reporting for individual and all
wallets.<br>
Also fixed a bug where internal transfers within wallets
were<br>
not being reported properly.<br>
<br>
- <b>Root PUBLIC Key Export</b><br>
You can now export just the root public key data that
allows<br>
you to reconstruct your watching-only wallet. It is five
lines<br>
that are easily printed or copied by hand. Could be used
to<br>
provide someone a chain of addresses for multiple
payments.<br>
<br>
</body>
</html>
--------------030108010808010808040702--
|
