coincashew / coincashew Goto Github PK

I would like to contribute a script that I've created to validate a kes rotation to this section
It records the existing kes, and when a rotation is performed it will validate that the necessary files have changed, and that the node counter in the certificate is as expected.

The script can be found on my github page https://github.com/ada-piggy-bank/pool-utils

Hello, big fan of guide-how-to-build-a-haskell-stakepool-node, went through it step by step and my issues are:

1. gLiveView.sh i get up to syncing (98.2%) but then seem forever stuck.

2. Even after reading "Before continuing, your node must be fully synchronized to the blockchain. Otherwise, you won't calculate the latest KES period" I went ahead at 98.2% synced to see what error would come next.

3. No errors but when I restarted with:

KES=${DIRECTORY}/kes.skey
VRF=${DIRECTORY}/vrf.skey
CERT=${DIRECTORY}/node.cert

I didn't go back to 98.2% the status from gLiveView now says "starting..."

My producer:

$ lsof -nP -i | grep LISTEN
cardano-n 1082            root   16u  IPv4  18821      0t0  TCP 127.0.0.1:12788 (LISTE)
cardano-n 1082            root   18u  IPv4  20207      0t0  TCP 127.0.0.1:12798 (LISTE)
cardano-n 1082            root   23u  IPv4  23646      0t0  TCP *:6000 (LISTEN)

My relay:

$ lsof -nP -i | grep LISTEN
cardano-n 1949            root   16u  IPv4  25291      0t0  TCP 127.0.0.1:12788 (LISTE)
cardano-n 1949            root   18u  IPv4  27038      0t0  TCP 127.0.0.1:12798 (LISTE)

Do I need something running on 6000 on the relay machine too?

Hello,
would you be interested in adding to the guide an automated way to run cardano-cli query leadership-schedule for next epoch?

I created a script that can do that job with cron.
Basically it calculate the time when the leadership-schedule check for the next epoch is doable (around 75% or 1.5 days before epoch ending) and then it runs the command automatically.

You can find it here https://github.com/Techs2Help/leaderScheduleCheck_cron

Let me know, I would be really happy to contribute to this guide that helped me so much :-)

Edit:
Added an extra if cause the cronjob didn't work as expected (in case that you have already checked). Sorry for the inconvegnence

Your /etc/fstab entry for this topic sets the tmpfs mount to READ-ONLY! Perhaps I'm missing something, but read-only shared memory would not be very useful - someone needs to be able to write to it for there to be anything to read. :) I believe the most flexible and secure mount options are : rw,noexec,nosuid,nodev . Note that Google Chrome, for instance, requires write access to shared memory to run, and there's no reason to believe that other applications would reasonably expect to have r/w access to this common system resource. To set shm to read-only is equivalent to not having it mounted at all at runtime. Also, some linux distros, e.g. Ubuntu, set the mount point to /dev/shm, not /run/shm, and then symlink /run/shm -> /dev/shm, so the /etc/fstab on those systems should be mounting tmpfs on /dev/shm, not /run/shm.

I have found on AWS Linux and presumably CentOS, you need to run the following after building libsodium

sudo ldconfig

Ref: https://www.coincashew.com/coins/overview-ada/guide-how-to-build-a-haskell-stakepool-node

Hi I was using your docs for my entire pool.

I had a TX error when withdrawing my retired pool, so I pasted the commands again but erroneously copied the destination address.

I accidentally sent my 512 ADA deposit to your address :( I retired the pool due to family medical fees.

You can see my transaction here: https://cardanoscan.io/address/addr1qxjtvm463f20swd8g0cldhe0wgnn5lunj4nayrpsclg86dv02ewj3tph9wkj9ky505alt4c8jcpvvgcmetd3g74l2u9salmhnq

To your address: addr1qxhazv2dp8yvqwyxxlt7n7ufwhw582uqtcn9llqak736ptfyf8d2zwjceymcq6l5gxht0nx9zwazvtvnn22sl84tgkyq7guw7q

If possible please you can you return the 512 ADA to my address (the sender)? however please take 30 ADA off as support to your wonderful articles, as a goodwill gesture and for the inconvenience.

Wishing you a pleasant day.

AdaCharityPool

Hi there @coincashew ,

I hope this finds you well. First of all I would like to thank you for the great work on the guide to set up a Cardano stake pool. It was of great assistance!

I would like to add a little something to Section 18.6 Auto-starting with systemd. The code published there is as follows:

cat > $NODE_HOME/cardano-node.service << EOF
#The Cardano node service (part of systemd)
#file: /etc/systemd/system/cardano-node.service

[Unit]
Description = Cardano node service
Wants = network-online.target
After = network-online.target

[Service]
User = $(whoami)
Type = forking
WorkingDirectory= $NODE_HOME
ExecStart = /usr/bin/tmux new -d -s cnode
ExecStartPost = /usr/bin/tmux send-keys -t cnode $NODE_HOME/startBlockProducingNode.sh Enter
ExecStop = killall cardano-node
Restart = always

[Install]
WantedBy = multi-user.target
EOF

Following some discussions on the Cardano Forum with other SPOs, I took the liberty of modifying the above to this:

[Unit]
Description = Cardano service
#Wants = network-online.target
After = network.target

[Service]
User = $(whoami)
Type = forking
WorkingDirectory= $NODE_HOME
ExecStart = /usr/bin/tmux new -d -s cnode
ExecStartPost = /usr/bin/tmux send-keys -t cnode $NODE_HOME/startBlockProducingNode.sh Enter
#ExecStop = killall cardano-node
KillSignal=SIGINT
RestartKillSignal=SIGINT
TimeoutStopSec=2
LimitNOFILE=32768
Restart=always
RestartSec=5

[Install]
WantedBy= multi-user.target

Whereas the change from After=network-online.target to After=network.target has produced no discernible results, the change of the ExecStop=killall cardano-node to KillSignal=SIGINT and RestartKillSignal=SIGINT produced a much faster reboot time for cardano-node. It seems that SIGINT will help gracefully exiting cardano-node, thereby drastically reducing the restart time. In my case the nodes would take between 3-5 minutes to restart (on machines that exceed the minimum requirements) before this slight change, now more in the order of 15 seconds.

Do you have any data that may show otherwise? Can you think of other elements in the code above that may have affected such big change in restart time?

I would like to thank Robert Phair (@COSDpool) https://forum.cardano.org/u/cosdpool/summary for his input regarding this matter.

Please let me know if you require more information at this time.

Regards,

Adrem https://forum.cardano.org/u/adrem/summary

When a wallet contains a native token the loop used for scraping the ADA total from the wallet causes an error when submitted. All UTXOs are used, which results in native tokens being included in the tx_in. Since they are not comparable to ADA, they also need to be in the tx_out. If native tokens (nfts) are used in the tx_in without being considered in the tx_out you receive the ValueNotConservedUTxO error.

Command failed: transaction submit Error: Error while submitting tx: ShelleyTxValidationError ShelleyBasedEraBabbage (
ApplyTxError [
UtxowFailure (
UtxoFailure (
FromAlonzoUtxoFail (
ValueNotConservedUTxO (
Value 9173755183 (
fromList [(
PolicyID {policyID = ScriptHash "ad79da159614ff55130b3a28189fbe5c429"},
fromList [(4b6964646f,1)])])) (Value 9173755183 (fromList [])))))])

At https://github.com/coincashew/coincashew/blob/master/coins/overview-xmr/guide-or-how-to-run-a-full-node.md there are references to ports 18081 and 18089. There is no explanation about why ports are mentioned. The information I have found suggests that the guide should explain that 18089 and 18081 serve the same purpose in two different contexts and that which one you use depends on whether or not you want the p2p network to broadcast your node to the public (and their wallets that need an open node). I am GUESSING that 89 is for public nodes that want to be broadcast, and if someone confirms my guess (hopefully with some explanation in the guide itself), then I will make some more progress in supporting the Monero network. Thanks!

the MD5 does not match anymore

10. Setup payment and stake keys
    Above section must be updated to mary era as below.
    Looks like this is relevant in more than one location

cardano-cli query protocol-parameters \ --mainnet \ --mary-era \ --out-file params.json

I would like to contribute by translating the How to Build a Cardano Stake Pool Guide into Spanish. This is the final translated guide Please let me know if y'all are interested in this. Thanks :)

Please consider adding to the guide a way to implement the detailed blocklog from cntools to gliveview but without installing cntools. Thanks in advance.

(very new to this, please forgive me if I am not doing this right)
Md5 hash for qcpolsendmytip.sh is mismatched.

Hash provided in doc: f7646132e922b24b140202e5f5cba3ac
Actual Hash: 25e6a4412560a72d19bbde957a660ee5

//xxxx@C222-BlockProd:~/cardano-my-node$ md5sum qcpolsendmytip.sh
25e6a4412560a72d19bbde957a660ee5 qcpolsendmytip.sh

Line: 3095

Hello

Maybe an issue here

we had a user trying to follow the guide and complaining about not being able to start the BP node

I think there's a regression.

this

block producer node

cat > $NODE_HOME/startBlockProducingNode.sh << EOF 
#!/bin/bash
DIRECTORY=$NODE_HOME
PORT=6000
HOSTADDR=0.0.0.0
TOPOLOGY=\${DIRECTORY}/${NODE_CONFIG}-topology.json
DB_PATH=\${DIRECTORY}/db
SOCKET_PATH=\${DIRECTORY}/db/socket
CONFIG=\${DIRECTORY}/${NODE_CONFIG}-config.json
KES=\${DIRECTORY}/kes.skey
VRF=\${DIRECTORY}/vrf.skey
CERT=\${DIRECTORY}/node.cert
/usr/local/bin/cardano-node run +RTS -N -A16m -qg -qb -RTS --topology \${TOPOLOGY} --database-path \${DB_PATH} --socket-path \${SOCKET_PATH} --host-addr \${HOSTADDR} --port \${PORT} --config \${CONFIG} --shelley-kes-key \${KES} --shelley-vrf-key \${VRF} --shelley-operational-certificate \${CERT}
EOF

should be changed to

cat > $NODE_HOME/startBlockProducingNode.sh << EOF 
#!/bin/bash
DIRECTORY=$NODE_HOME
PORT=6000
HOSTADDR=0.0.0.0
TOPOLOGY=\${DIRECTORY}/${NODE_CONFIG}-topology.json
DB_PATH=\${DIRECTORY}/db
SOCKET_PATH=\${DIRECTORY}/db/socket
CONFIG=\${DIRECTORY}/${NODE_CONFIG}-config.json
/usr/local/bin/cardano-node run +RTS -N -A16m -qg -qb -RTS --topology \${TOPOLOGY} --database-path \${DB_PATH} --socket-path \${SOCKET_PATH} --host-addr \${HOSTADDR} --port \${PORT} --config \${CONFIG}
EOF

KES, VRF and CERT are referenced but node is not even bootstrapped and can't start as Block Producer. Those files are created afterward.

After running the

./gLiveView.sh

I have got the following error

Failed to query protocol-parameters from node, not yet fully started?

ERROR: CNTools failed to load common env file
Please verify set values in 'User Variables' section in env file or log an issue on GitHub

In the documentation it's written that "A node must reach epoch 208 (Shelley launch) before gLiveView.sh can start tracking the node syncing. You can track the node syncing using journalctl before epoch 208."

Is this error message related to that? If it's the case, how can we check the epoch? Can we add that to the documentation

100 Thx

The ETH2 testnet guide was updated for Prater, but IMO it should still suggest Pyrmont. Prater is intended as a stress-testing environment for client devs, and its performance for users is currently suboptimal. For example, the highest ranked validator at time of writing only has 60% attestation effectiveness due to blocks being full!

Alternatively, if reverting the Prater guide back to Pyrmont isn't desirable, then hosting two copies of the guide (and recommending Pyrmont) would be good.

PS: Thanks for the awesome guide! ❤️

The python script to calculate leader slots is deprecated and users need to migrate to cncli: https://github.com/AndrewWestberg/cncli

https://github.com/papacarp/pooltool.io/blob/master/leaderLogs/README.md

Running clean install of Ubuntu 18.04.5. Automatic startup of services fails per the current documentation. I had to do the following to correct systemd related issues:

1. Add to the top of startBlockProducingNode.sh:
   #!/bin/bash

2. systemd was throwing this error upon service startup:

cardano-node: error while loading shared libraries: libsodium.so.23: cannot open shared object file: No such file or directory

To correct:

sudo ldconfig

3. In startBlockProducingNode.sh, update:

DIRECTORY=$NODE_HOME

to

DIRECTORY=/root/cardano-my-node

Otherwise, systemd throws this error:

InvalidYaml (Just (YamlException "Yaml file not found: /mainnet-config.json"))

4. In cardano-node.service, I had to change:

WorkingDirectory= /home/root/
...
ExecStop        = killall cardano-node
ExecReload      = killall cardano-node && /root/cardano-my-node/startBlockProducingNode.sh

to

WorkingDirectory= /root
ExecStop        = /usr/bin/killall cardano-node
ExecReload      = /usr/bin/killall cardano-node && /root/cardano-my-node/startBlockProducingNode.sh

Also, it would be great to have documentation on how to connect to the service and view the "LiveView".

Hello,

I'm following the execution installation guide for Nethermind.

• I had to add WorkingDirectory=$(echo $HOME)/nethermind to the service file. Without that, the service stuck with "Waiting for peers". Taken from there.
• I also had to apply the fix described here.

I'm using Ubuntu 22.04 LTS. Thanks for all the effort you put into this.

Not sure if I can make corrections to typos or not, I tried to do a pull-request so I could make the change but it went on and on about permissions and such...

Pre-Announcements has an incorrect date (type) for guide version 3.2.1 for Cardano Release v.1.26.1
April 14 2020 should be April 14, 2021

Got much further this time! Synced to 100% no problem. But at the end of step 11:

ADA: 77754451
Total ADA balance: 77754451
Number of UTXOs: 1
stakeAddressDeposit: 2000000
fee: 184685
txOut: 77939136

I feel like I transferred enough ADA into my new payment address i.e. 77754451 and I read: "Ensure your balance is greater than cost of fee + stakeAddressDeposit or this will not work." And yet I get:

Command failed: transaction submit  Error: Error while submitting tx: ShelleyTxValidationError ShelleyBasedEraMary
 (ApplyTxError [LedgerFailure (UtxowFailure (UtxoFailure 
(OutsideValidityIntervalUTxO (ValidityInterva
l {invalidBefore = SNothing, invalidHereafter = 
SJust (SlotNo 10000)}) (SlotNo 27995504)))),LedgerFailure 
(UtxowFailure (UtxoFailure (ValueNotConservedUTxO 
(Value 77754451 (fromList [])) (Value 80123821 (fromList [])))))])

I see multiple people having issues on the gLiveView.sh step.

One major finding is that ./gLiveView.sh works once the node has synced past epoch 280.

Adding an info note or warning in Section : 8. Start the nodes would be useful.

Something along the lines of:

Note that the relay node and block producing node must reach epoch 208 ( Shelley launch) before gLiveView.sh can start tracking the node syncing. You can track the node syncing using journalctl before epoch 208.
#> journalctl --unit=cardano-node --follow

Thanks for the great guide!
Luis

Just curious if I'm missing something here. I've been following the guide for staking on ETH2 Mainnet (getting ready for Dec 1) - great job on the guide BTW! In the opening you state an assumption that you will be running the validator under a user called 'ethereum' - but in the eth1.service (and it appears to be the same in the other services) you use: User= $(whoami), which inserts my current user name into the .service file.

Did you mean to add a step to su to ethereum before hand, or should we just include User = ethereum and Group = ethereum in the .service files?

Also - I'm using an SSD that I recently installed for my chaindata (it seems that ETH1 is taking up a lot of space) so I also included the --datadir in the .service file. Do you foresee any issues with that?

https://www.coincashew.com/coins/overview-xmr/guide-or-how-to-run-a-full-node provides instructions that include downloading and starting monerod, but I did that before I followed those instructions. My monero folder is in my home directory and the service fails with:

monerod.service: Failed to execute /home/free/monero/monerod: Permission denied
monerod.service: Failed at step EXEC spawning /home/free/monero/monerod: Permission denied

I chowned everything in the data directory to the monero user that the guide said to make to see if that would help the service start, but it didn't. It did make it harder to start monerod the way I usually do, so then I did sudo -s (because somewhere I read that would give me an elevated shell, but now I'm not so sure it did...) and then I was able to start monerod. I want to run a public node but I'm not sure what to change. It might have something to do with my flavor of linux, so here's this:

    ~ > cat /proc/version
    Linux version 5.17.9-1-MANJARO (builduser@fv-az451-156) (gcc (GCC) 12.1.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT Wed May 18 09:20:53 UTC 2022
    ```

I am going to move my monero folder to the place where the instructions would have put them and see if that helps and then I'll report back here.

Currently the Guide shows the startup scrips for the block producer and relays as the same script. I believe the bp nodes should have some extra inputs like the keys and certs needed to be a block producer node. I'm posting a link down below for convenience.

https://www.coincashew.com/coins/overview-ada/guide-how-to-build-a-haskell-stakepool-node#7-create-startup-scripts

Script for block producer is shown as
cat > $NODE_HOME/startBlockProducingNode.sh << EOF #!/bin/bash DIRECTORY=$NODE_HOME PORT=6000 HOSTADDR=0.0.0.0 TOPOLOGY=\${DIRECTORY}/${NODE_CONFIG}-topology.json DB_PATH=\${DIRECTORY}/db SOCKET_PATH=\${DIRECTORY}/db/socket CONFIG=\${DIRECTORY}/${NODE_CONFIG}-config.json /usr/local/bin/cardano-node run --topology \${TOPOLOGY} --database-path \${DB_PATH} --socket-path \${SOCKET_PATH} --host-addr \${HOSTADDR} --port \${PORT} --config \${CONFIG} EOF

The following suggestion should be for "TraceMempool", not "TraceMemPool".

Tip for relay and block producer nodes: It's possible to reduce the number of missed slot leader checks, memory and cpu usage by setting "TraceMemPool" to "false" in mainnet-config.json

https://github.com/coincashew/coincashew/blame/master/coins/overview-ada/guide-how-to-build-a-haskell-stakepool-node/README.md#L306

Reference: line 43 of the most official mainnet config (at the time of writing):
https://hydra.iohk.io/build/7654130/download/1/mainnet-config.json

I made a script + service to update height on pooltool.io and I would like to add it to the guide (https://www.coincashew.com/coins/overview-ada/guide-how-to-build-a-haskell-stakepool-node) under section 18. Operational and Maintenance Tips.

I found some scripts that did it, but none that required no tweaks if you followed the tutorial so I created one. It comes with installation steps and is pretty much plug-and-play (wget 2 files (script + service) + some sed command to insert the pool id and api key).

I want to know if it's something that will be approved before starting the guide.

I stepped through the instructions in section 18.4 to update pool fees, and I am receiving the following error when I attempt to send a transaction:

Shelley command failed: transaction submit Error: Error while submitting tx: ApplyTxError [LedgerFailure (UtxowFailure (UtxoFailure (ValueNotConservedUTxO (DeltaCoin 2096421302) (DeltaCoin 2596421302))))]

I cannot find information on this anywhere, but it seems that the instructions are wrong; all help appreciated.

First of all thank you for your amazing work on all the guides.

I wanted to ask what is your position on creating separate non-login/non-root users for both the eth1 and eth2 clients?

In current version everything is ran under the same user, who is in addition in the sudo group.

Thank you!

The documentation says to generate your poolMetaData.json file, hash it, then upload it to git.io.

Git.io will change the json file and remove spaces and new lines.

This will cause IOHK to get a different hash than the one you use to generate your node.cert.

Recommended update:

1. Generate poolMetaData.json file
2. Upload to git.io (GIST)
3. wget the json back from that url
4. use cardano-cli to hash that downloaded version
5. Use that hash in the generation of the pool.cert

I'm referring to this part of the guide:

When https://epoch-api.crypto2099.io:2096/epoch/ is updated with the next epoch data, the slot leader schedule section in the guide is wrong.

For exemple, right now we're in epoch 247 and the URL above was updated with data of epoch 248.

If we follow the guide we will calculate the sigma value of epoch 247 with getSigma.py and use that value to calculate slot leader of epoch 248 with leaderLogs.py, but a pool's sigma is different between 2 epochs. This is because leaderLogs.py pokes the url above to get the epoch number if the --epoch parameter isn't specified (which the guide doesn't mention).

https://github.com/coincashew/coincashew/blob/master/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-mainnet/part-ii-maintenance/checking-my-eth-validators-sync-committee-duties.md

The script doesn't find validators which are supposed to be in sync committees. Possibly a little bug?

In this section https://www.coincashew.com/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-mainnet#9-start-the-validator

It says "Store your keystore password in a file and make it read-only". This is wrong. This should be the Prysm password.

In the "guide-how-to-build-a-haskell-stakepool-node":

Downloading "shelley_testnet-config.json", the "GenesisFile" is set to "shelley_testnet-genesis.json". I am getting errors, when I start the node, because it in the rest of the guide it is called "shelley_testnet-shelley-genesis.json". Maybe it was changed by IOHK recently?

I think it needs to be changed either in the config file after downloading or in the rest of the guide.

• rpc-http-enabled
• rpc-http-port 8545
• engine-rpc-port 8551
• rpc-ws-enabled

The error message I was getting that I think was related to not having these parameters:

• (lighthouse) tcp connection refused

pretty sure this step, which is listed to be done on the block producer node, should be done on the cold storage node. Then the stake cert copied from cold node to block producer. Thank you for the excellent guide!

Hello,

I'm not sure if this is an issue with the guide or an issue with what I'm doing, so please forgive me if it's my mistake...

In the guide, at 18.4: 'Changing the pledge, fee, margin, etc'

(https://github.com/coincashew/coincashew/blob/master/coins/overview-ada/guide-how-to-build-a-haskell-stakepool-node/18.-operational-and-maintenance-tips.md)

When at the final step, parsing the ledger-state.json in order to verify the changes, there is no output from the following command...

jq -r '.esLState._delegationState._pstate._pParams."'"$(cat stakepoolid.txt)"'" // empty' ledger-state.json

What should the output be? I've attempted to use the stake pool ID from a handful of other pools, which also has no output.

Kind regards
Adam

Correction of Accumulation

account command is deprecated for lodestar and there's a section for lodestar to load the key using account command

Commands:
beacon Run a beacon chain node
validator Run one or multiple validator clients
lightclient Run lightclient
account [subcommands.. DEPRECATED
]

Also --testnet isn't valid

✖ Unknown argument: testnet

Please explain how to update from 8.6.5 or overwrite.
https://docs.cardano.org/projects/cardano-node/en/latest/getting-started/install.html#

As --http-web3provider is deprecated and has been replaced with --execution-endpoint should this be part of the merge guide so there is no impact when the fallback is removed in the future?

fantastic guide and thank you for it! I just wanted to add something that seemed to help me when following your guide. On step "4.5 Start the beacon chain and validator", under [Service] add "ExecStartPre = /bin/sleep 30" so that it wants for eth1 geth for 30 seconds before running. Without that, I noticed the error message that the beacon chain couldn't connect to the :8545 service

1. First, it would be nice to mention this statement so that people can understand the logic of the thing:

As stated here:
Each snapshot is taken at the end of a different era. The go snapshot is the current one and was taken two epochs earlier, set was taken one epoch ago, and mark was taken immediately before the start of the current epoch.

2. Then, to my understanding, the script requesting info for the next epoch doen't agree with this logic. This command:

POOL_STAKE=$(echo "$SNAPSHOT" | grep -oP '(?<=    "poolStakeGo": )\d+(?=,?)')
ACTIVE_STAKE=$(echo "$SNAPSHOT" | grep -oP '(?<=    "activeStakeGo": )\d+(?=,?)')

should be replaced by

POOL_STAKE=$(echo "$SNAPSHOT" | grep -oP '(?<=    "poolStakeMark": )\d+(?=,?)')
ACTIVE_STAKE=$(echo "$SNAPSHOT" | grep -oP '(?<=    "activeStakeMark": )\d+(?=,?)')

Hello,

This section does not make sense.

destinationAddress=$(cat payment.addr)
echo destinationAddress: $destinationAddress

It should be about claiming and transferring your rewards to an external wallet (eg Daedalus, Yoroi). This looks like you transfer the rewards from the stakepool back to the stakepool.

The other article I have found also has issues:
https://docs.cardano.org/projects/cardano-node/en/latest/stake-pool-operations/withdraw-rewards.html

Shelley command failed: query stake-address-info Error: A query from a certain era was applied to a ledger from a different era: EraMismatch {ledgerEraName = "Allegra", otherEraName = "Shelley"}

Can you please correct it.

I would prefer to not log to syslog, since later I would like to send tip and block height to PoolTool, etc. and I don't know if I want to give the script access to syslog.

Do you know how to change where the service logs to?

Good day, Coincashew team!
My name is Angel and I recently set up a Cardano Stake Pool in a Raspberry Pi 4 in my hometown in Mexico by following your guide :)

As many people in my region are unable to understand most of the Documents and Guides for setting up the Stake Pool, I'd like to translate it and focus the guide around using the Raspberry Pi devices. I see there's already a translation for the full guide to Spanish, so my aim is only to translate it up to point 8, just before generating the Stake Pool Keys.

Let me know what you guys think about this proposal! Thanks for reading and have a great day!

before "lighthouse --version"
you need to "sudo cp /$HOME/.cargo/bin/lighthouse /usr/local/bin"

Can someone update how to get # MY_GRAFFITI='poapAAAAACGatUA1bLuDnL4FMD13BfoD'
and where to save this file?

https://github.com/coincashew/coincashew/blob/master/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-testnet-prater.md