I have noticed that the Address object in BlockSci cannot be pickled.
This results in users not being able to use the multiprocessing libraries which rely on pickling objects.
BlockSci exposes the map_blocks, mapreduce_txes and mapreduce_blocks functions that help us utilise multiple cores to processing the blockchain.
I'm wondering if I am missing something similar for Address objects, as I currently work with lists of Address objects (e.g. to chart the historical balances of an entity's addresses), but not being able to handle this task in a parallel manner has led to quite a slowdown in our research velocity.
This is somewhat related to #83. Thank you very much for your time and work on BlockSci.
I have noticed that the Address object in BlockSci cannot be pickled.
This results in users not being able to use the multiprocessing libraries which rely on pickling objects.
BlockSci exposes the
map_blocks,mapreduce_txesandmapreduce_blocksfunctions that help us utilise multiple cores to processing the blockchain.I'm wondering if I am missing something similar for Address objects, as I currently work with lists of Address objects (e.g. to chart the historical balances of an entity's addresses), but not being able to handle this task in a parallel manner has led to quite a slowdown in our research velocity.
This is somewhat related to #83. Thank you very much for your time and work on BlockSci.