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
|
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 <mh.in.england@gmail.com>) id 1Ud3xk-0007Hs-Ts
for bitcoin-development@lists.sourceforge.net;
Thu, 16 May 2013 19:35:41 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.49 as permitted sender)
client-ip=209.85.219.49; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f49.google.com;
Received: from mail-oa0-f49.google.com ([209.85.219.49])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Ud3xf-0004l5-BW
for bitcoin-development@lists.sourceforge.net;
Thu, 16 May 2013 19:35:40 +0000
Received: by mail-oa0-f49.google.com with SMTP id k14so4294025oag.36
for <bitcoin-development@lists.sourceforge.net>;
Thu, 16 May 2013 12:35:30 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.40.65 with SMTP id v1mr22650858oek.124.1368732929920;
Thu, 16 May 2013 12:35:29 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.162.230 with HTTP; Thu, 16 May 2013 12:35:29 -0700 (PDT)
In-Reply-To: <20130516100206.82680@gmx.com>
References: <20130516100206.82680@gmx.com>
Date: Thu, 16 May 2013 12:35:29 -0700
X-Google-Sender-Auth: uMjykVbouDne2UA-GskjwJeJBQc
Message-ID: <CANEZrP0yHGP5ZRu3hX-Ox5rpRopDsYGBBNNxzDAsQK6keo1msg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: bitcoingrant@gmx.com
Content-Type: multipart/alternative; boundary=089e015367f614a5e004dcdaf886
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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
0.0 LOTS_OF_MONEY Huge... sums of money
X-Headers-End: 1Ud3xf-0004l5-BW
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Modularizing Bitcoin
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, 16 May 2013 19:35:41 -0000
--089e015367f614a5e004dcdaf886
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
I'm all for funding of Bitcoin development, but I suggest talking to Gavin
to find out what efforts would be the biggest win right now. I don't see
why separating wallet code from the main Bitcoin process would increase
node count, as the cost of running the node is almost all in keeping up
with transaction traffic and time spent in the wallet is likely to dominate
only for large merchants or exchanges.
That said, you can already do this today - just run an SPV wallet like
bitcoinj connected to your personal node. The wallet code in bitcoind won't
be used for anything.
There are lots of things that can be done, but the best way to approach
this is to get tightly written technical requirements from people in the
know, and then contract with developers. Bounty style development has the
risk of uncoordinated development that duplicates work and puts pressure on
Gavin or other maintainers to accept shoddy code due to the "first past the
post" winning criteria. Finding developers you trust and contracting with
them for well specified improvements minimises risk for everyone.
On Thu, May 16, 2013 at 3:02 AM, <bitcoingrant@gmx.com> wrote:
> One of the primary upcoming priorities for bitcoin=E2=80=99s infrastructu=
re,
> beyond the bloom filter, will be the continued modularization of the syst=
em.
>
> Here at the Bitcoin Grant, we would like to jump start this development
> with a financial incentive and initiate an ongoing conversation on how we
> can work together towards developing a smarter, more efficient system of
> tomorrow, today.
>
> Up for grabs: 500 bitcoins or $500,000; whichever is greater.
>
> Taking on a project of this scope is a highly intensive, technical
> undertaking and we believe excellent developers should be compensated as
> such, especially when it comes to open source projects.
>
> One of the main goals will be to separate the wallet from the node, as we
> have already done with mining. This way, the wallet, which will only hold
> private keys and create transactions, would pass transactions directly to=
a
> relay node, based on the bloom filter. Meanwhile, the block node will
> maintain the block chain and validate and relay new blocks.
>
> Such developments would significantly strengthen the system.
> Modularization would make cancer attacks less likely and increase the nod=
e
> count, which, currently, is fairly low.
>
> This is by no means is a feature request, merely ideas as to initiate a
> discussion. We welcome any feedback or suggestions. And of course, let us
> know if you would like to contribute to this project by submiting a grant
> proposal.
>
> http://bitcoingrant.org <http://bitcoingrant.org/&lang=3Den>
>
>
>
>
>
> -------------------------------------------------------------------------=
-----
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls
> from a single console and one unified framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--089e015367f614a5e004dcdaf886
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I'm all for funding of Bitcoin development, but I sugg=
est talking to Gavin to find out what efforts would be the biggest win righ=
t now. I don't see why separating wallet code from the main Bitcoin pro=
cess would increase node count, as the cost of running the node is almost a=
ll in keeping up with transaction traffic and time spent in the wallet is l=
ikely to dominate only for large merchants or exchanges.<div>
<br></div><div style>That said, you can already do this today - just run an=
SPV wallet like bitcoinj connected to your personal node. The wallet code =
in bitcoind won't be used for anything.</div><div style><br></div><div =
style>
There are lots of things that can be done, but the best way to approach thi=
s is to get tightly written technical requirements from people in the know,=
and then contract with developers. Bounty style development has the risk o=
f uncoordinated development that duplicates work and puts pressure on Gavin=
or other maintainers to accept shoddy code due to the "first past the=
post" winning criteria. Finding developers you trust and contracting =
with them for well specified improvements minimises risk for everyone.</div=
>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,=
May 16, 2013 at 3:02 AM, <span dir=3D"ltr"><<a href=3D"mailto:bitcoing=
rant@gmx.com" target=3D"_blank">bitcoingrant@gmx.com</a>></span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
<span style=3D"font-family:Verdana"><span style=3D"font-size:12px"><span st=
yle=3D"line-height:16px;font-size:11px;font-family:'Lucida Grande',=
Verdana,Arial,Helvetica,sans-serif">One of the primary upcoming priorities =
for bitcoin=E2=80=99s infrastructure, beyond the bloom filter, will be the =
continued modularization of the system.</span><p style=3D"padding-top:3px;m=
argin-bottom:5px;min-height:15px;padding:0px;outline:0px;padding-bottom:3px=
;vertical-align:baseline;line-height:16px;min-width:100%;font-size:11px;fon=
t-family:'Lucida Grande',Verdana,Arial,Helvetica,sans-serif;margin:=
0px;margin-top:5px;border:0px;background-image:none">
Here at the Bitcoin Grant, we would like to jump start this development wit=
h a financial incentive and initiate an ongoing conversation on how we can =
work together towards developing a smarter, more efficient system of tomorr=
ow, today.</p>
<p style=3D"padding-top:3px;margin-bottom:5px;min-height:15px;padding:0px;o=
utline:0px;padding-bottom:3px;vertical-align:baseline;line-height:16px;min-=
width:100%;font-size:11px;font-family:'Lucida Grande',Verdana,Arial=
,Helvetica,sans-serif;margin:0px;margin-top:5px;border:0px;background-image=
:none">
<span style=3D"margin:0px;padding:0px;border:0px;outline:0px;vertical-align=
:baseline;background-image:none">Up for grabs: 500 bitcoins or $500,000;=C2=
=A0whichever is greater.</span></p><p style=3D"padding-top:3px;margin-botto=
m:5px;min-height:15px;padding:0px;outline:0px;padding-bottom:3px;vertical-a=
lign:baseline;line-height:16px;min-width:100%;font-size:11px;font-family:&#=
39;Lucida Grande',Verdana,Arial,Helvetica,sans-serif;margin:0px;margin-=
top:5px;border:0px;background-image:none">
<span style=3D"margin:0px;padding:0px;border:0px;outline:0px;vertical-align=
:baseline;background-image:none">Taking on a project of this scope is a hig=
hly intensive, technical undertaking and we believe excellent developers sh=
ould be compensated as such, especially when it comes to open source projec=
ts.</span></p>
<p style=3D"padding-top:3px;margin-bottom:5px;min-height:15px;padding:0px;o=
utline:0px;padding-bottom:3px;vertical-align:baseline;line-height:16px;min-=
width:100%;font-size:11px;font-family:'Lucida Grande',Verdana,Arial=
,Helvetica,sans-serif;margin:0px;margin-top:5px;border:0px;background-image=
:none">
<span style=3D"margin:0px;padding:0px;border:0px;outline:0px;vertical-align=
:baseline;background-image:none">One of the main goals will be to separate =
the wallet from the node, as we have already done with mining. This way, th=
e wallet, which will only hold private keys and create transactions, would =
pass transactions directly to a relay node, based on the bloom filter. Mean=
while, the block node will maintain the block chain and validate and relay =
new blocks.</span></p>
<p style=3D"padding-top:3px;margin-bottom:5px;min-height:15px;padding:0px;o=
utline:0px;padding-bottom:3px;vertical-align:baseline;line-height:16px;min-=
width:100%;font-size:11px;font-family:'Lucida Grande',Verdana,Arial=
,Helvetica,sans-serif;margin:0px;margin-top:5px;border:0px;background-image=
:none">
<span style=3D"margin:0px;padding:0px;border:0px;outline:0px;vertical-align=
:baseline;background-image:none">Such developments would significantly stre=
ngthen the system. Modularization would make cancer attacks less likely and=
increase the node count, which, currently, is fairly low.</span></p>
<p style=3D"padding-top:3px;margin-bottom:5px;min-height:15px;padding:0px;o=
utline:0px;padding-bottom:3px;vertical-align:baseline;line-height:16px;min-=
width:100%;font-size:11px;font-family:'Lucida Grande',Verdana,Arial=
,Helvetica,sans-serif;margin:0px;margin-top:5px;border:0px;background-image=
:none">
<span style=3D"margin:0px;padding:0px;border:0px;outline:0px;vertical-align=
:baseline;background-image:none">This is by no means is a feature request, =
merely ideas as to initiate a discussion. We welcome any feedback or sugges=
tions.=C2=A0</span>And of course, let us know if you would like to contribu=
te to this project by submiting a grant proposal.</p>
<p style=3D"padding-top:3px;margin-bottom:5px;min-height:15px;padding:0px;o=
utline:0px;padding-bottom:3px;vertical-align:baseline;line-height:16px;min-=
width:100%;font-size:11px;font-family:'Lucida Grande',Verdana,Arial=
,Helvetica,sans-serif;margin:0px;margin-top:5px;border:0px;background-image=
:none">
<a href=3D"http://bitcoingrant.org/&lang=3Den" style=3D"margin:0px;padd=
ing:0px;border:0px;outline:0px;vertical-align:baseline;background-image:non=
e;text-decoration:none;color:rgb(149,0,0)" target=3D"_blank">http://bitcoin=
grant.org</a></p>
<p style=3D"margin:0px;padding:0px">=C2=A0</p><br><span><span style=3D"font=
-family:Verdana;font-size:12px">=C2=A0</span></span></span></span>
<br>-----------------------------------------------------------------------=
-------<br>
AlienVault Unified Security Management (USM) platform delivers complete<br>
security visibility with the essential security capabilities. Easily and<br=
>
efficiently configure, manage, and operate all of your security controls<br=
>
from a single console and one unified framework. Download a free trial.<br>
<a href=3D"http://p.sf.net/sfu/alienvault_d2d" target=3D"_blank">http://p.s=
f.net/sfu/alienvault_d2d</a><br>___________________________________________=
____<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>
--089e015367f614a5e004dcdaf886--
|
