summaryrefslogtreecommitdiff
path: root/a3/8f3a2282ac642185ee37c4e430f62c85a0c404
blob: f53a7ce8f19df52b0cf90da0751294f6a6596281 (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
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
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <pete@petertodd.org>) id 1Wc5Vp-0005TW-6E
	for bitcoin-development@lists.sourceforge.net;
	Mon, 21 Apr 2014 04:07:21 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.100 as permitted sender)
	client-ip=62.13.148.100; envelope-from=pete@petertodd.org;
	helo=outmail148100.authsmtp.co.uk; 
Received: from outmail148100.authsmtp.co.uk ([62.13.148.100])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1Wc5Vl-0005bE-M9 for bitcoin-development@lists.sourceforge.net;
	Mon, 21 Apr 2014 04:07:21 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
	by punt15.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s3L47Bxr005482;
	Mon, 21 Apr 2014 05:07:11 +0100 (BST)
Received: from android-9217c60504b57c40.netgear.com
	(184-14-125-77.dsl1.chtn.wv.frontiernet.net [184.14.125.77])
	(authenticated bits=0)
	by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s3L46fFi076310
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 21 Apr 2014 05:06:58 +0100 (BST)
User-Agent: K-9 Mail for Android
In-Reply-To: <CACh7GpFGEvR+_qArYCkgi7AW4coSeH741ob4hmBpj6G3MayNAQ@mail.gmail.com>
References: <mailman.122233.1398039406.2207.bitcoin-development@lists.sourceforge.net>
	<52CDA01B-13BF-4BB8-AC9A-5FBBB324FD15@sant.ox.ac.uk>
	<CACh7GpFGEvR+_qArYCkgi7AW4coSeH741ob4hmBpj6G3MayNAQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8
From: Peter Todd <pete@petertodd.org>
Date: Mon, 21 Apr 2014 00:06:27 -0400
To: Mark Friedenbach <mark@monetize.io>,
	Jonathan Levin <jonathan.levin@sant.ox.ac.uk>
Message-ID: <a9a262a9-c70f-470d-81e0-ca32c41d8dc5@email.android.com>
X-Server-Quench: 69028e89-c90a-11e3-b802-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
	http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
	aQdMdAMUGUUGAgsB AmIbW1FeUFp7WWo7 agJVcwRZfEtMWhtt
	V1dNRFdNFUsrAmAF AEhoCxl1cQZHeDB4 ZEZlXD5dVUR4fRN1
	S1MHHG1XeGZhPWMC AkhYdR5UcAFPdx8U a1UrBXRDAzANdhES
	HhM4ODE3eDlSNilR RRkIIFQOdA4mFTk6 QBUDFi5nGkNNRiM9
	KAYjI0IdG0BZKl81 KVIuUE4ZNBl6
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 184.14.125.77/465
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
	anti-virus system.
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by punt15.authsmtp.com id
	s3L47Bxr005482
X-Spam-Score: -1.5 (-)
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 SPF_PASS               SPF: sender matches SPF record
X-Headers-End: 1Wc5Vl-0005bE-M9
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Economics of information propagation
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: Mon, 21 Apr 2014 04:07:21 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

That is mistaken: you can't mine on top of just a block header, leaving s=
mall miners disadvantaged as they are earning no profit while they wait f=
or the information to validate the block and update their UTXO sets. This=
 results in the same problem as before, as the large pools who mine most =
blocks can validate either instantly - the self-mine case - or more quick=
ly than the smaller miners.

Of course, in reality smaller miners can just mine on top of block header=
s and include no transactions and do no validation, but that is extremely=
 harmful to the security of Bitcoin.


On 20 April 2014 23:58:58 GMT-04:00, Mark Friedenbach <mark@monetize.io> =
wrote:
>As soon as we switch to headers
>first - which will be soon - there will be no difference in propagation
>time no matter how large the block is. Only 80 bites will be required
>to
>propagate the block header which establishes priority for when the
>block is
>fully validated.
>On Apr 20, 2014 6:56 PM, "Jonathan Levin"
><jonathan.levin@sant.ox.ac.uk>
>wrote:
>
>> Hi all,
>>
>> I am a post-graduate economist writing a paper on the incentives of
>> mining. Even though this issue has been debated in the forums, I
>think it
>> is important to get a sense of the magnitude of the incentives at
>play and
>> determine what implications this has for the transaction fee market.
>>
>> As it has been pointed out before the marginal cost for miners does
>not
>> stem from the private cost of the miner validating the signature and
>> including it in the list of transactions in the block but rather the
>> increased probability that the block will be orphaned as a result of
>slower
>> propagation. Gavin did some back of the envelope worst case
>calculations
>> but these overstated the effect of propagation delay. The reason
>being the
>> 80ms additional time to reach 50% of the network is spread throughout
>the
>> time that it takes to reach 50% of the network. During this time
>miners are
>> notified about the block and treat it as the longest chain and hence
>are no
>> longer mining with the aim to produce a competing block.
>>
>> I am looking to calculate the change in the curvature of the
>probability
>> mass function that a block hears about my block in any given second
>as a
>> function of the block size. Although there is likely to be
>significant
>> noise here, there seems to be some stable linear relationships with
>the
>> time that it takes to reach different quartiles. Has anyone done
>this? I
>> have used some empirical data that I am happy to share but ideally I
>would
>> like analytical solutions.
>>
>> Following Peter Todd, I also find the concerning result that
>propagation
>> delays results in increasing returns to higher shares of the hashing
>power.
>> Indeed it may well be in the interest of large pools to publish large
>> blocks to increase propagation delays on the network which would
>increase
>> orphan rates particularly for small miners and miners that have not
>> invested in sufficient bandwidth / connectivity. If a small miner
>hears
>> about a block after 4.5 seconds on average there is a 0.7% chance
>that
>> there is already a block in circulation.  Large miners can increase
>the
>> time that it takes for small miners to hear about blocks by
>increasing the
>> size of their blocks. For example if the time that it takes for a
>small
>> miner to hear about the block goes to 12 seconds there is a 2 percent
>> chance there is already a block in circulation for the small miner.
>There
>> is also a 1.2% chance that there will be a competing block published
>after
>> a small miner propagates in the time that it gets to full
>propagation. Am I
>> getting this right that the probability of a miner=E2=80=99s block bei=
ng
>orphaned
>> is comprised of the probability that the miner was not the first to
>find a
>> valid block and the probability that given they are first, someone
>else in
>> the absence of hearing about it finds a competing valid block.
>>
>> One question is: Are orphans probabilistic and only resolved after
>hearing
>> about a new block that lengthens the chain or is there a way to know
>in
>> advance? Is it frowned upon to mine on top of a block that you have
>just
>> found even though it is very likely going to end up an orphan?
>>
>> Would be happy to share the draft form of the paper and receive any
>> feedback.
>>
>> Finally, at coinometrics we are working on a modified client to
>capture
>> information on network propagation and would invite any suggestions
>of any
>> other useful statistics that would be useful in the development of
>software.
>>
>> Best,
>>
>> Jonathan
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On 21 Apr 2014, at 01:16, <
>> bitcoin-development-request@lists.sourceforge.net> <
>> bitcoin-development-request@lists.sourceforge.net> wrote:
>>
>> > Send Bitcoin-development mailing list submissions to
>> >       bitcoin-development@lists.sourceforge.net
>> >
>> > To subscribe or unsubscribe via the World Wide Web, visit
>> >
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> > or, via email, send a message with subject or body 'help' to
>> >       bitcoin-development-request@lists.sourceforge.net
>> >
>> > You can reach the person managing the list at
>> >       bitcoin-development-owner@lists.sourceforge.net
>> >
>> > When replying, please edit your Subject line so it is more specific
>> > than "Re: Contents of Bitcoin-development digest..."
>> >
>> >
>> > Today's Topics:
>> >
>> >   1. Re: "bits": Unit of account (Oliver Egginger)
>> >   2. Re: "bits": Unit of account (Christophe Biocca)
>> >   3. Re: "bits": Unit of account (Gmail)
>> >   4. Re: "bits": Unit of account (Mike Caldwell)
>> >   5. Re: "bits": Unit of account (Justin A)
>> >
>> >
>> >
>----------------------------------------------------------------------
>> >
>> > Message: 1
>> > Date: Sun, 20 Apr 2014 20:43:24 +0200
>> > From: Oliver Egginger <bitcoin@olivere.de>
>> > Subject: Re: [Bitcoin-development] "bits": Unit of account
>> > To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
>> > Message-ID: <5354154C.1080908@olivere.de>
>> > Content-Type: text/plain; charset=3DISO-8859-1
>> >
>> > Hello,
>> >
>> > just my two 'cents':
>> >
>> > Terms arises by itself. Just as most people speak of coins when
>they
>> > mean bitcoins. I do not see that bitcoin is currently in common use
>> > except for speculation. Therefore no term for smaller units has
>> > established yet. No problem in my eyes. Time will tell.
>> >
>> > - oliver
>> >
>> >
>> >
>> >
>> > ------------------------------
>> >
>> > Message: 2
>> > Date: Sun, 20 Apr 2014 15:19:38 -0400
>> > From: Christophe Biocca <christophe.biocca@gmail.com>
>> > Subject: Re: [Bitcoin-development] "bits": Unit of account
>> > To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
>> > Message-ID:
>> >       <CANOOu=3D9=3D
>> TAnaCuyh_P2GqHaguyY39xjhj84HSA_x+6F4MOqM_A@mail.gmail.com>
>> > Content-Type: text/plain; charset=3DUTF-8
>> >
>> > Culturally neutral? "bit" in French phonetically collides with
>slang
>> > for phallus ("bitte", with a silent "e"). Apparently it means
>"louse"
>> > in Turkish as well.
>> >
>> > Not that this really would be avoidable with any short word (all
>the
>> > short possible words are usually taken), but it's not neutral.
>> >
>> > On Sun, Apr 20, 2014 at 2:43 PM, Oliver Egginger
><bitcoin@olivere.de>
>> wrote:
>> >> Hello,
>> >>
>> >> just my two 'cents':
>> >>
>> >> Terms arises by itself. Just as most people speak of coins when
>they
>> >> mean bitcoins. I do not see that bitcoin is currently in common
>use
>> >> except for speculation. Therefore no term for smaller units has
>> >> established yet. No problem in my eyes. Time will tell.
>> >>
>> >> - oliver
>> >>
>> >>
>> >>
>>
>------------------------------------------------------------------------=
------
>> >> Learn Graph Databases - Download FREE O'Reilly Book
>> >> "Graph Databases" is the definitive new guide to graph databases
>and
>> their
>> >> applications. Written by three acclaimed leaders in the field,
>> >> this first edition is now available. Download your free book
>today!
>> >> http://p.sf.net/sfu/NeoTech
>> >> _______________________________________________
>> >> Bitcoin-development mailing list
>> >> Bitcoin-development@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> >
>> >
>> >
>> > ------------------------------
>> >
>> > Message: 3
>> > Date: Sun, 20 Apr 2014 14:32:26 -0500
>> > From: Gmail <will.yager@gmail.com>
>> > Subject: Re: [Bitcoin-development] "bits": Unit of account
>> > Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
>> > Message-ID: <B687D4AD-263F-4594-BE7A-FF238B8DF7AF@gmail.com>
>> > Content-Type: text/plain; charset=3D"us-ascii"
>> >
>> > People in the Bitcoin community are sometimes resistant to the idea
>of
>> using the word "credit" as a unit of Bitcoin, because Bitcoin is not
>a
>> credit-based system.
>> >
>> > However, given that the average person has close to no
>understanding of
>> what "credit" means, and probably no concern for the distinction even
>if
>> they do know, it may be wise to use the futuristic and easily
>> understandable "credit" as our human-friendly unit.
>> >
>> > Do others agree that "credits" as a unit of account has a desirable
>> futuristic connotation?
>> >
>> > Will
>> >
>> > -------------- next part --------------
>> > A non-text attachment was scrubbed...
>> > Name: smime.p7s
>> > Type: application/pkcs7-signature
>> > Size: 1593 bytes
>> > Desc: not available
>> >
>> > ------------------------------
>> >
>> > Message: 4
>> > Date: Sun, 20 Apr 2014 16:28:34 -0400
>> > From: Mike Caldwell <mcaldwell@swipeclock.com>
>> > Subject: Re: [Bitcoin-development] "bits": Unit of account
>> > To: Christophe Biocca <christophe.biocca@gmail.com>
>> > Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
>> > Message-ID: <4098C706-D67F-474E-9C13-E4C8F56B41ED@swipeclock.com>
>> > Content-Type: text/plain; charset=3D"us-ascii"
>> >
>> > By culturally neutral I mean we avoid deliberately invoking a
>cultural
>> reference in the name.  For example "satoshi" would be a reference to
>> Japanese culture just for being a common Japanese name regardless of
>who
>> Satoshi turns out to be.
>> >
>> > Mike
>> >
>> > Sent from my iPhone
>> >
>> >> On Apr 20, 2014, at 1:20 PM, "Christophe Biocca" <
>> christophe.biocca@gmail.com> wrote:
>> >>
>> >> Culturally neutral? "bit" in French phonetically collides with
>slang
>> >> for phallus ("bitte", with a silent "e"). Apparently it means
>"louse"
>> >> in Turkish as well.
>> >>
>> >> Not that this really would be avoidable with any short word (all
>the
>> >> short possible words are usually taken), but it's not neutral.
>> >>
>> >>> On Sun, Apr 20, 2014 at 2:43 PM, Oliver Egginger
><bitcoin@olivere.de>
>> wrote:
>> >>> Hello,
>> >>>
>> >>> just my two 'cents':
>> >>>
>> >>> Terms arises by itself. Just as most people speak of coins when
>they
>> >>> mean bitcoins. I do not see that bitcoin is currently in common
>use
>> >>> except for speculation. Therefore no term for smaller units has
>> >>> established yet. No problem in my eyes. Time will tell.
>> >>>
>> >>> - oliver
>> >>>
>> >>>
>> >>>
>>
>------------------------------------------------------------------------=
------
>> >>> Learn Graph Databases - Download FREE O'Reilly Book
>> >>> "Graph Databases" is the definitive new guide to graph databases
>and
>> their
>> >>> applications. Written by three acclaimed leaders in the field,
>> >>> this first edition is now available. Download your free book
>today!
>> >>> http://p.sf.net/sfu/NeoTech
>> >>> _______________________________________________
>> >>> Bitcoin-development mailing list
>> >>> Bitcoin-development@lists.sourceforge.net
>> >>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> >>
>> >>
>>
>------------------------------------------------------------------------=
------
>> >> Learn Graph Databases - Download FREE O'Reilly Book
>> >> "Graph Databases" is the definitive new guide to graph databases
>and
>> their
>> >> applications. Written by three acclaimed leaders in the field,
>> >> this first edition is now available. Download your free book
>today!
>> >> http://p.sf.net/sfu/NeoTech
>> >> _______________________________________________
>> >> Bitcoin-development mailing list
>> >> Bitcoin-development@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> >
>> >
>> >
>> > ------------------------------
>> >
>> > Message: 5
>> > Date: Sun, 20 Apr 2014 20:16:35 -0400
>> > From: Justin A <allport@gmail.com>
>> > Subject: Re: [Bitcoin-development] "bits": Unit of account
>> > To: Mike Caldwell <mcaldwell@swipeclock.com>
>> > Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
>> > Message-ID:
>> >       <
>> CAK2MuX3GufxU_AH0Kaw3pUkzgX_agok86ahCh+7r96UkxZwneQ@mail.gmail.com>
>> > Content-Type: text/plain; charset=3D"utf-8"
>> >
>> > <delurk>
>> >
>> > What about "ubit", pronounced "YOU-bit", representing 1e-6 bitcoin?
>Easy
>> to
>> > say, tied in a visual way to the metric micro, leaves the required
>2
>> > decimal places for the marginally numerate.. What more could one
>want?
>> >
>> > </delurk>
>> >
>> > Also, hi. My first post; plan to get involved over the southern
>> hemisphere
>> > winter if I can learn enough.
>> > On Apr 20, 2014 4:32 PM, "Mike Caldwell" <mcaldwell@swipeclock.com>
>> wrote:
>> >
>> >> By culturally neutral I mean we avoid deliberately invoking a
>cultural
>> >> reference in the name.  For example "satoshi" would be a reference
>to
>> >> Japanese culture just for being a common Japanese name regardless
>of who
>> >> Satoshi turns out to be.
>> >>
>> >> Mike
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On Apr 20, 2014, at 1:20 PM, "Christophe Biocca" <
>> >> christophe.biocca@gmail.com> wrote:
>> >>>
>> >>> Culturally neutral? "bit" in French phonetically collides with
>slang
>> >>> for phallus ("bitte", with a silent "e"). Apparently it means
>"louse"
>> >>> in Turkish as well.
>> >>>
>> >>> Not that this really would be avoidable with any short word (all
>the
>> >>> short possible words are usually taken), but it's not neutral.
>> >>>
>> >>>> On Sun, Apr 20, 2014 at 2:43 PM, Oliver Egginger
><bitcoin@olivere.de>
>> >> wrote:
>> >>>> Hello,
>> >>>>
>> >>>> just my two 'cents':
>> >>>>
>> >>>> Terms arises by itself. Just as most people speak of coins when
>they
>> >>>> mean bitcoins. I do not see that bitcoin is currently in common
>use
>> >>>> except for speculation. Therefore no term for smaller units has
>> >>>> established yet. No problem in my eyes. Time will tell.
>> >>>>
>> >>>> - oliver
>> >>>>
>> >>>>
>> >>>>
>> >>
>>
>------------------------------------------------------------------------=
------
>> >>>> Learn Graph Databases - Download FREE O'Reilly Book
>> >>>> "Graph Databases" is the definitive new guide to graph databases
>and
>> >> their
>> >>>> applications. Written by three acclaimed leaders in the field,
>> >>>> this first edition is now available. Download your free book
>today!
>> >>>> http://p.sf.net/sfu/NeoTech
>> >>>> _______________________________________________
>> >>>> Bitcoin-development mailing list
>> >>>> Bitcoin-development@lists.sourceforge.net
>> >>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> >>>
>> >>>
>> >>
>>
>------------------------------------------------------------------------=
------
>> >>> Learn Graph Databases - Download FREE O'Reilly Book
>> >>> "Graph Databases" is the definitive new guide to graph databases
>and
>> >> their
>> >>> applications. Written by three acclaimed leaders in the field,
>> >>> this first edition is now available. Download your free book
>today!
>> >>> http://p.sf.net/sfu/NeoTech
>> >>> _______________________________________________
>> >>> Bitcoin-development mailing list
>> >>> Bitcoin-development@lists.sourceforge.net
>> >>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> >>
>> >>
>> >>
>>
>------------------------------------------------------------------------=
------
>> >> Learn Graph Databases - Download FREE O'Reilly Book
>> >> "Graph Databases" is the definitive new guide to graph databases
>and
>> their
>> >> applications. Written by three acclaimed leaders in the field,
>> >> this first edition is now available. Download your free book
>today!
>> >> http://p.sf.net/sfu/NeoTech
>> >> _______________________________________________
>> >> Bitcoin-development mailing list
>> >> Bitcoin-development@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> >>
>> > -------------- next part --------------
>> > An HTML attachment was scrubbed...
>> >
>> > ------------------------------
>> >
>> >
>>
>------------------------------------------------------------------------=
------
>> > Start Your Social Network Today - Download eXo Platform
>> > Build your Enterprise Intranet with eXo Platform Software
>> > Java Based Open Source Intranet - Social, Extensible, Cloud Ready
>> > Get Started Now And Turn Your Intranet Into A Collaboration
>Platform
>> > http://p.sf.net/sfu/ExoPlatform
>> >
>> > ------------------------------
>> >
>> > _______________________________________________
>> > Bitcoin-development mailing list
>> > Bitcoin-development@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> >
>> >
>> > End of Bitcoin-development Digest, Vol 35, Issue 72
>> > ***************************************************
>>
>>
>>
>>
>------------------------------------------------------------------------=
------
>> Start Your Social Network Today - Download eXo Platform
>> Build your Enterprise Intranet with eXo Platform Software
>> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
>> Get Started Now And Turn Your Intranet Into A Collaboration Platform
>> http://p.sf.net/sfu/ExoPlatform
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>
>
>------------------------------------------------------------------------
>
>------------------------------------------------------------------------=
------
>Start Your Social Network Today - Download eXo Platform
>Build your Enterprise Intranet with eXo Platform Software
>Java Based Open Source Intranet - Social, Extensible, Cloud Ready
>Get Started Now And Turn Your Intranet Into A Collaboration Platform
>http://p.sf.net/sfu/ExoPlatform
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1

iQFQBAEBCAA6BQJTVJlDMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhTbNB/4lHTsUN/iee7H0UyBn
+TDRgf1BSoUx9HP+vtwXzS0JkVQoxoB5x4Pls+ex7qIXGNxdG9EPYi1RqQ5A8RUo
X2ntOL2pj6qTmW4aYxqqyihiQayLs5ixHPmJxqHv343g5ekqsKmBeDuWR4hXjUyZ
0Pfcp40Xd3eJ38dSbq98letl5eD+ryBPKYtb91Trumqa9S0WB8kw9IqNaXjlpfG1
lYuaVEllpaLpZW+4cx1mlPneS1GmLvloWhXf4Qh4X39VXECAjOAmNKh1atJCyT7H
ugkOcx1F2Rxo5P3jNzBRJKyAD96sbOhKm4sX7rzSjhT3WJgyHtJm3wkeluDCOVbR
QZqK
=3DR7Tv
-----END PGP SIGNATURE-----