From: Mike Hearn <mike@plan99•net>
To: Alan Reiner <etotheipi@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Full Clients in the future - Blockchain management
Date: Sun, 3 Jun 2012 16:17:42 +0200 [thread overview]
Message-ID: <CANEZrP2sDD0MhO5xHB==N-oCtChXJwDBa79X07MENFa_ZjqpFQ@mail.gmail.com> (raw)
In-Reply-To: <4FCA33EB.5030706@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
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).
[-- Attachment #2: Type: text/html, Size: 664 bytes --]
prev parent reply other threads:[~2012-06-03 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 15:40 Alan Reiner
2012-06-03 14:17 ` Mike Hearn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANEZrP2sDD0MhO5xHB==N-oCtChXJwDBa79X07MENFa_ZjqpFQ@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=etotheipi@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox