summaryrefslogtreecommitdiff
path: root/cb/62eb7d0c568c7e1cc14ecef1e1ce57defebb18
blob: e1edfa61b17c9ab8c9bfb67acb58c72106c01c17 (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
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 <andy@coinbase.com>) id 1WmqMX-0002s3-1g
	for bitcoin-development@lists.sourceforge.net;
	Tue, 20 May 2014 20:10:13 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of coinbase.com
	designates 209.85.213.182 as permitted sender)
	client-ip=209.85.213.182; envelope-from=andy@coinbase.com;
	helo=mail-ig0-f182.google.com; 
Received: from mail-ig0-f182.google.com ([209.85.213.182])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WmqMH-00088i-03
	for bitcoin-development@lists.sourceforge.net;
	Tue, 20 May 2014 20:10:13 +0000
Received: by mail-ig0-f182.google.com with SMTP id uy17so1234527igb.3
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 20 May 2014 13:09:50 -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:date
	:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=Y/u/2y+cQZO5RiiSPVzqkfKEco4qwZcZAW7czwx6s1A=;
	b=VWD4s7NesyEd9hs0ZU+eDp6exdq7YmLikzElWfKu3yxsqoWhB8Fbfmz4zVM3me2kI/
	69Yzq++wyvVKXHa7wutSMuV0u9jnyg5mr3pEA/iM/58PLZdv5iBU845hAEeBJRIA5knu
	4axVg3JB4LQN2czFBJ5jTlR21slkkPsIpCndMvAbn2Pln6PDGL3S0Ic38d44751kH5HR
	1/foDkl5VtHgp+t87HMcv85sGmgWQzSlMHtCH42EN/ylIoVjHW/cwE6t0D8e2tlMhE3C
	+MClcxtyamcXqH7IdMUcGrayF7ebBmBw8yuXy9R7za65o/gxT5xP7Esxohd76USXsoM3
	srKg==
X-Gm-Message-State: ALoCoQmayq+9KRcUMZnMAyLt54T8YfZQ/GeXGafUFlQPlGWBmrHc1wLaRV/UMzxRunGpi3cIvelO
MIME-Version: 1.0
X-Received: by 10.50.253.163 with SMTP id ab3mr8108974igd.35.1400616590691;
	Tue, 20 May 2014 13:09:50 -0700 (PDT)
Received: by 10.42.39.3 with HTTP; Tue, 20 May 2014 13:09:50 -0700 (PDT)
In-Reply-To: <CAJHLa0PjUqJd_Hfjiwfj5c1yb6LJZeZMS0LFHd3Ncb+Ly88F8w@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>
Date: Tue, 20 May 2014 13:09:50 -0700
Message-ID: <CALKy-wp_d5Tzu2POai5gpe+EJUVGuOvN58aGu2WekBjkhNm8Gw@mail.gmail.com>
From: Andy Alness <andy@coinbase.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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
	0.0 TIME_LIMIT_EXCEEDED    Exceeded time limit / deadline
X-Headers-End: 1WmqMH-00088i-03
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:10:13 -0000

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 conti=
nue 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 arrange=
ments to circumvent the GFwOC.
>>>
>>> Users who can't access the worldwide blockchain will notice horrendousl=
y 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 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
>>>
>>
>>
>>
>> --
>> 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 ava=
ilable
>> 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/



--=20
Andy Alness
Software Engineer
Coinbase
San Francisco, CA