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 <marko.otbalkana@gmail.com>) id 1UkOSC-0005Pn-He for bitcoin-development@lists.sourceforge.net; Thu, 06 Jun 2013 00:53:24 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.193 as permitted sender) client-ip=209.85.217.193; envelope-from=marko.otbalkana@gmail.com; helo=mail-lb0-f193.google.com; Received: from mail-lb0-f193.google.com ([209.85.217.193]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UkOSB-0001F3-Pb for bitcoin-development@lists.sourceforge.net; Thu, 06 Jun 2013 00:53:24 +0000 Received: by mail-lb0-f193.google.com with SMTP id z5so546347lbh.4 for <bitcoin-development@lists.sourceforge.net>; Wed, 05 Jun 2013 17:53:17 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.142.73 with SMTP id ru9mr16142813lbb.22.1370479997003; Wed, 05 Jun 2013 17:53:17 -0700 (PDT) Received: by 10.114.161.198 with HTTP; Wed, 5 Jun 2013 17:53:16 -0700 (PDT) Date: Wed, 5 Jun 2013 17:53:16 -0700 Message-ID: <CALG7eYpKj9Ev2a1PZ7qsiqsazS4pHTPiGF22r64=s1buWm2aLQ@mail.gmail.com> From: Marko Otbalkana <marko.otbalkana@gmail.com> To: bitcoin-development@lists.sourceforge.net Content-Type: multipart/alternative; boundary=001a11c36c7a64acc504de71bd66 X-Spam-Score: -0.6 (/) 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 (marko.otbalkana[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1UkOSB-0001F3-Pb Subject: [Bitcoin-development] Blockchain alternative storage 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, 06 Jun 2013 00:53:24 -0000 --001a11c36c7a64acc504de71bd66 Content-Type: text/plain; charset=ISO-8859-1 Could anyone point me to work/project(s) related to storing the block chain in a database, like PostgreSQL, MySQL? How about any tools that can read the block chain from the Satoshi client and convert it into different formats? Thanks, -Marko --001a11c36c7a64acc504de71bd66 Content-Type: text/html; charset=ISO-8859-1 <div dir="ltr"><div><div>Could anyone point me to work/project(s) related to storing the block chain in a database, like PostgreSQL, MySQL? How about any tools that can read the block chain from the Satoshi client and convert it into different formats?<br> <br></div>Thanks,<br></div>-Marko<br></div> --001a11c36c7a64acc504de71bd66--