Open tzarebczan opened 3 years ago
Sorry for the confusion, @tzarebczan! Because rosetta-bitcoin
stores all relevant data in its own indexer, we didn't at a mode to disable pruning because we didn't think anyone would want to keep a redundant copy of block data around.
If you want to disable pruning, you could:
1) Upstream a config option that disables the pruning
goroutine
2) Remove the pruning
goroutine in your fork
TL;DR...remove these 3 lines and it will work: https://github.com/coinbase/rosetta-bitcoin/blob/1b4c984e2d62c6c3bebc35d9810cf7963eef04e1/main.go#L107-L109
@sidhujag asked about making this repo more generic so it is easier to use with bitcoin-core forks. Would that be something interesting to you? https://github.com/coinbase/rosetta-bitcoin/pull/50#discussion_r535495927
@sidhujag asked about making this repo more generic so it is easier to use with bitcoin-core forks. Would that be something interesting to you? #50 (comment)
I started to look at it but found a bunch of places that rely on genesis or network settings so I left it alone thinking you are probably better to do it @patrick-ogrady but I think it would be ideal. For us just the performance badger settings need to be set to be able to sync the rest is consistent (jsonify network and badger settings)
I started to look at it but found a bunch of places that rely on genesis or network settings so I left it alone thinking you are probably better to do it @patrick-ogrady but I think it would be ideal.
👍
For us just the performance badger settings need to be set to be able to sync the rest is consistent (jsonify network and badger settings)
Yep, makes sense to me!
Indexer was still running, but full node was shutdown