Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SbBct-0001Mn-HM for bitcoin-development@lists.sourceforge.net; Sun, 03 Jun 2012 14:17:51 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.175 as permitted sender) client-ip=209.85.212.175; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f175.google.com; Received: from mail-wi0-f175.google.com ([209.85.212.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1SbBcq-0002wt-PG for bitcoin-development@lists.sourceforge.net; Sun, 03 Jun 2012 14:17:51 +0000 Received: by wibhn6 with SMTP id hn6so1723093wib.10 for ; Sun, 03 Jun 2012 07:17:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.135.146 with SMTP id u18mr8579957wei.5.1338733062669; Sun, 03 Jun 2012 07:17:42 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.216.26.140 with HTTP; Sun, 3 Jun 2012 07:17:42 -0700 (PDT) In-Reply-To: <4FCA33EB.5030706@gmail.com> References: <4FCA33EB.5030706@gmail.com> Date: Sun, 3 Jun 2012 16:17:42 +0200 X-Google-Sender-Auth: xd-2Q2ddEjslUUxXKEXMUyorniY Message-ID: From: Mike Hearn To: Alan Reiner Content-Type: multipart/alternative; boundary=001636eeeb98a6464004c1921418 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 X-Headers-End: 1SbBcq-0002wt-PG Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Full Clients in the future - Blockchain management 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: Sun, 03 Jun 2012 14:17:51 -0000 --001636eeeb98a6464004c1921418 Content-Type: text/plain; charset=UTF-8 Yeah, for actually storing transactions the approach Satoshi uses of relying on a database engine makes sense and is what the code already does, so I'm not sure why this is a problem. The real problem with Satoshis code for scaling down to smaller devices (and one day desktops too) is the need to store all the chain headers in RAM. BitcoinJ avoids this but just creates more problems for itself in other places, partly because we also try to avoid a database engine (read/write traffic on phones can be insanely expensive, especially on older ones, and so sqlite is known to be a serious cause of performance pain on android apps). --001636eeeb98a6464004c1921418 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yeah, for actually storing transactions the approach Satoshi uses of relyin= g on a database engine makes sense and is what the code already does, so I&= #39;m not sure why this is a problem.

The real problem w= ith Satoshis code for scaling down to smaller devices (and one day desktops= too) is the need to store all the chain headers in RAM. BitcoinJ avoids th= is but just creates more problems for itself in other places, partly becaus= e we also try to avoid a database engine (read/write traffic on phones can = be insanely expensive, especially on older ones, and so sqlite is known to = be a serious cause of performance pain on android apps).
--001636eeeb98a6464004c1921418--