 |
September 18, 2011, 06:54:31 PM |
|
So I haven't worked much with SQL other than the fact that I know SQLite is pretty convenient in python, and I can read the blockchain from python -- so I should be able to figure out how to put the two together. If you write out explicitly what you want the database/tables to look like, and toss me a couple BTC (upon delivery) I should be able to produce a .sqlite file for you.
For instance, I assume you want two tables, one of block headers, one of transactions. The headers table would have all the core information in it (hashes, difficulty, nonce, etc). The transaction table would have the header hash, but be a little more complicated since each transaction actually has a variable list of inputs and outputs. I suppose you could go a step further and add a table of TxIn objects and a table of TxOut objects, each of which contain the parent Tx hash.
If it's not too intense, I can probably figure it out. I already have most of the tools made to do it, I just gotta learn the python-sqlite interface (is simply including hashes of the parent objects enough to consider the DB "relational?")
-Eto
|
