Running a Tezos node on the *alphanet* and the *zeronet* made super-simple (with RPI3)


This is what I see when I run the ls -l command. From what you said it appears I have the correct time stamp for the tezos folder. I also definitely performed the command to switch to zero net. It seems to be running, but I’m hoping you can help me confirm that.



It only lets me post one picture per post, so here is what I currently see on my screen:



well done, you are in the game…

If your node was still running last night it should have restarted automatically at 1am, maybe check it out. Type ps aux you should a line like this “/home/tzuser/tezos/tezos-node run” with start time 01:00 (or Apr25)



I got it running with the ./tz-start shell script and it also restarted May 1st at 1:00 so I think that is all going smoothly!

However, I keep getting a bunch of “validator.peer(332)” with a hash after it followed by the error code “Unclassified error: Tezos_error_monad__Error_monad.Canceled” text and then followed by “p2p.maintenance: Too few connections (0)”. These several lines repeat the most often. Every once in a while it seems to actually establish a connection with a few peers. What could this be due to? Could I have an erroneous blockchain data? Is there a way I can verify it?

I was also curious as to how updates will be handled in the future. I believe that right now you create a precompiled version of the updates from the tezos github, add it on drop box, and then use the tz-switch script file to unzip the new version and switch in the appropriate files. Would there be a way to create an update script that would go directly to the tezos github, compile the necessary updates and switch them in? Just thinking about the future of this project and how I could possibly make one of these myself if needed.



I see the “unclassified error” too, I am not particularly worried at the moment. My explanation (maybe completely wrong) is that something has changed in the block format with the recent version for the zeronet and some nodes (not ours) are still running an old version

“too few connections(0)” is normal, as long as it happens only from time to time. If you keep the node running long enough, it will establish more and more connections and the chance of getting (0) becomes less likely. Keep in mind also that there are few nodes running on the zeronet.

Updates, good question.
I’ll try to keep supporting Tezos for RPI3 with the precompiled version through all the stages, alphanet->betanet->mainnet, unless at some point I get a red card from the TF. You are right the zip file is just that, basically I save you the trouble of compiling it by yourself.
But if you are planning to run a node on the mainnet you should definitely give it a try, please do it, I can help you out, and please feel free to contribute to the wiki page (it is open access).

To get started with the compilation, in the wiki page there is a link to old notes [a], have a look at the steps
to compile Tezos (second part of the notes), however because they are somehow outdated, before jumping into the real work, have a look also at page [c] (unpolished instructions) and replace whatever is in the old notes[a] with the updated instructions in [c]. I know it is far from ideal, but keep re-writing detailed instructions that would become outdated quickly is not worth the effort right now.

Anyway if you get stuck somewhere in the process let me know…


Hi all –

100% noob here. I’m embarrassed to say that even the super-simple instructions may have been too much for me. I’m hoping that I’m a good test case because at least some other tezos folks will be pretty ignorant when it comes to the RPI3 and baking. Hopefully they can learn from my mistakes.

Here’s what I did:

  1. Bought a RPI3 and fooled around with it for a bit.
  2. Formatted a 16GB SD card.
  3. Used to write the recommended 4GB file onto the SD card.
  4. Popped the SD card into my RPI3 and plugged it in.

Every time I have done this – and I’ve done it about 8 times on 3 different SD cards over a few days – the RPI3 starts running, a lot of text passes across the monitor, eventually (after maybe 30 seconds and maybe 100+ lines of information), I get one blue line that says “[something something] Fedora 26”. Then a little bit more script in white, and the screen goes dark. It remains dark and nothing else ever appears. I can leave it alone for a long time and nothing happens. Typing on the keyboard, using the RPI3 touchscreen, and/or clicking on the mouse also have no effect. I don’t see a command prompt or anything else no matter how long I wait.

As I said, I have re-downloaded the 4GB image file at least 3 times, and etched it onto at least 3 different SD cards, and the same thing happens every time. So I doubt it’s the cards.

Has anyone else experienced this? Is there something obvious I’ve screwed up? My best guess is that I shouldn’t have fully formatted the SD card before etching the image file onto it. (I.e. the card should contain something other than just the .img file when I put it in my RPI3.) Second-best guess is that I screwed up using Etcher, which would be impressive but is totally possible. (The appearance of all that text when I boot up the RPI3 cuts against this explanation.)

Any help would be greatly appreciated. Also, although I’m an intelligent human being in matters unrelated to computers/programming, you’re probably best off explaining what I’ve done wrong as you would to your grandmother. :slight_smile:


Hi @misifecu
no worries, this is work in progress for all of us…
If etcher completed the writing process successfully, then the image on your sd card should be ok. The correct booting of the RPI3 ends with the X11 environment (X-windows) with a basic graphic interface and an open terminal shell. My best guess is that there is something going on with your monitor/display. If you have a spare monitor I would try it and repeat the boot.

But before trying anything you should go to the RPI3 wiki ( and grab the latest image which contains Fedora28+precompiled Tezos(zeronet network), file: RPI3-TEZOS-050618.img. The setup is the same (etcher etc.), the image is a bit bigger (~7GB) but F28 will be the OS that we’ll rely on when the official tezos(betanet/mainet) will go live, at least for a year or so.
In summary, (1) get the new image RPI3-TEZOS-050618.img, (2) use etcher to write it on the SD card (3) boot the RPI3 (4) if all goes well, type the 3 commands to get your RPI3 on the zeronet (./, ./ and ./ (5) please let me know the outcome


Thanks much for the quick reply. I followed the steps you listed and I’m up and running. Very grateful for the help!


excellent news and congratulations!


new home
Please visit for updates and support of Tezos on RPI3


Thanks a lot for keeping a backup. My account was tottaly deleted from github, because I had a site that was exposing the way the Dash masternode owners were voting.


Hi @pedro, when you have time please could you change the link to the wiki page for Tezos on RPI3? Here is the new one:



Done, please check if it is ok now.
Also let me know if you suggest any changes or additions.


perfect, thanks!
keep up with Tezos.Rocks, it is the place to go for anyone interested in Tezos.


I’m not able to boot up the RP3 B+ with the RPI3-TEZOS-050618.img file. I believe that file is for RP3 B, and it’s not compatible with RP3 B+. Is there an comparable img file that is compatible with RP3 B+? If not, are there other instructions where I can load the Tezos alphanet (and soon betanet) on an RP3 B+?

Great work! Thanks!


This is unexpected, The image RPI3-TEZOS-050618.img is based on Fedora 28 (minimal) which supports RPI3 B+, but it was created on my RPI3 B, it should not matter though, I am not sure. I don’t have a RPI3 B+ to test it, and I assume you don’t have a RPI3 B to verify your installation. We are stuck!
You can try two things.
I) according to this article one known issue that causes the boot process to freeze is the keyboard and the mouse. Try booting without them and add them later.
II) you can start from the original Fedora minimal for arm servers, but then you’ll have to configure the machine on your own, while the image I posted was tuned for Tezos pretty much out of the box.

Either way, if you make some progress, please share, there are other people that may be interested to use B+.

Keep up with the latest info about Tezos and RPI3 here:


Thank you for your reply. The screen I get with the 050618.file looks exactly like that shown in this post. The LED also flashes red. I’ve tried removing the mouse, keyboard, ethernet, along with 3 SD different cards, the image file from February, and 3 different power sources. Same screen. It’s a brand new B+, which I thought must be faulty, but then I came across this post and also this one (Sorry, only 2 links are allowed in my post, but here’s the URL They both implied it also could be an operating system problem. So when i tried with the Raspbian operating system, it booted up fine. I’m going to just buy a new B rather than trying to setup the B+, and leave that to those more skilled-in-the-art than me. Thanks again for your help.


oh no, sorry this is really disappointing, the image I posted includes the right firmware file bcm2837-rpi-3-b-plus.dtb, the same used by Raspbian, it should work. When you have time, it would be helpful if you could try to install the original Fedora minimal from
If the original Fedora works then I screwed up something with the image, I am investigating this issue and will report as soon as I find out more.


Happy to help, but will need some help as I’m not an IT person. I had a few minutes to go over Fedora. I downloaded the minimal version 328 MB raw file on my Windows computer that has an SD card reader. The Fedora documentation gives the install instructions, but I don’t have a linux computer to run the scripts. Is there a way to install Fedora on the SD card in Windows? Or am I missing something? I can try fiddling around a bit later today.


thanks for helping, it is actually very easy, with the image file of fedora minimal, just use etcher the same way you have done with the image that I posted, that’s it.
I am curious to see if it boots properly. Then if you decide to keep using Fedora on the B+, you would need to do something to expand the OS over the entire SD card using these two commands (as a superuser):
growpart /dev/mmcblk0 4
resize2fs /dev/mmcblk0p4
let me know if you need more info. Since it is only text based, to shutdown just type (as a superuser): shutdown -h now