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
|
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 <zellfaze@yahoo.com>) id 1SOwoB-0007r3-Sl
for bitcoin-development@lists.sourceforge.net;
Mon, 30 Apr 2012 20:02:55 +0000
X-ACL-Warn:
Received: from nm1-vm3.bullet.mail.ne1.yahoo.com ([98.138.91.131])
by sog-mx-4.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1SOwo9-00056H-2m for bitcoin-development@lists.sourceforge.net;
Mon, 30 Apr 2012 20:02:55 +0000
Received: from [98.138.90.49] by nm1.bullet.mail.ne1.yahoo.com with NNFMP;
30 Apr 2012 20:02:47 -0000
Received: from [98.138.88.233] by tm2.bullet.mail.ne1.yahoo.com with NNFMP;
30 Apr 2012 20:02:47 -0000
Received: from [127.0.0.1] by omp1033.mail.ne1.yahoo.com with NNFMP;
30 Apr 2012 20:02:47 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 385662.43064.bm@omp1033.mail.ne1.yahoo.com
Received: (qmail 93531 invoked by uid 60001); 30 Apr 2012 20:02:47 -0000
X-YMail-OSG: xTPCBAAVM1k5gi1mQCV6_wzlLryM2T6gbiJRxlf4tU3lCgb
er_WwgIRYZcruKyCYb8BQnfkxYQtlJblnhX_fdbHf1LNaiWUqAgaj3Hu1G_N
PFAt4chp2q65oclme3OaT1qP.MrGyTuOUdylv7hS6bUHuE0952iC.usNXwRV
A_ozMh934Imv46Bmb.9_xhoP2PHzOswPdQhj93ANlcHKP9DJVEw8YUs.GZ07
QuQhSoL1L7es3QWMsCqYU1zRxJmFsaltY7Om9FKqbS0T5L.A8QvdHm6sXEo9
5VD_CV0gGRfB29SWDcWJD2BSMl9uiIvNb7uOdDcagHFTx7xRZxg1UuRTsYIU
xO.yY14FCtBgKP8473fOp8RZq8iFsMk6bd0vS1RIkWP2STaYKlceGCRJ8ulN
04uFtSvpvxaxLFHXa2UBXNACpheQZvcR3GeRCZbjs2HGzmdLeQ7TOCR_GYBN
4Dsn3aAVg3w8gC3IheEMetaLRJyt1eyK2cObAsmyyVtn757aZYTDu00wD1vH
U.aTktf57zSvj3FTJeNoeLvgwIAFh4xGO1mmzBeC6s_32LFLVi7L5VrqMyXy
Za2gjrhW8ZyV0VHh_y2Nsat7FLbHQWR7JreveIolK5vOx09BKdXMbwEsmQf4
aAEc24Mn.t6lC9DynBW9GP1qoLNMVaeWHvCeOcyAwT7mxHbVvkGxA5rXopKG
PPJooR0TTtyq8baZ4FKMmn3Z1o1hk1X26zoZFuAVBubkOMdOvBba_IRvv.pz
gaHz3Hg--
Received: from [65.242.81.226] by web120904.mail.ne1.yahoo.com via HTTP;
Mon, 30 Apr 2012 13:02:47 PDT
X-Mailer: YahooMailClassic/15.0.6 YahooMailWebService/0.8.118.349524
Message-ID: <1335816167.89493.YahooMailClassic@web120904.mail.ne1.yahoo.com>
Date: Mon, 30 Apr 2012 13:02:47 -0700 (PDT)
From: Zell Faze <zellfaze@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <1335813078.98321.YahooMailNeo@web121004.mail.ne1.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.1 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.138.91.131 listed in list.dnswl.org]
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(zellfaze[at]yahoo.com)
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-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: 1SOwo9-00056H-2m
Subject: Re: [Bitcoin-development] BIP to improve the availability of blocks
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, 30 Apr 2012 20:02:56 -0000
Although quite true, I actually agree though that there should be some sort=
of checksum for the blocks. Bandwidth may not be a bottleneck now (or eve=
r), but it may be at some point. This change will help Bitcoin scale.=0A=
=0A------------------------=0A"It stopped being just a website a long time =
ago. For many of us, most of us, Wikipedia has become an indispensable part=
of our daily lives."=0A=E2=80=94 Jimmy Wales, Founder of Wikipedia =0AHelp=
protect it now. Please make a donation today: http://www.wikimediafoundati=
on.org/wiki/Donate=0A=0A=0A=0A--- On Mon, 4/30/12, Amir Taaki <zgenjix@yaho=
o.com> wrote:=0A=0A> From: Amir Taaki <zgenjix@yahoo.com>=0A> Subject: Re: =
[Bitcoin-development] BIP to improve the availability of blocks=0A> To: "bi=
tcoin-development@lists.sourceforge.net" <bitcoin-development@lists.sourcef=
orge.net>=0A> Date: Monday, April 30, 2012, 3:11 PM=0A> This is optimisatio=
n where it isn't=0A> needed. Bandwidth is not the bottleneck of the Bitcoin=
=0A> system. It is the immense time needed to validate the=0A> blockchain.=
=0A> =0A> And clients should never send blocks first. They always send=0A> =
an inv packet, then you request the block. It is a=0A> disruptive change an=
d brings little.=0A> =0A> We don't need to optimise every aspect of Bitcoin=
:) Just=0A> focus on the big bits that matter, while keeping everything=0A=
> working with minimal changes.=0A> =0A> For instance say we did this and t=
o maintain backwards=0A> compatible, we introduced a new message called "ha=
sh+block".=0A> Now there are 2 code branches that must be maintained -=0A> =
urgh.=0A> =0A> =0A> ________________________________=0A> From: Wladimir <la=
anwj@gmail.com>=0A> To: Rebroad (sourceforge) <rebroad+sourceforge.net@gmai=
l.com>=0A> =0A> Cc: bitcoin-development@lists.sourceforge.net=0A> =0A> Sent=
: Monday, April 30, 2012 7:26 PM=0A> Subject: Re: [Bitcoin-development] BIP=
to improve the=0A> availability of blocks=0A> =0A> =0A> On Mon, Apr 30, 20=
12 at 6:40 PM, Rebroad (sourceforge)=0A> <rebroad+sourceforge.net@gmail.com=
>=0A> wrote: =0A> =0A> =0A> >My proposal is that in addition to the size (w=
hich is=0A> advertised in=0A> >the header), the hash is also advertised in =
the header=0A> (of a block).=0A> >This would help nodes to determine whethe=
r they wanted=0A> to reject the=0A> >download. (e.g. if it already had a bl=
ock matching that=0A> hash). This of=0A> >course wouldn't prevent a rogue n=
ode from sending an=0A> incorrect hash,=0A> >but this would aid in saving b=
andwidth amongst behaving=0A> nodes.=0A> >=0A> =0A> I suppose it would make=
sense for clients to be able to=0A> reject blocks that they already have, =
if that's not=0A> currently possible.=0A> =0A> =0A> The other part of the p=
roposal is to allow nodes to request=0A> upload and=0A> >download blocks th=
at have already been partially=0A> downloaded.=0A> >=0A> >This could be don=
e by modifying the existing methods of=0A> upload,=0A> >download, or by add=
ing a new method, perhaps even using=0A> HTTP/HTTPS or=0A> >something simil=
ar. This would also help nodes to obtain=0A> the blockchain=0A> >who have r=
estrictive ISPs, especially if they are being=0A> served on port=0A> >80 or=
443. This could perhaps also allow web caches to=0A> keep caches of=0A> >t=
he blockchain, thereby making it also more available=0A> also.=0A> >=0A> =
=0A> You don't need a BIP if you want to somehow fetch the=0A> (initial) bl=
ock chain =0A> outside the bitcoin protocol. You could download it from=0A>=
some http =0A> server or even pass it along on an USB stick. Then with a=
=0A> simple client change you can import it: https://github.com/bitcoin/bit=
coin/pull/883 .=0A> =0A> =0A> Currently, without this=C2=A0functionality, n=
odes with=0A> restrictive (or=0A> >slow) internet have some options, such a=
s going via a=0A> tor proxy, but=0A> >due to the latency, the problem with =
multiple receptions=0A> of the same=0A> >block still occur.=0A> >=0A> =0A> =
If you're behind such a slow internet connection, and=0A> concerned about =
=0A> every bit of bandwidth, it is better to run a lightweight=0A> node. Fo=
r example, Electrum.=0A> =0A> Even if you could reduce the wasted bandwidth=
a bit by=0A> puzzling =0A> around with partial blocks, the download will s=
till be=0A> substantial (and that's going to get worse before it gets=0A> b=
etter). =0A> =0A> Wladimir=0A> =0A> =0A> ----------------------------------=
--------------------------------------------=0A> Live Security Virtual Conf=
erence=0A> Exclusive live event will cover all the ways today's=0A> securit=
y and =0A> threat landscape has changed and how IT managers can=0A> respond=
. Discussions =0A> will include endpoint security, mobile security and the=
=0A> latest in malware =0A> threats. http://www.accelacomm.com/jaw/sfrnl042=
42012/114/50122263/=0A> _______________________________________________=0A>=
Bitcoin-development mailing list=0A> Bitcoin-development@lists.sourceforge=
.net=0A> https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
=0A> =0A> -----------------------------------------------------------------=
-------------=0A> Live Security Virtual Conference=0A> Exclusive live event=
will cover all the ways today's=0A> security and =0A> threat landscape has=
changed and how IT managers can=0A> respond. Discussions =0A> will include=
endpoint security, mobile security and the=0A> latest in malware =0A> thre=
ats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/=0A> ________=
_______________________________________=0A> Bitcoin-development mailing lis=
t=0A> Bitcoin-development@lists.sourceforge.net=0A> https://lists.sourcefor=
ge.net/lists/listinfo/bitcoin-development=0A>
|
