So I have spent more time with mynode https://mynodebtc.com/ along with RaspiBlitz https://raspiblitz.com/
Both are solid and both do work well.
The RaspiBlitz does not have all the features that mynode does, but it also does not limit you asking to buy the paid version to unlock more stuff.
mynode can run on different hardware even a VM where RaspiBlitz is only for a RPi (which this thread is about)
If you don't want to play and learn, get an RPI4 with 2GB or 4GB, an SD card and a USB SSD, burn the SD card with one of them and you will have a running node with Lightning in a very short time.
Both offer good support (although not here more github / telegram)
Both do work, have had both of them running for a while.
-Dave
Topic: Advice on Raspberry pi hardware for running full BTC node - page 2. (Read 3198 times)
Bit of humor.
The RPi2 and RPi3 look very similar.
When they are in a clear case they are almost impossible to tell apart.
You then can spend about an hour trying to get the non existent wi-fi on a RPi2 to work.
I may possibly have some recent experience with this.
Also, for sale 1 slightly used RPi2 only thrown at wall once.
-Dave
The RPi2 and RPi3 look very similar.
When they are in a clear case they are almost impossible to tell apart.
You then can spend about an hour trying to get the non existent wi-fi on a RPi2 to work.
I may possibly have some recent experience with this.
Also, for sale 1 slightly used RPi2 only thrown at wall once.
-Dave
Tip : you can use command sudo dmidecode -t1 to find type of your raspberry, notebook or motherboard. neofetch also can show your device type & specification in general.
That would have required me to think in that way.
I really thought it was a 3. Through the years I have had a bunch of them with troublesome Wi-Fi & BT. I figured it was just one of them. Did not notice that I grabbed an older one.
-Dave
Bit of humor.
The RPi2 and RPi3 look very similar.
When they are in a clear case they are almost impossible to tell apart.
You then can spend about an hour trying to get the non existent wi-fi on a RPi2 to work.
I may possibly have some recent experience with this.
Also, for sale 1 slightly used RPi2 only thrown at wall once.
-Dave
The RPi2 and RPi3 look very similar.
When they are in a clear case they are almost impossible to tell apart.
You then can spend about an hour trying to get the non existent wi-fi on a RPi2 to work.
I may possibly have some recent experience with this.
Also, for sale 1 slightly used RPi2 only thrown at wall once.
-Dave
Tip : you can use command sudo dmidecode -t1 to find type of your raspberry, notebook or motherboard. neofetch also can show your device type & specification in general.
Bit of humor.
The RPi2 and RPi3 look very similar.
When they are in a clear case they are almost impossible to tell apart.
You then can spend about an hour trying to get the non existent wi-fi on a RPi2 to work.
I may possibly have some recent experience with this.
Also, for sale 1 slightly used RPi2 only thrown at wall once.
-Dave
The RPi2 and RPi3 look very similar.
When they are in a clear case they are almost impossible to tell apart.
You then can spend about an hour trying to get the non existent wi-fi on a RPi2 to work.
I may possibly have some recent experience with this.
Also, for sale 1 slightly used RPi2 only thrown at wall once.
-Dave
Wouldnt you want to use a much faster hard drive to run bitcoin on such as a "Samsung 960 Pro NVMe M.2 SSD" or something of that speed? Or would that not be able to connect to the Rasberry Pi? You would think you would want something faster than 100mb/s though, especially for a public node... those usb thumb drives arent very fast...
The RPi only has USB so the NVMe and other drives will not work.
You can get a 500GB SSD usb drive for under $90.
-Dave
Wouldnt you want to use a much faster hard drive to run bitcoin on such as a "Samsung 960 Pro NVMe M.2 SSD" or something of that speed? Or would that not be able to connect to the Rasberry Pi? You would think you would want something faster than 100mb/s though, especially for a public node... those usb thumb drives arent very fast...
Such an SSD would be a huge waste of resources. The latest Raspberry Pi has USB 3.0 which allows for speeds up to ~600 MB/s while that drive can perform much better. I don't think if there is any point in buying an expensive SSD for such a budget setup. A cheap HDD is enough.
Trying to update mynode last couple hours and its proving to be beyond my understanding. If anyone's able to help, I'm stuck.
Here's the instructions:
I'm stuck at #3
Using git bash on windows 10 I get this:
user@mycomputer MINGW64 ~/mynode (master)
Here's the instructions:
Quote
1. Start by running myNode on your device via the instructions above in "Running myNode"
2. Clone the latest release from the git repo on your PC or laptop
* Run 'git clone https://github.com/mynodebtc/mynode.git --branch latest_release'
* Run 'cd mynode'
3. Run 'make rootfs'
4. Run 'make start_file_server'
* This will run a local HTTP server so your device can download files
5. On your device, run 'sudo mynode-local-upgrade [dev pc ip address]'
* This will download your locally generated artifact and install it on your device
* Your device will automatically reboot to ensure updates take effect
6. Optional: Run 'make stop_file_server'
* This will stop the local HTTP server
7. You are now running the latest version of myNode software!
2. Clone the latest release from the git repo on your PC or laptop
* Run 'git clone https://github.com/mynodebtc/mynode.git --branch latest_release'
* Run 'cd mynode'
3. Run 'make rootfs'
4. Run 'make start_file_server'
* This will run a local HTTP server so your device can download files
5. On your device, run 'sudo mynode-local-upgrade [dev pc ip address]'
* This will download your locally generated artifact and install it on your device
* Your device will automatically reboot to ensure updates take effect
6. Optional: Run 'make stop_file_server'
* This will stop the local HTTP server
7. You are now running the latest version of myNode software!
I'm stuck at #3
Using git bash on windows 10 I get this:
user@mycomputer MINGW64 ~/mynode (master)
Code:
$ make rootfs
bash: make: command not found
Not sure what I'm doing wrong bash: make: command not found
Your mistake is using Windows, tools/software make isn't available by default on Windows. I saw people port tool make to Windows, but i don't know if it's stable or still updated.
My suggestion is run the guide from linux distro which have live OS feature such as Ubuntu. If you're not sure how to do it, see https://ubuntu.com/tutorials/tutorial-create-a-usb-stick-on-windows
Thanks, recently I made a bootable ubuntu flash drive and followed directions to install alongside Windows for a dual boot experience however I'm not sure its working, still can't figure out how to boot into ubuntu (just goes to windows). I can use ubuntu live from usb at startup but cannot save anything locally. Tried this tutorial.
Trying to update mynode last couple hours and its proving to be beyond my understanding. If anyone's able to help, I'm stuck.
Here's the instructions:
I'm stuck at #3
Using git bash on windows 10 I get this:
user@mycomputer MINGW64 ~/mynode (master)
Here's the instructions:
Quote
1. Start by running myNode on your device via the instructions above in "Running myNode"
2. Clone the latest release from the git repo on your PC or laptop
* Run 'git clone https://github.com/mynodebtc/mynode.git --branch latest_release'
* Run 'cd mynode'
3. Run 'make rootfs'
4. Run 'make start_file_server'
* This will run a local HTTP server so your device can download files
5. On your device, run 'sudo mynode-local-upgrade [dev pc ip address]'
* This will download your locally generated artifact and install it on your device
* Your device will automatically reboot to ensure updates take effect
6. Optional: Run 'make stop_file_server'
* This will stop the local HTTP server
7. You are now running the latest version of myNode software!
2. Clone the latest release from the git repo on your PC or laptop
* Run 'git clone https://github.com/mynodebtc/mynode.git --branch latest_release'
* Run 'cd mynode'
3. Run 'make rootfs'
4. Run 'make start_file_server'
* This will run a local HTTP server so your device can download files
5. On your device, run 'sudo mynode-local-upgrade [dev pc ip address]'
* This will download your locally generated artifact and install it on your device
* Your device will automatically reboot to ensure updates take effect
6. Optional: Run 'make stop_file_server'
* This will stop the local HTTP server
7. You are now running the latest version of myNode software!
I'm stuck at #3
Using git bash on windows 10 I get this:
user@mycomputer MINGW64 ~/mynode (master)
Code:
$ make rootfs
bash: make: command not found
Not sure what I'm doing wrong bash: make: command not found
Your mistake is using Windows, tools/software make isn't available by default on Windows. I saw people port tool make to Windows, but i don't know if it's stable or still updated.
My suggestion is run the guide from linux distro which have live OS feature such as Ubuntu. If you're not sure how to do it, see https://ubuntu.com/tutorials/tutorial-create-a-usb-stick-on-windows
Trying to update mynode last couple hours and its proving to be beyond my understanding. If anyone's able to help, I'm stuck.
Here's the instructions:
I'm stuck at #3
Using git bash on windows 10 I get this:
user@mycomputer MINGW64 ~/mynode (master)
Here's the instructions:
Quote
1. Start by running myNode on your device via the instructions above in "Running myNode"
2. Clone the latest release from the git repo on your PC or laptop
* Run 'git clone https://github.com/mynodebtc/mynode.git --branch latest_release'
* Run 'cd mynode'
3. Run 'make rootfs'
4. Run 'make start_file_server'
* This will run a local HTTP server so your device can download files
5. On your device, run 'sudo mynode-local-upgrade [dev pc ip address]'
* This will download your locally generated artifact and install it on your device
* Your device will automatically reboot to ensure updates take effect
6. Optional: Run 'make stop_file_server'
* This will stop the local HTTP server
7. You are now running the latest version of myNode software!
2. Clone the latest release from the git repo on your PC or laptop
* Run 'git clone https://github.com/mynodebtc/mynode.git --branch latest_release'
* Run 'cd mynode'
3. Run 'make rootfs'
4. Run 'make start_file_server'
* This will run a local HTTP server so your device can download files
5. On your device, run 'sudo mynode-local-upgrade [dev pc ip address]'
* This will download your locally generated artifact and install it on your device
* Your device will automatically reboot to ensure updates take effect
6. Optional: Run 'make stop_file_server'
* This will stop the local HTTP server
7. You are now running the latest version of myNode software!
I'm stuck at #3
Using git bash on windows 10 I get this:
user@mycomputer MINGW64 ~/mynode (master)
Code:
$ make rootfs
bash: make: command not found
Not sure what I'm doing wrong bash: make: command not found
Success! Finally got MyNode running on Raspberry Pi 4.
Took about 28 hours to download it and finish the sync to the pi and powered only with the official RPi cable.
I'll be trying to upgrade it manually next and then, figure out how to access it from another network.
Took about 28 hours to download it and finish the sync to the pi and powered only with the official RPi cable.
I'll be trying to upgrade it manually next and then, figure out how to access it from another network.
28 hours is impressive.
It took one full month to reindex and vaidate the blockchain (downloading was pretty fast actually) on my Rpi3.
28 hours is good.
I did 6 with a 2000 dollar pc.
seems like it is competive at last.
so this was a rasp pi 4. correct?
what is it loaded to a ssd or a hdd or a sd card?
Success! Finally got MyNode running on Raspberry Pi 4.
Took about 28 hours to download it and finish the sync to the pi and powered only with the official RPi cable.
I'll be trying to upgrade it manually next and then, figure out how to access it from another network.
Took about 28 hours to download it and finish the sync to the pi and powered only with the official RPi cable.
I'll be trying to upgrade it manually next and then, figure out how to access it from another network.
28 hours is impressive.
It took one full month to reindex and vaidate the blockchain (downloading was pretty fast actually) on my Rpi3.
28 hours is good.
I did 6 with a 2000 dollar pc.
seems like it is competive at last.
so this was a rasp pi 4. correct?
what is it loaded to a ssd or a hdd or a sd card?
Success! Finally got MyNode running on Raspberry Pi 4.
Took about 28 hours to download it and finish the sync to the pi and powered only with the official RPi cable.
I'll be trying to upgrade it manually next and then, figure out how to access it from another network.
Took about 28 hours to download it and finish the sync to the pi and powered only with the official RPi cable.
I'll be trying to upgrade it manually next and then, figure out how to access it from another network.
28 hours is impressive.
It took one full month to reindex and vaidate the blockchain (downloading was pretty fast actually) on my Rpi3.
Off network is easy all you have to do is forward the ports in your firewall to the ip of your mynode and access it by your public IP.
It has these ports open in it's own firewall by default. I closed a bunch of mine, but that's just me....
It has these ports open in it's own firewall by default. I closed a bunch of mine, but that's just me....
Code:
22 ALLOW Anywhere # allow SSH
80 ALLOW Anywhere # allow WWW
443 ALLOW Anywhere # allow Secure WWW
1900 ALLOW Anywhere # allow SSDP for UPnP discovery
10009 ALLOW Anywhere # allow Lightning gRPC
10080 ALLOW Anywhere # allow Lightning REST RPC
9735 ALLOW Anywhere # allow Lightning
8333 ALLOW Anywhere # allow Bitcoin mainnet
18333 ALLOW Anywhere # allow Bitcoin testnet
2222 ALLOW Anywhere # allow WebSSH2
3000 ALLOW Anywhere # allow LndHub
3002 ALLOW Anywhere # allow BTC RPC Explorer
3010 ALLOW Anywhere # allow RTL
5353 ALLOW Anywhere # allow Avahi
50001 ALLOW Anywhere # allow Electrum Server
50002 ALLOW Anywhere # allow Electrum Server
56881 ALLOW Anywhere # allow myNode QuickSync
51413 ALLOW Anywhere # allow myNode QuickSync
6771 ALLOW Anywhere # allow myNode QuickSync (LPD)
19999 ALLOW Anywhere # allow Netdata
51194 ALLOW Anywhere # allow VPN
61208 ALLOW Anywhere # allow Glances
Anywhere ALLOW 127.0.0.1 # allow from localhost
8332 ALLOW Anywhere # allow Bitcoin RPC - filtered by rpcallowip
28332 ALLOW 172.17.0.0/16 # allow Dojo zmqrawblock
28332 ALLOW 172.28.0.0/16 # allow Dojo zmqrawblock
28333 ALLOW 172.17.0.0/16 # allow Dojo zmqrawtx
28333 ALLOW 172.28.0.0/16 # allow Dojo zmqrawtx
28334 ALLOW 172.17.0.0/16 # allow Dojo zmqhashblock
28334 ALLOW 172.28.0.0/16 # allow Dojo zmqhashblock
4080 ALLOW Anywhere # allow Mempool.Space
8899 ALLOW Anywhere # allow Whirlpool
49392 ALLOW Anywhere # allow BTCPay Server-direct
80 ALLOW Anywhere # allow WWW
443 ALLOW Anywhere # allow Secure WWW
1900 ALLOW Anywhere # allow SSDP for UPnP discovery
10009 ALLOW Anywhere # allow Lightning gRPC
10080 ALLOW Anywhere # allow Lightning REST RPC
9735 ALLOW Anywhere # allow Lightning
8333 ALLOW Anywhere # allow Bitcoin mainnet
18333 ALLOW Anywhere # allow Bitcoin testnet
2222 ALLOW Anywhere # allow WebSSH2
3000 ALLOW Anywhere # allow LndHub
3002 ALLOW Anywhere # allow BTC RPC Explorer
3010 ALLOW Anywhere # allow RTL
5353 ALLOW Anywhere # allow Avahi
50001 ALLOW Anywhere # allow Electrum Server
50002 ALLOW Anywhere # allow Electrum Server
56881 ALLOW Anywhere # allow myNode QuickSync
51413 ALLOW Anywhere # allow myNode QuickSync
6771 ALLOW Anywhere # allow myNode QuickSync (LPD)
19999 ALLOW Anywhere # allow Netdata
51194 ALLOW Anywhere # allow VPN
61208 ALLOW Anywhere # allow Glances
Anywhere ALLOW 127.0.0.1 # allow from localhost
8332 ALLOW Anywhere # allow Bitcoin RPC - filtered by rpcallowip
28332 ALLOW 172.17.0.0/16 # allow Dojo zmqrawblock
28332 ALLOW 172.28.0.0/16 # allow Dojo zmqrawblock
28333 ALLOW 172.17.0.0/16 # allow Dojo zmqrawtx
28333 ALLOW 172.28.0.0/16 # allow Dojo zmqrawtx
28334 ALLOW 172.17.0.0/16 # allow Dojo zmqhashblock
28334 ALLOW 172.28.0.0/16 # allow Dojo zmqhashblock
4080 ALLOW Anywhere # allow Mempool.Space
8899 ALLOW Anywhere # allow Whirlpool
49392 ALLOW Anywhere # allow BTCPay Server-direct
Success! Finally got MyNode running on Raspberry Pi 4.
Took about 28 hours to download it and finish the sync to the pi and powered only with the official RPi cable.
I'll be trying to upgrade it manually next and then, figure out how to access it from another network.
Took about 28 hours to download it and finish the sync to the pi and powered only with the official RPi cable.
I'll be trying to upgrade it manually next and then, figure out how to access it from another network.
For bitcoin itself you can usually just copy the files. I have at times had issues with permissions but that is usually just a quick fix.
For the electrum server and the lnd server I have no idea of how they are setup here. I know in general how they are done but if anything was tweaked / changed I would have to *gasp of horror* read the docs.
In general when doing something like this I prefer to do it cold to get a feel for how someone who has never done it before would see it.
Gives me a bit better feel.
So far I do like mynode for the most part. Everything works, decent performance, nice gui.
Not happy about the fact that the latest image for VM is way older then the latest version of the setup itself and the way to upgrade it without paying for the Premium version is a bit convoluted.
-Dave
For the electrum server and the lnd server I have no idea of how they are setup here. I know in general how they are done but if anything was tweaked / changed I would have to *gasp of horror* read the docs.
In general when doing something like this I prefer to do it cold to get a feel for how someone who has never done it before would see it.
Gives me a bit better feel.
So far I do like mynode for the most part. Everything works, decent performance, nice gui.
Not happy about the fact that the latest image for VM is way older then the latest version of the setup itself and the way to upgrade it without paying for the Premium version is a bit convoluted.
-Dave
I think just copy the blockchain files from a full node PC to the rasp pi should work.
yeah I would think so that seems to be fastest way to do it.
This is what Stadicus suggested on his guide Raspibolt.
Just read here:
https://github.com/Stadicus/RaspiBolt/blob/1.0/raspibolt_50_mainnet.md
I think just copy the blockchain files from a full node PC to the rasp pi should work.
yeah I would think so that seems to be fastest way to do it.
I think just copy the blockchain files from a full node PC to the rasp pi should work.
So the mynode VM finished the download and now I have it working on the other stuff (electrum server and such)
Seems like a nice GUI wrapper for all the stuff that you would have to CLI for.
The update process if you do not have the paid version seems a bit cumbersome. Once everything it done and synced I will make a backup of the virtual drives and see how well it works.
-Dave
Seems like a nice GUI wrapper for all the stuff that you would have to CLI for.
The update process if you do not have the paid version seems a bit cumbersome. Once everything it done and synced I will make a backup of the virtual drives and see how well it works.
-Dave
to give some benchmarks on a high-end beast pc .
I downloaded full node in six hours last night.
Did it with a ryzen 9 3900x cpu and a 2tb m2 nvme gen 4 hard drive.
along with 16gb ram and a 200mb internet connection.
a computer like mine is around 2000 to,build.
i suspect my bottleneck is my eth connection.
it does illustrate that full nodes are pretty hard to download quickly.
i think i could do it it quicker and spend less but a really fast download under four hours is tough if not impossible.
i knock the rasp pi but if you create a working 1 tb ssd for your rasp pi and clone it once a week. you would save a ton of money.
is it possible to run a rasp pi in a vm on a high end pc just to make a full node quickly then clone it to an ssd and use that with the rasp Pi.
I downloaded full node in six hours last night.
Did it with a ryzen 9 3900x cpu and a 2tb m2 nvme gen 4 hard drive.
along with 16gb ram and a 200mb internet connection.
a computer like mine is around 2000 to,build.
i suspect my bottleneck is my eth connection.
it does illustrate that full nodes are pretty hard to download quickly.
i think i could do it it quicker and spend less but a really fast download under four hours is tough if not impossible.
i knock the rasp pi but if you create a working 1 tb ssd for your rasp pi and clone it once a week. you would save a ton of money.
is it possible to run a rasp pi in a vm on a high end pc just to make a full node quickly then clone it to an ssd and use that with the rasp Pi.
Jump to: