pull down to refresh

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.
It may discourage many among us from running a node at all.
What are you using your node for?
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
with well above average hardware specs
posts specs pls
reply