I sometimes get asked how to configure bitcoin core for mining, and whilst you can go mad with custom patches, there are some basic rules anyone can apply. Here are a quick set of basic bitcoin mining node optimisations that come to mind for mining: Use a dedicated node that is only doing mining and no other node tasks - use a separate node on a different machine for other duties. Do not run more than one bitcoind on the same machine. Run your node on fast hardware - CPU architecture and raw clock speed matter MUCH more than total CPUs as there is a lot of serialised code. A high clock speed i5 with few cores is better than a lower clock speed i7 with many cores. Have plenty of ram, ideally 32GB, and set dbcache to 12GB so it can contain the full UTXO set in time. Leave your node running permanently - each time you restart it, it will be very slow and get progressively quicker on subsequent block changes. Don't be afraid to prune a node if your drive is more than half full and it's being used purely for mining. Filesystems inherently slow down once they are more than 70% full, and provided a pruned node remains in sync it offers zero disadvantage in mining. Use an SSD. A pruned node on an SSD is infinitely better than a full node on a spinning drive. Don't increase the number of connections - this will increase mutex contention in the code. Don't connect it via wifi. Use ethernet where possible, and preferably a wired connection to the internet, though starlink is not too bad. Don't enable transaction indexing. This serves no purpose in mining. Do not use blocksonly mode or your node will be slow to confirm and rebuild new blocks. Build your own bitcoind from scratch for your hardware which will enable CPU optimisations specific to it.