summaryrefslogtreecommitdiff
path: root/76/56ff7271ecd824014924986d94dffe94c18695
blob: dc97f90f4a694896ace74e43e60c1837979ab92a (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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gavinandresen@gmail.com>) id 1X7uS5-0000Wj-8X
	for bitcoin-development@lists.sourceforge.net;
	Thu, 17 Jul 2014 22:47:01 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.54 as permitted sender)
	client-ip=209.85.213.54; envelope-from=gavinandresen@gmail.com;
	helo=mail-yh0-f54.google.com; 
Received: from mail-yh0-f54.google.com ([209.85.213.54])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1X7uS3-0001Xm-DM
	for bitcoin-development@lists.sourceforge.net;
	Thu, 17 Jul 2014 22:47:01 +0000
Received: by mail-yh0-f54.google.com with SMTP id v1so1786613yhn.41
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 17 Jul 2014 15:46:53 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.236.172.161 with SMTP id t21mr545554yhl.65.1405637212983;
	Thu, 17 Jul 2014 15:46:52 -0700 (PDT)
Received: by 10.170.190.208 with HTTP; Thu, 17 Jul 2014 15:46:52 -0700 (PDT)
In-Reply-To: <CA+iPb=EaX=bvOjNtZ+LnYTMRLQQ9nFcrefAkBdv8eActoX_b8A@mail.gmail.com>
References: <CA+iPb=EaX=bvOjNtZ+LnYTMRLQQ9nFcrefAkBdv8eActoX_b8A@mail.gmail.com>
Date: Thu, 17 Jul 2014 18:46:52 -0400
Message-ID: <CABsx9T0ag_o_mu=5Q7Ju7s2hO3jz-o5g9FihE9h4B6+ednd2Pg@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Kaz Wesley <keziahw@gmail.com>
Content-Type: multipart/alternative; boundary=20cf304273e0c3595204fe6b6af3
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
	(gavinandresen[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: 1X7uS3-0001Xm-DM
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Squashing redundant tx data in blocks on
 the wire
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, 17 Jul 2014 22:47:01 -0000

--20cf304273e0c3595204fe6b6af3
Content-Type: text/plain; charset=ISO-8859-1

A couple of half-baked thoughts:

On Thu, Jul 17, 2014 at 5:35 PM, Kaz Wesley <keziahw@gmail.com> wrote:

> If there's support for this proposal, I can begin working on the specific
> implementation details, such as the bloom filters, message format, and
> capability advertisment, and draft a BIP once I have a concrete proposal
> for
> what those would look like and a corresponding precise cost/benefit
> analysis.
>

I'd encourage you to code up a prototype first (or at the same time), in
whatever programming language / networking library you're most familiar
with.

Maybe not even using the existing p2p protocol; there could be a
mining-only very-fast-block-propagation network separate from the existing
p2p network.

Combining your optimizations with "broadcast as many near-miss blocks as
bandwidth will allow" on a mining backbone network should allow insanely
fast propagation of most newly solved blocks.

-- 
--
Gavin Andresen

--20cf304273e0c3595204fe6b6af3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">A co=
uple of half-baked thoughts:</div><div class=3D"gmail_quote"><br></div><div=
 class=3D"gmail_quote">On Thu, Jul 17, 2014 at 5:35 PM, Kaz Wesley <span di=
r=3D"ltr">&lt;<a href=3D"mailto:keziahw@gmail.com" target=3D"_blank">keziah=
w@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>If there&#39;s support for this proposa=
l, I can begin working on the specific</div><div>implementation details, su=
ch as the bloom filters, message format, and</div>
<div>capability advertisment, and draft a BIP once I have a concrete propos=
al for</div>

<div>what those would look like and a corresponding precise cost/benefit an=
alysis.</div><span class=3D"HOEnZb"><font color=3D"#888888"><div></div></fo=
nt></span></blockquote></div><br>I&#39;d encourage you to code up a prototy=
pe first (or at the same time), in whatever programming language / networki=
ng library you&#39;re most familiar with.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Maybe not e=
ven using the existing p2p protocol; there could be a mining-only very-fast=
-block-propagation network separate from the existing p2p network.</div><di=
v class=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">Combining your optimizations with &quo=
t;broadcast as many near-miss blocks as bandwidth will allow&quot; on a min=
ing backbone network should allow insanely fast propagation of most newly s=
olved blocks.</div>
<div class=3D"gmail_extra"><br>-- <br>--<br>Gavin Andresen<br>
</div><div class=3D"gmail_extra"><br></div></div>

--20cf304273e0c3595204fe6b6af3--