Introducing [RAOOL] - Raspberry stakepool

Staking & Delegation Pool Introductions
62

Thanks for your reply, that’s a really good news!

I’ll give it a try on mine.

63

Hi to all raspbians,

I have a pi4 4gb as well and i want to use it just for node. My question is…can i run 2 nodes on same Pi ?

64
1 Like
65

Hey I just created a new Post Guide Raspberry Pi 4 HTN Setup [Pi Pool]. I just created a guide to how to setup the HTN on Raspberry Pi. I hope it can help some of you.

3 Likes
66

thank you alessandro

1 Like
68

hello Alessandro,

hope all is well!

i am looking to set up two raspberry Pi’s, do you have a guide or know one i can follow to get started, please?

kind regards
R

69

Hey, yes you can check this out: GitHub - alessandrokonrad/Pi-Pool: Cardano Stakepool on Raspberry Pi

70

You can also install Docker on the Pi and then simply do …

docker run --detach \
    --name=relay \
    -p 3001:3001 \
    -v shelley-data:/opt/cardano/data \
    nessusio/cardano run

docker logs -f relay

The image also supports built-in …

  • gLiveView
  • topologyUpdater
  • slot leader logs

The details of which are here

71

Correct spelling for the era is Shelley, but I don’t run a pool, maybe the coders got it wrong, making this line correct…

72

This is entirely my mistake - thanks for pointing it out. I’ll fix the docs.

1 Like
73

Hey there,

This post was very helpful, thank you!
I’m creating a test pool in aws (since i’m most comfortable there) but I would love to build a pi setup, maybe I can pick your brain if I get stuck on something. :slight_smile:

Thanks,
Matt

74

Sure you can. If you use AWS you might as well use an arm64 image from them. They have CentOS8 on arm64 for example. In that way you can build docker images on AWS that will then run on your Pi as well.

Unfortunately, the upstream Nix build does currently not work on arm64 because of [BUG] - cardano-node build fails with “Segmentation fault” on aarch64

For the nessusio/cardano images I have a convoluted workaround that builds the arm64 derivation through Docker (instead of Nix). Once I have the the binaries for the node & cli a normal Nix build can continue.

If you like this work, you may want to endorse this [CIP] - Provide high quality multiarch docker image and k8s support. The PRs that I have so far are here

76

Hello there!

Here is an update of the pool situation, as this is its introduction page after all :smiley:

The first post mentions that I used one RPi 4GB. This was true only during ITN, back in April 2020.
Since Shelley, I’ve been using two RPi 8GB.

Building this pool with my two Raspberry Pi has been a wonderful journey.
But as improvements on the Cardano protocol keep coming, I find it hard to rely on them solely. I’ve noticed that transitions between epochs often result in CPU/RAM overload, giving a hard time for the Pi, especially the one that hosts two relays and the block-producer.
This situation made me miss a block that was scheduled very early in epoch 251, I have to be honest.

Thanks to IOG delegation program that started in february 2021, I’ve been able to produce 11 blocks.
So, I decided to use part of the received rewards to buy a barebone server with the following specs :

CPU: Intel i5-8259U Quad-Core 2.3GHz
RAM: Corsair 16 GB DDR4 2400 MHz
SSD: Corsair MP510 960GB

This newcomer is dedicated to be the block-producer, nothing more. It runs since mid-epoch 251, the transition with epoch 252 was totally smooth and it has produced its first block this morning.
No relay runs on it, even if it’s powerful enough. I keep this tasks for the RPi. The one that used to run two relays and the block-producer feels better now ^^
Another bonus that comes with this new architecture is the extra layer of security as the block-producer now sits behind the relays, not next to one as it used to be.

2 Likes