What is Nostr?
hh / HH
npub1s27…dsym
2024-09-09 17:18:35

hh on Nostr: FYI if you're thinking about running your own Bitcoin Core node, as of today, the ...

FYI if you're thinking about running your own Bitcoin Core node, as of today, the full datadir is taking up 760.5 GB of space on an SSD.

I would have sworn it was like 600 not that long ago, just earlier this year. (I may be wrong).

Also, on Ubuntu, do whatever you must to avoid installing this MF through Snap. It fucks up all the names, paths, directories and commands. It's just not worth it and now that I have successfully synched the blockchain in full, I'm going to nuke it and reinstall it properly.

I don't understand how Bitcoin.org puts that Snap shit out there as a legit option, if after that ZERO of the documents and help cover its many specifics at all. Even on forums and other internet sources, it's very rare to find any references at all.


More bitcoin node self-hosting pain #AskNostr

Spoke too early... I ran Bitcoin Core QT, and all's good. I even set up Sparrow, Wasabi, Bisq, etc. and they all hook up to locally on the right port it and work fine. I have rebooted the system several times and nothing gets fucked in the process, so I'm happy.

Problem is, first, for some reason despite having selected the option on the GUI, this thing just won't run on startup. I have to manually open it every time. Annoying.

Anyway, now I'm trying to run this thing as a service to see if I can set up Electrum and eventually Mempool, and it's a hot mess.

First, after much figuring out just how to even run any of this on Terminal, because for some reason all the commands are different (I guess Snap's fault?), I can manually start "bitcoin-core.daemon", which shows up as "bitcoind" in the process list, so nice.

Problem is, it has ignored the previously set data and block folders and it seems to have begun a separate initial download, because I found the corresponding folders and files (including 25 Gb of blocks already) on my internal disk.

If I start QT as usual, it's using the correct ones, no new synch required.

I am now paralyzed scared shitless that if I point the daemon to the correct folders that qt is using, it will nuke them and restart the excruciating initial download again...

nevent1q…7zc5
Author Public Key
npub1s277u5rww60te98w9umz6p7pjcxuus96cegdsf4y978qcqvu8jtq88dsym