Cheqd Airdrop Review: The authentic Data network

About Cheqd Airdrop

Cheqd Airdrop is a blockchain network, built in the Cosmos ecosystem, designed to do three core things: to enable people and organizations to have digital, trustworthy interactions directly with each other, whilst maintaining privacy and without any centralized registry or organization needed, to facilitate new business models for decentralized identity and Verifiable Credentials, through the use of token, $CHEQ, to bridge the DeFi ecosystem with the decentralized identity ecosystem, for better user experiences, democratic governance, regulatory compliance and operational efficiency.

Cheqd is airdropping free CHEQ tokens to ATOM, JUNO, OSMO and CHEQ stakers. The snapshot of ATOM, JUNO and OSMO stakers was taken on March 10th, 2022 and the snapshot of CHEQ stakers was taken on March 18th, 2022. Users who staked at least 10 ATOM, 20 JUNO, 20 OSMO or 100 CHEQ by the snapshot date are eligible to claim the airdrop.

Solution For You

We give you back privacy and control of your data.

Your data shouldn’t be in silos waiting to be leaked or stolen. Companies shouldn’t make money selling your data without your consent. The network allows SSI companies to build and deliver secure solutions to you.

New business models for verifiable credentials .

They help companies create new and innovative business models, ensuring self-sovereign identity is a viable and rewarding service to offer to customers. 

Using cheqd

Once installed, cheqd-node can be controlled using the cheqd Cosmos CLI guide.

Currently supported functionality

Basic token functionality for holding and transferring tokens to other accounts on the same network

Creating, managing, and configuring accounts and keys on a cheqd node

Staking and participating in public-permissionless governance

Governance framework for public-permissionless self-sovereign identity networks

Creating did:cheqd method DIDs, DID Documents (“DIDDocs”), and querying full DIDDocs

Cheqd Cosmos CLI

There are two command line interface (CLI) tools for interacting with a running cheqd-node instance:

• cheqd Cosmos CLI: This is intended for node operators. Typically for node configuration, setup, and Cosmos keys.
• Verifiable Data Registry (VDR) Tools CLI: This is intended for carrying out interactions related to decentralised identity / self-sovereign identity (SSI) functionality.

Upcoming functionality

A non-exhaustive list of future planned functionality (not necessarily in order of priority) is highlighted below:

• Creating and managing Verifiable Credentials anchored to DIDs on cheqd mainnet
• Querying DIDDoc fragments and specific resources
• Defining persistent Schemas that can be referenced using DIDs

They plan on adding new functionality rapidly and on a regular basis and welcome feedback on cheqd Community Slack workspace.

Developing & contributing to cheqd

cheqd-node is written in Go and built using Cosmos SDK. The Cosmos SDK Developer Guide explains a lot of the basic concepts of how the cheqd network functions.If you want to build a node from source or contribute to the code, please read our guide to building and testing.

Creating a local network

If you are building from source, or otherwise interested in running a local network, we have instructions on how to set up a new network for development purposes.

Client-app Identity APIs

This page describes how identity domain transactions need to be implemented by client-side applications/libraries such as cheqd-sdk (forked from Evernym VDR Tools). Details on how identity transactions are defined is available in ADR 002: Identity entities and transactions.

Architecture Decision Record (ADR) Process

This is a location to record all high-level architecture decisions for cheqd-node, the server/node portion of purpose-built network for decentralised identity.

An Architectural Decision (AD) is a software design choice that addresses a functional or non-functional requirement that is architecturally significant.

An Architectural Decision Record (ADR) captures a single AD, such as often done when writing personal notes or meeting minutes; the collection of ADRs created and maintained in a project constitute its decision log.

Rationale

ADRs are intended to be the primary mechanism for proposing new feature designs and new processes, for collecting community input on an issue, and for documenting the design decisions. An ADR should provide:

• Context on the relevant goals and the current state
• Proposed changes to achieve the goals
• Summary of pros and cons
• References

Reporting a Vulnerability

If you think you have discovered a security issue in any of cheqd projects, we’d love to hear from you. They take all security bugs seriously. If confirmed upon investigation, we will patch it within a reasonable amount of time and release a public security bulletin discussing the impact and credit the discoverer.

Get in touch

The team will be happy to talk about network and your project. Get in touch and let’s collaborate. Be part of revolution.