pull down to refresh

0 sats \ 2 replies \ @SimpleStacker OP 12 May \ parent \ on: Observations on initial block download and fullnode requirements, 2022 to 2025 bitcoin
Thanks! Glad to hear someone is working on IBD optimization.
I have dbcache=4000, and my HD speed testing with hdparm was something like 250 MB/s... which I think is supposed to be ok?
Haven't tried dbbatchsize or assumevalid yet
write
preview
5 sats \ 1 reply \ @anon 14 May
Forgot to ask: are you doing IBD over TOR? That's notoriously slow (I'm really proud of the "no-tor-io" pun here)
reply
0 sats \ 0 replies \ @SimpleStacker OP 14 May
Tor is enabled, but I thought it can download via both clearnet and Tor.
Here are my bitcoin.conf settings. Let me know if there's anything I should change:
# RaspiBolt: bitcoind configuration
# /home/bitcoin/.bitcoin/bitcoin.conf

# Bitcoin daemon
server=1
txindex=1

# Allow creation of legacy wallets (required for JoinMarket)
deprecatedrpc=create_bdb

# Network
listen=1
listenonion=1
proxy=127.0.0.1:9050
bind=127.0.0.1

# Activate v2 P2P
v2transport=1

# Connections
rpcauth=<replace with your own auth line generated by rpcauth.py>
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333
whitelist=download@127.0.0.1          # for Electrs

# Raspberry Pi optimizations
maxconnections=40
maxuploadtarget=5000

# Initial block download optimizations
dbcache=4000
blocksonly=1
reply