Mehran

The same issue exists here and the simple workaround for me was to directly send JSON-RPC calls to the web server started by `bitcoind` and then do some parsing for...

> This issue should be fixed in the latest version https://github.com/blockchain-etl/bitcoin-etl/pull/57/files I'm using the latest version committed here and get the same output yet: https://github.com/blockchain-etl/bitcoin-etl/commit/77f1b469c46fa803a74963ff814154a0199cfe57

> 410400d0ade32217e076945e0946ef7bed72d9aea035aa8891e4bf0749ae6e24f8a7d3ea56efafe472ac3943dbed3af7c093729720ac9ab04e8eba09286e3a00fe41ac How to reproduce the bug: `export_blocks_and_transactions --provider-uri http://user:pass@bitcoind:8332 --chain bitcoin --start-block 119965 --end-block 119965 --blocks-output output/blocks.json --transactions-output output/transactions.json` Output Log: ` {"hash": "d70ae1131d433b655d0faeae1db4efa15bb4138f1e38e60a53073a58ea1dcc34", "size": 135, "virtual_size": 135, "version":...

I've encountered the same issue: `stream --provider-uri http://user:pass@bitcoind:8332 --chain bitcoin --last-synced-block-file config/last_synced_block.txt --period-seconds 30 --batch-size 40 --block-batch-size 120 --max-workers 20 --output path_to_dir` However using the default values, I see no...

I'm interested in implementing such feature. So, if it's desired, I can make a PR. I was thinking of something similar to this I've posted [here](https://github.com/blockchain-etl/bitcoin-etl/issues/55#issuecomment-1013669048).