1.34.1 will not work on the testnet, anymore, because the testnet was already forked to Vasil and that needs 1.35.x. So, testnet should be 1.35.2 and 1.35.2 only, at the moment.
After this chaos has settled a bit and probably after the mainnet has successfully been forked, they will probably rebuild the testnet from scratch. But there should be announcements on that.
To build a new cardano-node version, you will typically follow https://cardano-community.github.io/guild-operators/Build/node-cli/. But, since you need a very specific version, you should replace git checkout $(curl -s https://api.github.com/repos/input-output-hk/cardano-node/releases/latest | jq -r .tag_name) by git checkout 1.35.2. (Personally, I do not know if blindly using the latest release â as the command in the guide does â is such a good idea at all.)
Since you mention wanting to continue to learn, Iâd recommend to try to understand what you are doing while following these guides. If you are not already familiar with Unix/Linux, try to learn some of that in parallel. A lot of questions that we get here are not primarily Cardano-related, but often come down to something like: âWhich program in the $PATH gets executed?â, âWhen is which environment variable set by whom?â, âIs your cardano-node socket path set in your .bashrc?â, âAre the files where this specific helper script expects them?â Having a working knowledge of Linux helps a lot with these.
Thank you @HeptaSean for the information, I will work to upgrade my node to 1.35.2.
With respect to the guide, yes, I followed it from the beginning. This is not the only I guide I have used to learn. I have used many to formulate my own internally that I will use when I move to Mainnet. I have landed on theirs since I have re-built my node a few times through my testing.
I am know Linux expert, but know enough to understand what you wrote above. I can humbly admit I still have a lot to learn. Upgrading shouldnât be too tough, especially the relay. My concern was the BPNâs wallet and pool.
@Alexd1985, going back to the minting blocks issue. Is there anything I can do to ensure my pool is configured correctly to mint blocks? Do I need to wait for another epoch since my pool was down?
should work by default, if not perhaps u will need to update the path for vrf file inside cncli script
#POOL_ID="" # Automatically detected if POOL_NAME is set in env. Required for leaderlog calculation & pooltool sendtip, lower-case hex pool id
#POOL_VRF_SKEY="" # Automatically detected if POOL_NAME is set in env. Required for leaderlog calculation, path to pool's vrf.skey file
#POOL_VRF_VKEY=""
run deploy-as-systemd and press N for topology updater and for pooltool (there are 2 services, sendmytip and another one⌠send blocks or something like that) and yes for cncli and the rest⌠then restart the node and check the sync process
sudo system | grep cncli
then with sudo systemctl status (sync service)
this way it will be always 100% synced and it will check automatically leaderlog
The total tADA staked to the pool is 29.49k. I have 3 testnet wallets staking ~3.5k each. The pledge is 10k. The BPN wallet currently has 18.9k tADA staked.
I did the above without issue, but was still not able to get leader log to fully sync. I then renamed guild-db to guild-db.old and restarted the cncli service. I believe that did it, now the sync continued to grow and reached 100%. Does this mean my pool could be selected to produce blocks on Testnet?
Perfect, u can delete the folder renamed⌠now, the stake is to low to create blocks, open another tipic and ask for someone to send some tADA to u to ur pool address or to stake to ur pool,
Thanks @Alexd1985 really appreciate all the help you provided. One last question, what are you recommending for a total staked amount to produce blocks? 100k? I only ask to understand the minimum requirement I am trying to meet.
