Bitcoin Node Hashrate Seems low

Hi all,
I just started up a node but the synchronization seems to be taking extremely long.
After running for a couple of hours, it is still at block height 30k+. 10 peers connected, but hash rate is averaging ~10MH/s.
Speedtest conducted on RPi4 gets approx. 300Mbps download 400 Mbps upload. Even then, this seems oddly slow in terms of synchronization, considering most of the early blocks are “light” with only 1-2 transactions.

Is this normal behaviour? At this

Error log here:

= Umbrel debug info =

Umbrel version

0.5.3

Flashed OS version

v0.5.3

Raspberry Pi Model

Revision : d03114
Serial : 10000000c7b83baf
Model : Raspberry Pi 4 Model B Rev 1.4

Firmware

Dec 1 2021 15:01:54
Copyright (c) 2012 Broadcom
version 71bd3109023a0c8575585ba87cbb374d2eeb038f (clean) (release) (start)

Temperature

temp=48.7’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 7.8G 2.6G 191M 11M 5.0G 5.1G
Swap: 4.1G 0B 4.1G

total: 33.7%
bitcoin: 9.2%
lightning: 5.9%
thunderhub: 4.4%
electrs: 3.8%
mempool: 3.6%
chatbot-ui: 3.1%
bitfeed: 2.3%
ride-the-lightning: 2.2%
nostr-relay: 2.1%
vaultwarden: 1.8%
bluewallet: 1.6%
snort: 1.5%
tailscale: 0.7%
system: 0%

Memory monitor logs

2022-11-02 15:37:57 Memory monitor running!
2022-11-02 15:17:23 Memory monitor running!
2023-05-18 07:19:19 Memory monitor running!
2023-05-18 07:25:11 Memory monitor running!
2023-05-18 08:01:18 Memory monitor running!
2023-05-18 08:44:35 Memory monitor running!
2023-05-18 09:23:20 Memory monitor running!
2023-05-18 09:42:47 Memory monitor running!
2023-05-18 09:45:03 Memory monitor running!
2023-05-18 10:18:56 Memory monitor running!

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 29G 3.0G 25G 11% /
/dev/sda1 1.8T 13G 1.7T 1% /home/umbrel/umbrel

Startup service logs

May 18 10:19:28 umbrel umbrel startup[999]: Creating bitcoin_i2pd_daemon_1 …
May 18 10:19:28 umbrel umbrel startup[999]: Creating bitcoin_tor_1 …
May 18 10:19:28 umbrel umbrel startup[999]: Creating bitcoin_bitcoind_1 …
May 18 10:19:35 umbrel umbrel startup[999]: Creating ride-the-lightning_boltz_1 … done
May 18 10:19:36 umbrel umbrel startup[999]: Creating ride-the-lightning_app_proxy_1 … done
May 18 10:19:37 umbrel umbrel startup[999]: Creating ride-the-lightning_web_1 … done
May 18 10:19:38 umbrel umbrel startup[999]: Creating lightning_tor_1 … done
May 18 10:19:39 umbrel umbrel startup[999]: Creating electrs_tor_1 … done
May 18 10:19:39 umbrel umbrel startup[999]: Creating lightning_app_1 … done
May 18 10:19:40 umbrel umbrel startup[999]: Creating mempool_mariadb_1 … done
May 18 10:19:41 umbrel umbrel startup[999]: Creating lightning_app_proxy_1 … done
May 18 10:19:41 umbrel umbrel startup[999]: Creating mempool_api_1 … done
May 18 10:19:41 umbrel umbrel startup[999]: Creating mempool_web_1 … done
May 18 10:19:42 umbrel umbrel startup[999]: Creating bitcoin_i2pd_daemon_1 … done
May 18 10:19:42 umbrel umbrel startup[999]: Creating mempool_app_proxy_1 … done
May 18 10:19:42 umbrel umbrel startup[999]: Creating bitcoin_app_proxy_1 … done
May 18 10:19:42 umbrel umbrel startup[999]: Creating electrs_electrs_1 … done
May 18 10:19:42 umbrel umbrel startup[999]: Creating electrs_app_1 …
May 18 10:19:42 umbrel umbrel startup[999]: Creating lightning_lnd_1 … done
May 18 10:19:42 umbrel umbrel startup[999]: Creating bitcoin_tor_1 … done
May 18 10:19:43 umbrel umbrel startup[999]: Creating bitcoin_bitcoind_1 … done
May 18 10:19:43 umbrel umbrel startup[999]: Creating electrs_app_proxy_1 … done
May 18 10:19:43 umbrel umbrel startup[999]: Creating bitcoin_server_1 …
May 18 10:19:48 umbrel umbrel startup[999]: Creating electrs_app_1 … done
May 18 10:19:48 umbrel umbrel startup[999]: Creating bitcoin_server_1 … done
May 18 10:19:49 umbrel umbrel startup[999]: Umbrel is now accessible at
May 18 10:19:49 umbrel umbrel startup[999]: http://umbrel.local
May 18 10:19:49 umbrel umbrel startup[999]: http://192.168.1.35
May 18 10:19:49 umbrel systemd[1]: Started Umbrel Startup Service.
May 18 11:19:45 umbrel passwd[28526]: pam_unix(passwd:chauthtok): password changed for umbrel

External storage service logs

May 18 10:18:42 umbrel external storage mounter[500]: Running external storage mount script…
May 18 10:18:42 umbrel external storage mounter[500]: Found device “External USB3.0”
May 18 10:18:42 umbrel external storage mounter[500]: Blacklisting USB device IDs against UAS driver…
May 18 10:18:42 umbrel external storage mounter[500]: Rebinding USB drivers…
May 18 10:18:42 umbrel external storage mounter[500]: Checking USB devices are back…
May 18 10:18:42 umbrel external storage mounter[500]: Waiting for USB devices…
May 18 10:18:43 umbrel external storage mounter[500]: Waiting for USB devices…
May 18 10:18:44 umbrel external storage mounter[500]: Waiting for USB devices…
May 18 10:18:45 umbrel external storage mounter[500]: Checking if the device is ext4…
May 18 10:18:45 umbrel external storage mounter[500]: Yes, it is ext4
May 18 10:18:45 umbrel external storage mounter[500]: Checking filesystem for corruption…
May 18 10:18:45 umbrel external storage mounter[500]: e2fsck 1.44.5 (15-Dec-2018)
May 18 10:18:46 umbrel external storage mounter[500]: umbrel: clean, 308250/122101760 files, 10426537/488378368 blocks
May 18 10:18:46 umbrel external storage mounter[500]: Mounting partition…
May 18 10:18:46 umbrel external storage mounter[500]: Checking if device contains an Umbrel install…
May 18 10:18:46 umbrel external storage mounter[500]: Yes, it contains an Umbrel install
May 18 10:18:46 umbrel external storage mounter[500]: Bind mounting external storage over local Umbrel installation…
May 18 10:18:46 umbrel external storage mounter[500]: Bind mounting external storage over local Docker data dir…
May 18 10:18:46 umbrel external storage mounter[500]: Bind mounting external storage to /swap
May 18 10:18:46 umbrel external storage mounter[500]: Bind mounting SD card root at /sd-card…
May 18 10:18:46 umbrel external storage mounter[500]: Checking Umbrel root is now on external storage…
May 18 10:18:47 umbrel external storage mounter[500]: Checking /var/lib/docker is now on external storage…
May 18 10:18:47 umbrel external storage mounter[500]: Checking /swap is now on external storage…
May 18 10:18:47 umbrel external storage mounter[500]: Setting up swapfile
May 18 10:18:47 umbrel external storage mounter[500]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
May 18 10:18:47 umbrel external storage mounter[500]: no label, UUID=3abc48d7-b487-4f7e-99d5-5553684828c2
May 18 10:18:48 umbrel external storage mounter[500]: Checking SD Card root is bind mounted at /sd-root…
May 18 10:18:48 umbrel external storage mounter[500]: Starting external drive mount monitor…
May 18 10:18:48 umbrel external storage mounter[500]: Mount script completed successfully!
May 18 10:18:48 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Thu 2023-05-18 10:18:37 UTC, end at Thu 2023-05-18 11:19:59 UTC. –
May 18 10:18:56 umbrel systemd[1]: Starting External Storage SDcard Updater…
May 18 10:18:56 umbrel external storage updater[921]: Checking if SD card Umbrel is newer than external storage…
May 18 10:18:56 umbrel external storage updater[921]: No, SD version is not newer, exiting.
May 18 10:18:56 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

Pulling web … extracting (69.6%)
Pulling web … extracting (70.6%)
Pulling web … extracting (71.6%)
Pulling web … extracting (72.6%)
Pulling web … extracting (73.6%)
Pulling web … extracting (74.6%)
Pulling web … extracting (75.6%)
Pulling web … extracting (76.6%)
Pulling web … extracting (77.6%)
Pulling web … extracting (78.6%)
Pulling web … extracting (79.6%)
Pulling web … extracting (80.6%)
Pulling web … extracting (81.6%)
Pulling web … extracting (82.6%)
Pulling web … extracting (83.6%)
Pulling web … extracting (84.6%)
Pulling web … extracting (85.6%)
Pulling web … extracting (86.6%)
Pulling web … extracting (88.5%)
Pulling web … extracting (90.5%)
Pulling web … extracting (91.5%)
Pulling web … extracting (92.5%)
Pulling web … extracting (93.5%)
Pulling web … extracting (94.5%)
Pulling web … extracting (95.5%)
Pulling web … extracting (96.5%)
Pulling web … extracting (97.5%)
Pulling web … extracting (98.5%)
Pulling web … extracting (100.0%)
Pulling web … pull complete
Pulling web … digest: sha256:1c3c2b0563e567258a…
Pulling web … status: downloaded newer image fo…
Pulling web … done
Starting app nostr-relay…
Creating nostr-relay_web_1 …
Creating nostr-relay_relay_1 …
Creating nostr-relay_app_proxy_1 …
Creating nostr-relay_relay_1 … done
Creating nostr-relay_web_1 … done
Creating nostr-relay_app_proxy_1 … done
Saving app nostr-relay in DB…
Successfully installed app nostr-relay
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: debug
karen is getting triggered!

Docker containers

NAMES STATUS
nostr-relay_relay_1 Up 51 minutes
nostr-relay_app_proxy_1 Up 51 minutes
nostr-relay_web_1 Up 51 minutes
chatbot-ui_web_1 Up 51 minutes
chatbot-ui_app_proxy_1 Up 51 minutes
snort_web_1 Up 52 minutes
snort_app_proxy_1 Up 52 minutes
vaultwarden_server_1 Up 52 minutes (healthy)
vaultwarden_app_proxy_1 Up 52 minutes
bluewallet_lndhub_1 Restarting (1) 54 seconds ago
bluewallet_app_proxy_1 Up 52 minutes
bluewallet_redis_1 Up 52 minutes
bitfeed_web_1 Up 53 minutes
bitfeed_api_1 Up 53 minutes
bitfeed_app_proxy_1 Up 53 minutes
bitcoin_server_1 Up About an hour
electrs_app_1 Up About an hour
bitcoin_bitcoind_1 Up About an hour
bitcoin_tor_1 Up About an hour
bitcoin_i2pd_daemon_1 Up About an hour
bitcoin_app_proxy_1 Up About an hour
electrs_app_proxy_1 Up About an hour
mempool_app_proxy_1 Up About an hour
electrs_electrs_1 Up About an hour
lightning_app_proxy_1 Up About an hour
mempool_web_1 Up About an hour
lightning_tor_1 Up About an hour
lightning_app_1 Up About an hour
mempool_api_1 Up About an hour
electrs_tor_1 Up About an hour
lightning_lnd_1 Up About an hour
mempool_mariadb_1 Up About an hour
ride-the-lightning_web_1 Up About an hour
ride-the-lightning_app_proxy_1 Up About an hour
ride-the-lightning_boltz_1 Restarting (1) 33 seconds ago
tailscale_web_1 Up About an hour
thunderhub_web_1 Up About an hour
thunderhub_app_proxy_1 Up About an hour
nginx Up About an hour
dashboard Up About an hour
tor_proxy Up About an hour
manager Up About an hour
auth Up About an hour

Umbrel logs

Attaching to manager
manager | ::ffff:10.21.0.11 - - [Thu, 18 May 2023 11:20:26 GMT] “GET /v1/account/token?token=480fdf342257800c112a962539a09d8f3fba63af1c1d8a823f6a3865b96e411a HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.11 - - [Thu, 18 May 2023 11:20:26 GMT] “GET /v1/account/token?token=480fdf342257800c112a962539a09d8f3fba63af1c1d8a823f6a3865b96e411a HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 18 May 2023 11:20:26 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 18 May 2023 11:20:27 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 18 May 2023 11:20:29 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 18 May 2023 11:20:30 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.11 - - [Thu, 18 May 2023 11:20:31 GMT] “GET /v1/account/token?token=480fdf342257800c112a962539a09d8f3fba63af1c1d8a823f6a3865b96e411a HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 18 May 2023 11:20:31 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.11 - - [Thu, 18 May 2023 11:20:31 GMT] “GET /v1/account/token?token=480fdf342257800c112a962539a09d8f3fba63af1c1d8a823f6a3865b96e411a HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 18 May 2023 11:20:33 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager

Tor Proxy logs

Attaching to tor_proxy
tor_proxy | May 18 10:19:58.000 [notice] Bootstrapped 60% (loading_descriptors): Loading relay descriptors
tor_proxy | May 18 10:20:00.000 [notice] Bootstrapped 68% (loading_descriptors): Loading relay descriptors
tor_proxy | May 18 10:20:00.000 [notice] Bootstrapped 73% (loading_descriptors): Loading relay descriptors
tor_proxy | May 18 10:20:01.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_proxy | May 18 10:20:01.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_proxy | May 18 10:20:02.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_proxy | May 18 10:20:02.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_proxy | May 18 10:20:03.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_proxy | May 18 10:20:03.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_proxy | May 18 10:20:04.000 [notice] Bootstrapped 100% (done): Done

App logs

bitcoin

Attaching to bitcoin_server_1, bitcoin_bitcoind_1, bitcoin_tor_1, bitcoin_i2pd_daemon_1, bitcoin_app_proxy_1
bitcoind_1 | 2023-05-18T11:20:39Z UpdateTip: new best=0000000042fcd65c964e27ae3f8ff837bc5fa00f60394af1faef343963411847 height=37105 version=0x00000001 log2_work=47.227762 tx=37369 date=‘2010-01-29T22:38:44Z’ progress=0.000045 cache=8.1MiB(37288txo)
app_proxy_1 | Validating token: 480fdf342257 …
bitcoind_1 | 2023-05-18T11:20:39Z UpdateTip: new best=00000000364a2f0e4d2030d7dd5199947314bf5c3d332d067cfc895207692d01 height=37106 version=0x00000001 log2_work=47.227813 tx=37370 date=‘2010-01-29T22:39:56Z’ progress=0.000045 cache=8.1MiB(37289txo)
bitcoind_1 | 2023-05-18T11:20:39Z UpdateTip: new best=000000003aca8e6d8ea79b02b33b9301a2142de0179a1362819778b4be920edf height=37107 version=0x00000001 log2_work=47.227863 tx=37371 date=‘2010-01-29T22:42:50Z’ progress=0.000045 cache=8.1MiB(37290txo)
app_proxy_1 | Validating token: 480fdf342257 …
bitcoind_1 | 2023-05-18T11:20:39Z UpdateTip: new best=0000000036513136f994e3c1fa5e4944d11b53c6cb5c2b19cbcdb851ddc5dc96 height=37108 version=0x00000001 log2_work=47.227914 tx=37372 date=‘2010-01-29T22:44:38Z’ progress=0.000045 cache=8.1MiB(37291txo)
bitcoind_1 | 2023-05-18T11:20:39Z UpdateTip: new best=000000008ed82f3de026c5f37f08ea971dc31f699838b737b1bb7702bf029ef8 height=37109 version=0x00000001 log2_work=47.227964 tx=37373 date=‘2010-01-29T22:47:45Z’ progress=0.000045 cache=8.1MiB(37292txo)
app_proxy_1 | Validating token: 480fdf342257 …
app_proxy_1 | Validating token: 480fdf342257 …
bitcoind_1 | 2023-05-18T11:20:39Z UpdateTip: new best=000000007ed833ccc122a52e3f46d3a2a0e8a193aed05356580d51f0ca31719c height=37110 version=0x00000001 log2_work=47.228015 tx=37374 date=‘2010-01-29T23:10:34Z’ progress=0.000045 cache=8.1MiB(37293txo)
bitcoind_1 | 2023-05-18T11:20:39Z UpdateTip: new best=000000009e63f198b71fb9cadaac50522fcd470f0f3770ad01e9dfdef0aaf8a0 height=37111 version=0x00000001 log2_work=47.228066 tx=37375 date=‘2010-01-29T23:30:16Z’ progress=0.000045 cache=8.1MiB(37294txo)
tor_1 | May 18 10:20:07.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
i2pd_daemon_1 | 10:53:19@526/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 10:53:39@738/error - Tunnel: Tunnel with id 4217581434 already exists
i2pd_daemon_1 | 10:54:33@338/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1 | 10:57:13@738/error - Tunnel: Tunnel with id 366371053 already exists
server_1 | umbrel-middleware
app_proxy_1 | Validating token: 480fdf342257 …
app_proxy_1 | Validating token: 480fdf342257 …
app_proxy_1 | Validating token: 480fdf342257 …
bitcoind_1 | 2023-05-18T11:20:39Z UpdateTip: new best=00000000b2ea03b8610e246e28fedec1f3eca488d6c25cc3a9866ddf7c07c309 height=37112 version=0x00000001 log2_work=47.228116 tx=37376 date=‘2010-01-29T23:36:48Z’ progress=0.000045 cache=8.1MiB(37295txo)
app_proxy_1 | Validating token: 480fdf342257 …
i2pd_daemon_1 | 10:58:56@526/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 11:01:42@338/error - SSU2: RelayIntro unknown router to introduce
tor_1 | May 18 10:20:08.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
bitcoind_1 | 2023-05-18T11:20:39Z UpdateTip: new best=00000000b2d7f083db940f1bcca33bb3eab2b213f1e83f36d006e93254662cc6 height=37113 version=0x00000001 log2_work=47.228167 tx=37377 date=‘2010-01-29T23:37:25Z’ progress=0.000045 cache=8.1MiB(37296txo)
bitcoind_1 | 2023-05-18T11:20:39Z UpdateTip: new best=0000000089555c7434946e0222c92339265c2e2187267de2d4edd484cd04c61f height=37114 version=0x00000001 log2_work=47.228217 tx=37379 date=‘2010-01-29T23:44:14Z’ progress=0.000045 cache=8.1MiB(37298txo)
app_proxy_1 | Validating token: 480fdf342257 …
app_proxy_1 | Validating token: 480fdf342257 …
tor_1 | May 18 10:20:08.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | May 18 10:20:09.000 [notice] Bootstrapped 100% (done): Done
tor_1 | May 18 10:21:51.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor_1 | May 18 10:23:03.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor_1 | May 18 10:23:27.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor_1 | May 18 10:24:03.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
i2pd_daemon_1 | 11:07:18@338/error - SSU2: RelayIntro unknown router to introduce
tor_1 | May 18 10:26:24.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor_1 | May 18 11:01:42.000 [notice] Application asked to connect to port 0. Refusing.
i2pd_daemon_1 | 11:08:35@526/error - ElGamal decrypt hash doesn’t match
server_1 | ::ffff:10.21.0.11 - - [Thu, 18 May 2023 11:20:39 GMT] “GET /v1/bitcoind/info/blocks?from=37073&to=37076 HTTP/1.1” 200 992 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36”
i2pd_daemon_1 | 11:08:35@526/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
server_1 |
i2pd_daemon_1 | 11:18:21@526/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.11 - - [Thu, 18 May 2023 11:20:39 GMT] “GET /v1/bitcoind/info/sync HTTP/1.1” 200 106 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.11 - - [Thu, 18 May 2023 11:20:39 GMT] “GET /v1/bitcoind/info/blocks?from=37111&to=37114 HTTP/1.1” 200 992 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36”
server_1 |
server_1 | umbrel-middleware

================
==== Result ====

The debug script did not automatically detect any issues with your Umbrel.

Don’t see any breaking errors in your logs,

After a couple more hours see if there’s a change?

Looks like you’re on Pi 4 and it should get around 200

Some things to just double check, you don’t have any throttling on your router or connections. This may not be as common anymore but anything older than a Cat 5e ethernet cable you’re using would not handle the throughput of your 300Mbps download speed, to under 100…

You can also increase your cache size to help with the initial sync in Bitcoin Node Advanced Settings, as shown here increasing to 3500MB would be good if you have 4GB of RAM:

Then scroll download and Save and Restart Node for it to take effect after making a change.

Referenced in the official FAQ here under “Speeding Up Blockchain Synchronization,”

You can also optionally Enable “Outgoing Connections to Clearnet Peers” and disable “Connect to all Clearnet Peers over Tor” so your Bitcoin node is not throttled by Tor’s latency to fetch the blocks. Note: This will leak IP address to the Bitcoin network, and your ISP will also be able to figure out that you’re running a Bitcoin node. If you change these settings, you may revert them after the synchronizing is complete.

1 Like

I’m currently using a Cat6 ethernet cable which should work fine as the bottleneck seems to be download/upload speeds.

Have made adjustments based on your recommendation, will report back in a while to see if it’s any joy.

Much thanks!

Quick update - Hashrate has gone up to 8GH/s (thank you!)

1 Like

If I remember correctly, this is not your own hashrate. It’s the hashrate of the blockchain at that point in time.

It will keep going up as you go through the years.

2 Likes

Ah, that makes so much more sense. Thank you!
Is this officially documented somewhere? It would seem rather strange to me to have a record of the hashrate across time as a top level detail.

I haven’t seen it documented. I believe I saw it mentioned somewhere when I had the same worry about slow hash rate :smiley:

What’s your hash rate now? Up to PH/s? Which I don’t think the mighty Pi is capable of!

No worries, you’r Pi is not doing any hashes, it merely validates every single TX in the timechain, which is more than enough load for it…
You will not be getting any bitcoin for running the node, that’s what “miner nodes” do with ASICs. You simply act as a guardian against malicious and/or invalid TX entering the timechain.

The hashrate you see is truly the network hashrate at any given point in time, as your node syncs.
The sync is so slow, because you have to do the validation :slight_smile:

Why it’s shown? Ask creator of this UI, I don’t know, guess just as a cool gimmick to see how hashrate goes up over time in magnificent manner.

1 Like

Node is fully synchronized and hash rate is currently at 363 EH/s - sounds about right for the network hashrate!

1 Like

Thank you for the clarification.

Initially, I was thinking the hashrate refers to the node’s local verification process as it validates transactions/blocks from the genesis block. I therefore thought that this hashrate is a local node performance metric that can be improved upon.

I understand now that the hashrate metric instead refers to the historical network hashrate at the latest synchronized blockheight (and thus starts off in the single digits MH/s - thanks Satoshi!)

1 Like

lnbc190280n1pjxe0v3pp57247q9d0q6dswfqz6cecs3yzunsqt0dlyv2tcg4tkxuecr5nyl4qdp8gdhkjmj8v96x2gz0wfjx2u3qyvcnvwpkx56rxwqcqzzsxqrp90sp5pqrcu26v7h3svzt8jc8uuuy4ppvug9m8pxfjawczdtn6zge9z20q9qyyssqh7z5h7g0dvfhrtz8vypxt0hur8cpmz0lpgdhap0wfz0ksmcxwscp9pxezjygyxf2d95pg8nm6u7hucjhvyffr46nlgfmergc2kxer0gp7muusm