Hi Alex,
thank you very much for your extra work hier, without you it would have been very difficult for many of SPO’s.
I do not understand why you recommend two wallets , one new created for taxes and one imported for pledge. Isn’t it simpler and safer just one (the imported one) for both? (I’m in this point ( STEP 5)now )
Tx!
If will be easier for u then ucan import one single wallet and use it for both
I said to have differents wallets because each time when u will want to modify the pool or … perform any transaction u will need the wallet files uploaded to server… will be more secure or better say less painfull if some one will hack ur server and will steal the wallet files … it will steal only few ada
But again… if u feel more confortable with only one wallet u can use one single wallet
and u will need 2 wallets in case u will use hw wallet for pledge… because hw wallet can’t be used as pool wallet
@Alexd1985 thanks for sharing.
I’ve read your tutorial, and I don’t see that you utilize the kubernetes stack. Is the kubernetes for cardano stake pool an overkill stack?
Using kubernetes we can guarantee the high availbility of the stake pool service, even if your VPS provider has 99,9% uptime, what is your strategy to update the cardano-node?
Already updated, updated first on my relay for test… passed stress tests.
Regarding the kubernetes… I don’t use… I have my Producer at home, connected to 1 public relay and other private nodes (which can be started as a Producer if the main one has issues)
Do you have a fix IP address at home? My public IP at home is not static. Since the relay node also need the IP of the producer in the topology file, a fix IP address for the producer node at home is mandatory, isn’t it?
I have static IP but it will not be an issue if u don’t have… u will need to edit the relay topology updater script each time when the Producer IP change… but I guess it’s not happening often… right?
It’s more problematic for relays… because u will need to wait 3 hours … if the IP will change
Sorry, if I missed it somewhere, but is there a way to disable the guild scripts from auto-updating, or locking them to deployed tag?
I want to update to 1.26.1 later, when I prep properly, but the tools auto-updated.
Guild scripts has now been upgraded to support cardano-node 1.26.0 or higher (1.25.1 found).
Please update cardano-node (note that you should ideally update your config too) or use tagged branches for older node version.
I confirmed the update, not looking to roll back, but more for future reference. Does downloading the prereqs.sh from a tagged branch help (not direct download, but git clone)?
I mean, I have create on the producer server two wallets, one new for taxes and registry fees and another imported from Daedalus special only for pledge.
When I visit my Daedalus on desktop I see that is possible to stake this pledge-wallet ADA to my own pool from the pool list.
I wonder if make sense and if is possible at all.
U should delegate from daedalus but if u imported the wallet and pledged it should be already delegated… check the wallet pledge address on cardanoscan.io
Hey,
can you tell me where to find information on how to connect my BP to my relays via IPv6? If I set IP_VERSION=mix in the env file, the node no longer starts.