pull down to refresh
226 sats \ 9 replies \ @optimism 11h \ on: Bitcoin Knots Synchronisation Lost bitcoin_beginners
This means that the chainstate could not be fully verified and is not specific to Knots. I've had this happen with Core on machines with:
- Bad RAM
- Bad disk
and it's really hard to reproduce for others. See also #1060416
If it happens again:
- Run memtest
- Inspect SMART reports for your disk
Let us know what it says if it comes this far - may make sense to do this regardless of whether the issue persists.
Speaking of #1060416, is there a hardware guide for running an efficient bitcoin node anywhere?
I built my node during the old days when a raspberry pi and a 1 TB external SSD was enough. But it seems like the resource pressure is higher now, but I don't understand much about hard drive specs like DRAM cache, or other specs that might help make running a node smoother.
reply
reply
Right now, nothing. It's supposed to be my main lightning node. I used to use it for a bit of routing (never profitable), and for broadcasting my own transactions from command line (a good educational experience). But ever since I wiped it and rebuilt it and it took a month to IBD, I lost interest a bit. Primarily just using Alby Desktop for now. Overall though, my goal of having this node would be to validate blocks myself, broadcast my own transactions, help the network, and run a more stable lightning node than my current Alby Desktop (which isn't always on.)
What a pity! It is a few month old machine with well above average hardware specs, and I am regularly running some heavy machine learning workload (training and inference with GPU) without any issue. So it's a surprise to know that Knots surfaces some deep hardware bug that nothing else I run has an issue with.
I am a fairly technical software guy, but debugging at hardware level (may be I can pull it off by some google searches and research) is not my cup of tea, mainly because of time than anything else. But I will try.
It may discourage many among us from running a node at all.
reply
reply
What are you using your node for?
I read that it in itself is a small contribution to the network, and also, when it synchronises, I plan to use it to broadcast my sparrow wallet transactions.
reply
Okay. The "contribution" thing really depends on how well your node runs, how good your uplink is, how much people sync off you, and so on. In general, small, slow nodes are a burden to the network, so make sure to keep learning how to help the network best.
For actually verifying your own blocks and posting your own transactions, it's of course a great use-case.
reply