Keep us updated!

I synced a full node over tor with a much worse connection bandwidth + over wifi into 2.5 days. Hardware was an Odroid M1, bought for less than 120 bucks.

About 30 minutes in, Mr. Overkill has entered Bitcoin’s 6th year of existence!

However, since November 2013 the ETA has increased to 10 hours!

After 1 hour of syncing, Mr. Overkill has entered the year 2016.

I can almost hear Mike Hearn ragequitting!

But I must confess that I’ve made a stupid mistake and didn’t set power options correctly: Mr. Overkill went to sleep for about 10 minutes while I was in another room 😅

2 hours later, Mr. Overkill is in August 2017 – with an approximate ETA of 7 hours.

Up to this point, Core was in default mode (db cache of 450 MiB, 0 script verification threads).

Now I’ll boost the db cache to 9999 MiB + I’ll give it 12 script verification threads 💪🏻

5 hours later, Mr. Overkill is in March 2022 💪🏻

13 years of Bitcoin history, synced in just one evening 😍

Let’s see how long it takes to sync the last 2 years, when the blocks have become bigger and fuller 🟩

6 hours later, Mr. Overkill started validating the ordinal inscriptions.

Does anyone want to bet how long it’s going to take to complete the last year of Bitcoin transactions?

The ETA is 90 minutes, which would make a total sync time of 7 1/2 hours!

7 hours later, Mr. Overkill entered the year 2024 and estimates it would complete the sync in only 22 minutes 😍

The ordinal inscriptions of 2023 didn’t cause the expected slowdown 💪🏻

I wonder what happens when it runs into Runes?

The last month of transactions/blocks carries about 2% of the blockchain size.

Pretty crazy! (but nothing Mr. Overkill can’t handle)

Final sync time: 7 hours, 40 minutes.

I expected a slowdown around halving time (4/20), but Mr. Overkill just ate up those blocks and completed the task without any hiccups 💪🏻

I can probably optimize for 7 hours or 6:30 hours if I allocate more RAM and processing threads from the get-go, but so far I’m happy with the result!