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 ) 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 ; 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: From: Mike Hearn 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 Subject: Re: [Bitcoin-development] Modularizing Bitcoin X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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, 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 > > > > > > -------------------------------------------------------------------------= ----- > 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
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.

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 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.


On Thu,= May 16, 2013 at 3:02 AM, <bitcoingrant@gmx.com> wrote:<= br>
One of the primary upcoming priorities = for bitcoin=E2=80=99s infrastructure, beyond the bloom filter, will be the = continued modularization of the system.

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.

Up for grabs: 500 bitcoins or $500,000;=C2= =A0whichever is greater.

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.

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.

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.

This is by no means is a feature request, = merely ideas as to initiate a discussion. We welcome any feedback or sugges= tions.=C2=A0And of course, let us know if you would like to contribu= te to this project by submiting a grant proposal.

http://bitcoin= grant.org

=C2=A0


=C2=A0
-----------------------------------------------------------------------= -------
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.s= f.net/sfu/alienvault_d2d
___________________________________________= ____
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--089e015367f614a5e004dcdaf886--