@Obionecoinobi Research - I track node performance changes over time to see how the cost of node operation is trending.
@itsLIRAN Around 7 hours if you force checking of all historical transaction signatures. Half that if you use the d… https://t.co/PxHJNBcRQo
@yashar_rashedi NVME drive, pruning old states to reduce disk space. https://t.co/BcSRZBskN3
@PeterMcCormack 1) Number go up!
2) When in doubt, zoom out! pic.twitter.com/sKBdYRkkJX
So if I’m reading this right, 5 mining pools with 35% of the BCH hashpower are threatening to orphan blocks from th… https://t.co/OZsGKcy39W
@chrislockwood_ All of the above!
The OG-ness of a Bitcoiner ought not be measured by the coins they have, but by the coins they have lost.
@JustDoingItBig Yeah and in the debug logs it seemed to be continuously looping through trying to connect to various peers.
It appears that new Parity Ethereum nodes won’t do a full sync thanks to a stale bootnode list and incompatibility… https://t.co/g3Ag0mD5yj
@djhfhasfdshy @god_of_bitcoin My geth config:
[Eth]
NetworkId = 1
SyncMode = “full”
NoPruning = false
DatabaseCache = 26000
@omgbtc Yes, I skip doing any “warp” syncing or “snapshot” syncing - it downloads and verifies every block.
@stochasms If you try to sync on a machine with a spinning disk you’re gonna have a bad time. My machine is pretty high end.
It took my benchmark machine 5 days 15 hours to full sync Geth 1.99 to block 9,330,000. It performed over 6 TB of d… https://t.co/RC1f8LzwSv