micahriggan

@loicbellez could you email me your ETH address and we'll figure out what's going on? [email protected]

From what I remember, the disk write speed is usually the limiting factor. Your mongodb should be saturated with as many write operations as it can handle. Depending on your...

Ah that sounds like something is messed up. It should be pushing in the megabytes You don't need txindex because it syncs the blocks directly, and indexes the txs in...

@giaki3003 is your BTC node in regtest mode correctly? The icon is blue right? You may need ``` [regtest] port=12345 rpcport=12234 rpcuser=test rpcpassword=test ``` The bitcoin.conf file format has changed...

Hi Daniel! Thanks for checking out the v8 branch. It's still a work in progress, but it should definitely be able to connect to ABC. Do you mind sharing your...

Try dropping your state collection in bitcore-node if you're having issues with it picking back up. Theres an entry in there that tracks which process is syncing, and it expires...

Have you experimented with changing the maxPoolSize? If you're finding your database write speed isn't being used fully, you may be able to adjust that config value higher. ``` "maxPoolSize":...

@kruisdraad I've done a few experiments with in-memory sync, and flushing to the database after it reaches an update threshold. It does improve the speed a little bit. I never...

@kruisdraad My system looks like this, and I've got mongo running on the same host as bitcore-node ``` Processor Name: Intel Core i9 Processor Speed: 2.9 GHz Number of Processors:...

@kruisdraad Can you make the following change to the bitcoin p2p module, and then run in debug mode with `npm run debug` ``` diff --git a/packages/bitcore-node/src/modules/bitcoin/p2p.ts b/packages/bitcore-node/src/modules/bitcoin/p2p.ts index e7ad4a574..a671a8cb4 100644...