Daniel Cousens

@unsystemizer exactly

@unsystemizer the issue with a local transaction index, is that we can't index into the `.dat` files themselves, as they may be in an indeterminate state (as `bitcoind` updates them)....

Another alternative is if we could ask network peers for the blocks on the initial sync... then continue as normal with our pruned node. We don't want to ask random...

In the mean time, `indexd` could use the `pruneblockchain` RPC command to signal where it is up to `-prune=1` (aka, manual RPC pruning only), then we could allow `indexd` to...

@theuni yes it would. Thanks for pointing that issue out.

@KryptoNova the blockchain contains blocks, which each have transactions, which each have inputs and outputs. Each output has a script (the output script) which is typically (but not always) of...

@KryptoNova apologies, I thought this was question was for another project. > Is the data structure in indexd able to perform this type of query against the blockchain? `indexd` has...

@uniphonic what is the new error?

> @dcousens I noticed you had some concerns with pull #39, and I'm guessing you might have the same concerns here, since additional .so files are being added, in addition...

@Gp2mv3 try disabling `Bitcode` in your compilation options.