Daniel Cousens

@jordansexton if you want to complete these, I will happily merge them :+1:

I assume this is OK then?

> include/bitcoin.hpp:114:33: error: conversion to ‘size_t {aka unsigned int}’ from ‘long long unsigned int’ may alter its value [-Werror=conversion] This is a bit harder without a cast... I suspect I...

Hi @agoora, at this time there isn't a transform that solely deals with a UTXO set. You can acquire the required data using the [`leveldb`](https://github.com/dcousens/fast-dat-parser/blob/master/src/leveldb.hpp) transform, but, it has a...

> dump all hash160 with btc address ? The script transform migth be of interest to you: > 1 - Outputs every script prefixed with a uint16_t length

@agoora, I do not have the time to do this for you. There might be an option for such specific functionality at a later date, but at this time, you'll...

@agoora if you are referring to https://github.com/dcousens/fast-dat-parser/commit/600723a4008f58ef2c35649f57a99cdd97c16705, it isn't ready/tested yet, but certainly it may give you an idea of how you could do it.

Blocked by https://github.com/bitcoinjs/indexd/issues/26

The three options as I see them: * Ask `bitcoind` for the block@`height` (`getblock`), and our index maintains the transaction offset into that block * Easily cache-able... but probably? high...

If we maintain our own `txindex`, not only can we bundle it with https://github.com/bitcoinjs/indexd/issues/9 - but we can preserve the entire transaction for other analysis. @runn1ng the concern here is,...