Malte Möser

Would be nice to have some kind of version number attached to parsings to be able to notify the user when changes to the parser are not backwards-compatible (and also...

Potential optimizations of the parser/AMI to make it safer to work with the parser - [ ] Allow to interrupt parser - [ ] Parser schedule: setting parser to run...

Fixes one of the problems in #412.

fix: parse full chain index when maxBlockNum=0

1

Makes behavior consistent with the disk-based parser, i.e. to parse the full chain up to the maximum height when setting `maxBlockNum` to `0`

WITNESS_UNKNOWN and NONSTANDARD scripts don't appear in testchain

1

Our synthetic testchain does not contain scripts of type `WITNESS_UNKNOWN` and `NONSTANDARD`.

If we switch to C++ 17, we probably can get rid of some of the external dependencies: - [ ] wjakob/filesystem - [ ] mpark/variant - [ ] ranges::optional (still...

RocksDB provides [bloom filters](https://github.com/facebook/rocksdb/wiki/RocksDB-Bloom-Filter) which we could use instead of our own implementation.

`chain.address_from_index(num, type)` crashes the Jupyter kernel when called with `num > chain.address_count(type)`. It should return None/an error instead. TODO: check behavior for transactions

The parser currently parses all input scripts. This may not be necessary if the script has already been revealed.

Move mempool data out of parser directory

4

- [ ] Move mempool data outside of the parser data directory to prevent accidental deletion when reparsing the chain. - [ ] Add instructions on re-parsing to the FAQ/documentation