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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WmqYp-00080V-4v
for bitcoin-development@lists.sourceforge.net;
Tue, 20 May 2014 20:22:55 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.181 as permitted sender)
client-ip=209.85.212.181; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f181.google.com;
Received: from mail-wi0-f181.google.com ([209.85.212.181])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WmqYo-000052-0d
for bitcoin-development@lists.sourceforge.net;
Tue, 20 May 2014 20:22:55 +0000
Received: by mail-wi0-f181.google.com with SMTP id n15so1642011wiw.2
for <bitcoin-development@lists.sourceforge.net>;
Tue, 20 May 2014 13:22:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type:content-transfer-encoding;
bh=1PoI3nmxqoS7N3knDMIXEr80e8R1N5n3iTLeZGdYfQc=;
b=StmyS5ECWAxxqbfQ/sCR8xkKNT9t/lzGRNLm/vzqgma/M8wUk2scqMBgZrPcNoI7Lt
26THnJLc0QoYZZKoTTy3HhAeL6vBQUyo61veHr7JKqsyaed+58AZePZqOPJ2hfEqEZ0D
6w208KFVhTP9t+ee8nJQnVFwfr4RYU7FrAUD2dXwxtodROTyF5P7GvLdL2+ukgjD3GV0
ZX2MhII9aMaz6Z1YBK66dHarLYLrovIz9yFLOFRYdjypBh8efgBW5hOy8mEjv8swpSpd
8HDoTUapCuykBl3AIhwvK1cBoMLnR7jEF+CEuJEpd95gRYars19XxHOAVwq8XtE7RVmT
YiXQ==
X-Gm-Message-State: ALoCoQkMrK/Z1ScDE99QJR8mRhCyykQLDoRL/BacAKGvKuUP/rEGjy8bJrFJlw7be2TxfzN2Jozx
X-Received: by 10.194.8.229 with SMTP id u5mr12442230wja.65.1400617367742;
Tue, 20 May 2014 13:22:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.240.166 with HTTP; Tue, 20 May 2014 13:22:27 -0700 (PDT)
In-Reply-To: <CALKy-wp_d5Tzu2POai5gpe+EJUVGuOvN58aGu2WekBjkhNm8Gw@mail.gmail.com>
References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com>
<CANAnSg0ABVyRcSaO2aEcqO8qaj+JdxRN4z-hLE-EbESv2TMf2g@mail.gmail.com>
<trinity-1957ed0e-a607-47d7-803b-71c59af8eb89-1400573744536@3capp-mailcom-bs08>
<20140520143710.GT26986@leitl.org>
<4078A034-6626-495D-B42F-BDA94ACE1DA3@gmail.com>
<CALKy-wodNVZK+3q79YUJLmTRjihP85va4Mcp=mnUQTuUfLh+zg@mail.gmail.com>
<CAJHLa0PjUqJd_Hfjiwfj5c1yb6LJZeZMS0LFHd3Ncb+Ly88F8w@mail.gmail.com>
<CALKy-wp_d5Tzu2POai5gpe+EJUVGuOvN58aGu2WekBjkhNm8Gw@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Tue, 20 May 2014 16:22:27 -0400
Message-ID: <CAJHLa0Omi=fyE0S440dAqkzvZMKcfuOTrvoYwvxW+hO76CHogA@mail.gmail.com>
To: Andy Alness <andy@coinbase.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
-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: 1WmqYo-000052-0d
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
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: Tue, 20 May 2014 20:22:55 -0000
Indeed -- you must reinvent TCP over UDP, ultimately, to handle blocks
and large TXs.
On Tue, May 20, 2014 at 4:09 PM, Andy Alness <andy@coinbase.com> wrote:
> Awesome! I'm assuming this is it:
> https://bitcointalk.org/index.php?topic=3D156769.0
>
> It would be interesting (at least to me) to take this a step further
> and offer UDP as a full TCP replacement capable of STUN-assisted NAT
> traversal and possibly swarmed blockchain syncs. It would require open
> TCP nodes to facilitate "connection" establishment. It is obviously a
> non-trivial amount of work but would be an interesting experiment.
> Maybe BitTorrent's =C2=B5TP protocol could be leveraged.
>
> On Tue, May 20, 2014 at 12:17 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
>> Yes, i spec'd out the UDP traversal of the P2P protocol. It seems
>> reasonable especially for "inv" messages.
>>
>> On Tue, May 20, 2014 at 2:46 PM, Andy Alness <andy@coinbase.com> wrote:
>>> Has there ever been serious discussion on extending the protocol to
>>> support UDP transport? That would allow for NAT traversal and for many
>>> more people to run effective nodes. I'm also curious if it could be
>>> made improve block propagation time.
>>>
>>> On Tue, May 20, 2014 at 7:52 AM, Gmail <will.yager@gmail.com> wrote:
>>>> Unlikely. I doubt any significant portion of miners in china will cont=
inue to mine on a china-specific chain, since it will certainly be outmined=
by non-Chinese miners, and will be orphaned eventually.
>>>>
>>>> More likely is that mining interests in china will make special arrang=
ements to circumvent the GFwOC.
>>>>
>>>> Users who can't access the worldwide blockchain will notice horrendous=
ly slow confirmation times and other side effects.
>>>>
>>>>> On May 20, 2014, at 10:37, Eugen Leitl <eugen@leitl.org>
>>>>>
>>>>> Could a blockchain fork due to network split happen?
>>>>>
>>>>
>>>> ----------------------------------------------------------------------=
--------
>>>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>>>> Instantly run your Selenium tests across 300+ browser/OS combos.
>>>> Get unparalleled scalability from the best Selenium testing platform a=
vailable
>>>> Simple to use. Nothing to install. Get started now for free."
>>>> http://p.sf.net/sfu/SauceLabs
>>>> _______________________________________________
>>>> Bitcoin-development mailing list
>>>> Bitcoin-development@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>>
>>>
>>>
>>>
>>> --
>>> Andy Alness
>>> Software Engineer
>>> Coinbase
>>> San Francisco, CA
>>>
>>> -----------------------------------------------------------------------=
-------
>>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>>> Instantly run your Selenium tests across 300+ browser/OS combos.
>>> Get unparalleled scalability from the best Selenium testing platform av=
ailable
>>> Simple to use. Nothing to install. Get started now for free."
>>> http://p.sf.net/sfu/SauceLabs
>>> _______________________________________________
>>> Bitcoin-development mailing list
>>> Bitcoin-development@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>>
>> --
>> Jeff Garzik
>> Bitcoin core developer and open source evangelist
>> BitPay, Inc. https://bitpay.com/
>
>
>
> --
> Andy Alness
> Software Engineer
> Coinbase
> San Francisco, CA
--=20
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
