Guild Tools Announcements

2023-03-18 07:52:41 FYI - Node 1.35.6 is not being updated on binary list on guild repo until we have more details about ongoing [potential] issue with disconnection against local peer with mixed (P2P and non-P2P mode) topologies. This does not mean node isn't stable, but would want to avoid possibly double update in case there is indeed an issue.

You may download pre-compiled binary for 1.35.6 outside of guild-deploy if needed via links on cardano-node releases page (extract cardano-node binary to ~/.local/bin folder , and restart node to do so).

We will send an update announcement prior to making guild-deploy use newer version of pre-compiled binaries for download option, when verified. Buka / Bagaimana

2023-01-28 02:41:50 Hi Folks, Greetings! It has been a while since our last update. As some of you might have known, we had been working on revamp of the scripts and are now a step closer to the target we'd like to see them to be, by merging it to alpha branch and open it for… Buka / Bagaimana

2023-01-20 03:31:21 Hi Folks,

Greetings! It has been a while since our last update.

As some of you might have known, we had been working on revamp of the scripts and are now a step closer to the target we'd like to see them to be, by merging it to alpha branch and open it for testing to advanced users.


If you are not an advanced user (who'd like to test or contribute to repo with Issue/PRs) for tools, you should stick to master branch (running tools with -b master), no changes yet.
If you are a Koios user, you do not need to make any changes yet if you're using a tag.

For those who would like to participate, we would recommend to do this on non-mainnet network first.

The overall flow of scripts remains the same. A summary of what's changing (now on alpha):
- prereqs.sh is being deprecated (not removed yet) and replaced by new guild-deploy.sh, the new script will start with less and only deploy what it's asked. This will allow you to skip build dependencies like ghc , cabal deployed on to machines that are only downloading binaries.
- As part of guild-deploy.sh, we add new parameter to allow you to download pre-compiled binary if you'd like to - as some were found to be compiling binaries on every machine instead.
- Improve handling of top-level folder for scripts.
- Consolidate binaries into ~/.local/bin (previously , different compilers and guides had binaries spread to different locations)

For existing users interested to help out with testing and performing the upgrade, we have compiled a 1-time upgrade guide trying our best to help you with the upgrade (note that for now , the branch reference is alpha - not master).

Please create an issue (PRs are welcome too) should you have any trouble or suggestions to update in the guides.

Lastly - when encountering an issue, we would request you to not use solutions from forum/alternate-guides if they request making edits in the file - instead try to raise an issue as above. We've often found folks being suggested to make changes to dynamic content of scripts and as part of the change, turn off auto-updates (in some cases, those changes were addressed simply by setting corresponding variable in env file). Buka / Bagaimana

2022-10-05 10:58:24 Hi All,

For those using alpha branch (thus, hopefully non-production networks), there was an issue introduced with previous env file update. The impact of that issue was to future updates - if you had already gone through the previous update from alpha, your env file might prevent future updates atm by replacing target files with empty ones.

To resolve, you can replace env from backup taken automatically prior to update and then start your tools again. Alternatively , you can use the below snippet :
cd "${HOME}"/tmp
curl -sf https://raw.githubusercontent.com/cardano-community/guild-operators/alpha/scripts/cnode-helper-scripts/prereqs.sh -o prereqs.sh
chmod 755 prereqs.sh
# please add -n -t depending on your instance
./prereqs.sh -s -b alpha

If using prereqs, ensure to revert your config/topology if changed using the latest backup that will be created, your script variables should remain intact.

Apologies for the unforeseen inconvenience to the testers.

1.4K viewsedited  07:58

Buka / Bagaimana

2022-10-01 11:42:49 Hi All,

Just a heads up , CNTools 10.0.4 is being merged to master shortly. The release will fix token mint/burn issue reported recently, but also start integrating with Koios API v1.0.7. For users using CNTools in online mode with Koios, this update would be essential, as older versions will no longer be able to fetch balance from old endpoints

A reminder for those who might've missed - if you do not want CNTools to connect to internet or to koios, you can still do so - please check this post on how to turn connection to Koios off Buka / Bagaimana

2022-09-23 01:09:47 Update to previous CNCLI announcement

Before running leaderlog force command, please execute below command to clear any previous blocks added.
. scripts/env offline
sqlite3 "${BLOCKLOG_DB}" "DELETE FROM blocklog WHERE epoch=365;" Buka / Bagaimana

2022-09-22 12:06:28 CNCLI leaderlog Vasil HFE 1-epoch edge case

The reason:
Cardano mainnet merge into Babbage era 22 Sep @ 21:44 UTC. One of the changes is that we go from TPraos(Transitional Praos) to Praos ouroboros consensus. Due to this change, cncli has a new --consensus parameter that sets the correct type.

The problem:
The cncli.sh wrapper script in Guild script suite has this parameter implemented, but there is an edge case for the transition. As leaderlog is calculated before the HFE occur, the wrong consensus for upcoming epoch is identified.

The solution:
Make sure that you have the latest version of cncli.sh wrapper script deployed. Also make sure to run the latest version of cncli binary, v5.1.2 as of this message. Both can be deployed/updated using prereqs.sh script.
After HFE event, ie after crossing into epoch 365, run the below command from the scripts folder to re-calculate leaderlog for current epoch.
./cncli.sh leaderlog force

Optional:
If pooltool sendslots is active, you might also want to run the below command to force submission of slots to pooltool after calculating correct leaderlog.
./cncli.sh ptsendslots force Buka / Bagaimana

2022-08-24 05:31:30 Hi All, Now that community stepped up and performed the tests for scripts, we will be moving forward with merge from alpha to master branch in next 24 Hours. It is still recommended you go through atleast preprod network using 1.34.1 to 1.35.3 before touching… Buka / Bagaimana

2022-08-21 08:17:41 Hi All,

Now that community stepped up and performed the tests for scripts, we will be moving forward with merge from alpha to master branch in next 24 Hours.

It is still recommended you go through atleast preprod network using 1.34.1 to 1.35.3 before touching mainnet, as we should not be having to answer basic usage issues from SPOs post upgrade.

Once the merge to master is done , you may receive a prompt for update of scripts next time you startup tools ...

ONLY select Yes, if you've already upgraded to 1.35.3, select No if you haven't

There isn't a need to rush, there are no close deadlines, so take your time and be sure that you've upgraded as per your comfort using preprod Environment. There can be other (for instance, p2p networking improvements) that might still be discovered, but the primary risk holding us back putting network at risk has been proven to be safe

The intention of this message is purely to give early notice for folks pre-update, no actions expected yet. We will follow this up with another message once merged. Buka / Bagaimana

2022-08-15 12:15:36 Hey All,

We've added initial support for Pre-Prod and Preview environments to guild-operators alpha branch, that is in-line with IO's new strategy for updates.

Below is a short summary in case missed:

- Testnet:
Due to an issue introduced in node 1.35.1 , fixed at 1.35.2, the current public testnet had invalid block that did not pass ledger rules - making any new nodes fail verification when attempting to sync. Thus, this testnet is limited to 1.35.2 version only - and is already considered legacy. The support for this testnet will gradually be removed (will make another post about removal with enough heads up when the time comes)

- New Replacements for Testnet:
The role of testnet will now be split amongst 2 networks : Pre-Prod and Preview. The intention from IO is to have any future updates to preview 4 weeks prior preprod/mainnet, while preprod will be treated similar to mainnet. Note that Preview network may be re-spun during forks should there be an issue. The node version to be used for this network should be 1.35.3

- Temporary Dev-Nets:
Other than the above, there are some temporary networks that will short-lived (vasil-dev, shelley-qa, etc) - these are only meant for advanced users who should be aware of how to update configs and specific files. There will not be automation for these.

- Outcome for guild tools support:
Mainnet (currently 1.34.1 - master branch)
PreProd/Preview (1.35.3 - alpha branch)
Testnet (1.35.2 - alpha branch) <= will be retired in coming weeks/months, depending on activity and progress upstream Buka / Bagaimana