but it *is* possible on any hardware, unlike some "decentralized" networks out there

only "2022-04-15 03:32:19.241 I Synced 2598032/2602170 (99%, 4138 left" for my 5400 rpm!

Ahhh. That makes a lot of sense. I'm syncing to a spinning disk.

yeah. its crazy to think, but spinny disks are old tech.

gingeropolous: Yep, 100% My system boots off an SSD, but it's too small to hold the blockchain. Most of my stuff is stored on a bunch of spinning disks.

I'll need to get a bigger SSD for this sort of tinkering.

It's still super odd that these errors come and go. I'll bet it's from some weird activity on the network.

Ha! Dropped an old SSD into my box: `Downloading at 2871 kB/s`

You're not kidding, it's an order of magnitude faster now.

It went from 85.6 -> 85.9 over the last few mins.

It's several orders of magnitude faster.

DANG. This thing is doing 10s 1000s of tps to the device.

Welp, you guys were right, it's almost but not quite unusable on a spinning disk since it needs an insane number of IOs during initial sync.

I wonder if it would be better if you could chose a log based update scheme that would cause the file to grow very large, then you could shrink it down with a rewrite after.

It's not about the file growing, it's because every new block that you verify requires verifiying every single transaction in it - and every single transaction requires checking that each ring member on the input side exists in the chain. So for every single input in every single transaction in every single block, it has to go back and search the chain to make sure it exists

gah, it was a 7200 rpm this whole time

well the T61 synchronized

is anything cheaper than github.com/comit-network/xmr-btc-swap  to have cash from monero

firefox crashed