Troubleshooting

Frequently asked questions (FAQ)

We maintain a list of answers to Frequently Asked Questions on GitHub. Please make sure to check these first.

Technical and practical questions

If you’ve encountered an issue or have a question about using BlockSci not answered in the FAQ, the best way to find help is to search for similar issues in our GitHub issue tracker, or open a new issue.

As of November 2020, we are no longer actively developing or supporting BlockSci.

Cryptocurrency support and data correctness

We are not able to keep track of the development of the various blockchains that BlockSci can potentially support. When cryptocurrencies implement new features (e.g., script types, signature schemes), there’s a possibility that it breaks BlockSci in unexpected ways or requires updates to the code base (e.g., the parsing logic). We therefore strongly recommend that you put procedures in place that may help detect issues with data validity and correctness, such as comparing transaction and address data against blockchain explorers.

Known limitations

• Iterating over an AddressIterator in Python will produce a segfault or implausible results (this includes casting it to a list using list(iterator)). Use .to_list() to retrieve a list of the results over which you can iterate.

• Slicing a ClusterRange will produce a segfault or implausible results.

Parser diagnostics

The parser includes a diagnostic tool that allows to check for common issues with its setup.

blocksci_parser <path/to/config.json> doctor