githubEdit

0.6.x

Read about the major cheqd network upgrades, moving to version 0.6.x

This list contains all stable releases in the cheqd-nodearrow-up-right v0.6.x family, and skips pre-release versions.

v0.6.10arrow-up-right: Genesis export fixes [December 2022]

Read Full changelog on GitHub: cheqd-node v0.6.10 release notesarrow-up-right

v0.6.9arrow-up-right: "Dragonberry" security vulnerability patch [October 2022]

The following steps have been prepared by the cheqd development team for cheqd validators to follow in order to manually upgrade their node.

This is in response to a high-risk security vulnerability (dubbed "Dragonberry")arrow-up-right related to IBC protocol / ICS23.

This is closely related to the "Dragonfruit" security vulnerability published on Cosmos forumsarrow-up-right. v0.6.9 fixes this vulnerability by patching to Cosmos SDK v0.45.9arrow-up-right upstream.

Considerations

This patch is non-state-breaking. This means that validators can switch to the new binary, and restart their node without necessarily needing an on-chain software upgrade (which is intended for consensus-breaking changes).

The patch has already been applied to cheqd's own validator nodearrow-up-right and one of the other large validators (at the time of writing this).

Read Full changelog on GitHub: cheqd-node 0.6.9 release notesarrow-up-right

v0.6.7arrow-up-right: Multi-platform builds [August 2022]

Read Full changelog on GitHub: cheqd-node v0.6.7 release notesarrow-up-right

v0.6.1arrow-up-right: Installer and Docker fixes [August 2022]

Read Full changelog on GitHub: cheqd-node v0.6.1 release notesarrow-up-right

v0.6.0arrow-up-right: DID-Linked Resources & Tooling for an Improved Developer Experience [July 2022]

Here’s what’s new in the latest cheqd node version - v0.6.0. This release is a state-breaking update that brings fundamental changes to the cheqd-node testnet and mainnet. The release notes below pertain to the cheqd-node changes only.

Summary

This upgrade includes 3 primary enhancements and new features, each of which helping accelerate cheqd to support a greater number of credential formats & SDKs, more use cases for decentralised identity applications and streamline the end-to-end developer experience.

  1. Implementation of a Resources module, used to support DID-Linked Resources

  2. Introduction of an Interactive Installer to streamline the developer onboarding experience

  3. Introduction of Cosmovisor for automated upgrades.

Feature Deep-dive

1. Implementation of a Resources module, used to support DID-Linked Resources

What's changed?

The concept of resources in self-sovereign identity (SSI) ecosystems is not new, however, as we will discuss throughout this blog post, existing approaches to resources in SSI oblige adopters to make compromises between security, availability and interoperability. We first noticed this when we were looking at how we could securely reference credential schemas, something we will expand on throughout this post.

Our objective in building resources on cheqd is to improve the way resources are stored, referenced and retrieved for our partners and the broader SSI community, in line with the existing W3C DID Core standardarrow-up-right.

An initial use case for DID-Linked Resources is supporting AnonCreds on cheqd. This is an industry first as AnonCreds have to date been tightly bedded to the Indy ledger. We are using the Resources module to create DID-Linked Resources for schemas and CredDef, bringing AnonCreds support to the cheqd ledger in a W3C compliant format.

Please take a look at our blogarrow-up-right which provides a thorough explanation for your reasoning on this approach, and links to our documentation.

2. Introduction of an Interactive Installer to streamline the developer onboarding experience

What's changed?

Prior to this upgrade, we offered developers looking to setup using a Ubuntu .deb package file and installing a with Dockerarrow-up-right

Although these were fit for purpose, allowing the vast majority of validators on the cheqd network to get set up these methods do require a higher level of technical skillset, and are more time-consuming.

The Interactive Installer offers a more intuitive and simple developer experience, which guides developers through a step-by-step journey, asking questions with the CLI along the way.

Find out more about how to get started using the Interactive Installer herearrow-up-right.

3. Introduction of Cosmovisor for automated upgrades

What's changed?

With an increasing number of validators on the cheqd network, we wanted to provide developers managing nodes the opportunity to more easily upgrade their node.

Cosmovisorarrow-up-right is a small process manager for Cosmos SDK application binaries that monitors the governance module for incoming chain upgrade proposals. If it sees a proposal that gets approved, cosmovisor can automatically download the new binary, stop the current binary, switch from the old binary to the new one, and finally restart the node with the new binary.

Full changelog

Read on GitHub: cheqd-node v0.6.0 release notesarrow-up-right

Features

Bug fixes & patches

CI/CD

Testing

Documentation

Last updated

Was this helpful?