4 ms·
The author mentions being plagued by crashes/corruption, but I've never experienced this and I've been running a full node for a few years. Other than the large
by therealidiot 10y ago
The author mentions being plagued by crashes/corruption, but I've never experienced this and I've been running a full node for a few years. Other than the large (well, not _that_ large) storage requirements (.bitcoin is currently 101G) I've not got any complaints...
Unless there's a bug in a recent version of bitcoind which causes it to crap out when initially catching up with the network?
- jstanley 10y agoI've been informed that crashes+corruption indicate either lack of memory or hardware faults. Bitcoin needs to do an awful lot of cryptography, and it all needs to come out perfectly for it to work, so it tends to be sensitive to hardware faults.
- Senji 10y agoIf you're doing bitcoin crypto on a machine without ECC RAM, you're a madman.
- aphextron 10y ago> Other than the large (well, not _that_ large) storage requirements (.bitcoin is currently 101G) This has always been my complaint with bitcoin. Will the block chain download just keep getting larger and larger? Setting up a full node takes forever because of that. Is there any possible way to improve this?