<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ankur Banerjee on Medium]]></title>
        <description><![CDATA[Stories by Ankur Banerjee on Medium]]></description>
        <link>https://medium.com/@ankurb?source=rss-c5166068a656------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RscMXOfbIykD7HaBO0zi-w.jpeg</url>
            <title>Stories by Ankur Banerjee on Medium</title>
            <link>https://medium.com/@ankurb?source=rss-c5166068a656------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:24:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ankurb/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Pioneering Trust in the Age of AI: Introducing cheqd’s MCP-Enabled Agentic Trust Solution]]></title>
            <link>https://blog.cheqd.io/pioneering-trust-in-the-age-of-ai-introducing-cheqds-mcp-enabled-agentic-trust-solution-c26265c99384?source=rss-c5166068a656------2</link>
            <guid isPermaLink="false">https://medium.com/p/c26265c99384</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[mcp-server]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Ankur Banerjee]]></dc:creator>
            <pubDate>Mon, 07 Apr 2025 10:44:47 GMT</pubDate>
            <atom:updated>2025-04-07T10:44:47.113Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LTeM8uG9Feyknrldgp8fgg.png" /></figure><p>Imagine a world humming with AI agents — digital helpers managing your schedule, booking travel, executing transactions, even collaborating with each other. This future is rapidly approaching. But alongside the excitement comes a fundamental challenge: in a world increasingly reliant on autonomous AI, how do we establish <strong>trust</strong>? How do we <em>know</em> an agent is what it claims to be, that it’s operating securely, or that it has the right permissions for the tasks it performs?</p><p>To meet this challenge head-on, cheqd has developed a pioneering way to build verifiable trust directly into AI interactions. We are <strong>introducing cheqd’s Agentic Trust Solution,</strong> powered by the emerging <strong>Model Context Protocol (MCP)</strong>. This new system provides AI agents with verifiable digital credentials, allowing their identities and permissions to be cryptographically proven. By ensuring AI agents operate securely and accountably, we aim to foster an AI ecosystem that is both powerful and trustworthy.</p><p>Without clear answers, we risk building our AI future on shaky ground. We’ve been focused on <a href="https://cheqd.io/blog/how-verifiable-ai-enables-trust-for-ai-agent-adoption/?utm_source=medium&amp;utm_medium=social">building <strong>Verifiable AI (vAI)</strong> solutions for these emerging issues</a> for over a year at cheqd. From our market research and partnerships with AI companies (some existing, some prospective), we understand that one of the earliest issues that needs to be tackled is <strong>creating solutions for users and AI agents to understand which AI agents are trusted</strong>. This takes various forms such as:</p><ul><li>How does a user trust that an AI app or agent they came across is trustworthy and treats their data in a respectful manner?</li><li>How can an AI app/agent hold digital, cryptographically tamper-proof credentials to show who developed it, what sort of models it runs, and the accreditations/audits it holds?</li><li>If an AI app/agent needs to rely on other AI agents to accomplish tasks it has been given, how does it know which AI agents to trust and which ones <em>not</em> to trust? How about which tools, services, and data sources to trust? Moreover, how would AI agents know <em>which topic(s)</em> to trust another AI agent/tool/source on?</li><li>How can this be done in a scalable fashion, without relying on centralised lists or app stores maintained by gatekeeping Big Tech companies?</li></ul><h3><strong>Why has this been hard to bring to life until now?</strong></h3><p>Beyond just the questions of agentic trust, we’ve also been exploring scoped, <em>granular</em> permissions for AI agents (e.g., for an AI agent to “use my credit card to book a restaurant reservation, but NOT go on a spending spree on anything else”) and auditing. The hard part has been to translate this into enforceable and repeatable instructions that can be followed by a wide variety of AI apps and agents, without building a proprietary protocol to interact with <em>any</em> kind of decentralised identity network.</p><p>Recent advancements in this field have made it practically feasible for AI agents to understand and process digital identity. That’s why cheqd is taking a pioneering step forward, extending our vision of Verifiable AI into this new frontier. We’re thrilled to introduce cheqd’s <strong>Agentic Trust Solution</strong>, one of the <strong>world’s first digital identity toolkits to weave verifiable trust</strong> directly into the fabric of AI agent interactions.</p><h3><strong>The breakthrough: Model Context Protocol (MCP) gives AI agents access to <em>tools</em></strong></h3><p>A key catalyst for this shift is the emergence of the <a href="https://modelcontextprotocol.io/introduction"><strong>Model Context Protocol (MCP)</strong></a>, which was announced by <a href="https://www.anthropic.com/">Anthropic</a> (the creators of <a href="https://www.anthropic.com/claude">Claude AI</a>) in November 2024. Understanding a bit about MCP clarifies how verifiable trust can be technically achieved in AI interactions. It provides a much-needed <strong>common language</strong> for AI models, agents, and external tools to communicate context and capabilities securely. It’s the interoperability layer the ecosystem desperately needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/0*Usvmujf_oMXnwsT9" /><figcaption>Source: <a href="https://generativeai.pub/mcp-servers-explained-python-and-agentic-ai-tool-integration-aa2ddca6cbe5">Generative AI</a></figcaption></figure><p>AI agents and apps will need access to tools and data sources to do their work. Prior to MCP being released, the usual way in which developers would need to deal with such integrations was to provide complex prompts to AI agents/LLMs, and hope that they follow those instructions (and not end up misinterpreting the intent). Writing such prompts can be complicated and hard to repeat consistently. Alternatively, it’s also simpler than building custom integrations to a specific AI app, ChatGPT plugins, or other frameworks such as <a href="https://www.langchain.com/">LangChain</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ge4NE4wV7CDXZo9O" /><figcaption><em>Source: Stytch “</em><a href="https://stytch.com/blog/model-context-protocol-introduction/"><em>Model Context Protocol (MCP): A comprehensive introduction for developers</em></a><em>”</em></figcaption></figure><p>MCP had been gaining a <em>lot</em> of traction amongst the earliest adopters and developers — but was restricted so far only to “MCP Clients” (user software) such as Claude Desktop that supported the protocol. Within the last week, however, <a href="https://x.com/openaidevs/status/1904957755829481737">OpenAI announced it would support MCP in the OpenAI SDK and ChatGPT Desktop app</a>…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eCS7PFVZCb3E0Ndl" /></figure><p>…as well as <a href="https://x.com/sundarpichai/status/1906484930957193255">Sundar Pichai, Alphabet’s CEO, hinting that Google would support the specification</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5n-thxVl87bJfcVD" /></figure><h3><strong>Enter cheqd’s Agentic Trust Solution for AI agents and developers</strong></h3><p>Within the past few months, <a href="https://github.com/modelcontextprotocol/servers">many MCP “Servers” (tools that can be used by AI apps to connect to particular sources, such as Google Search, Github etc)</a> have been created. While MCP itself provides the communication rails, <strong>it doesn’t inherently solve the trust problem — that’s where cheqd’s Agentic Trust Solution comes in</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZE6LMoVFD_jnByVT" /><figcaption><em>Illustration of how AI agents can hold accreditations through Decentralized Trust Registries</em></figcaption></figure><p>Our approach uses MCP as the communication backbone to enable <a href="https://docs.cheqd.io/product/build-trust-for-ai-agents?utm_source=medium&amp;utm_medium=social"><strong>Decentralized Trust Registries</strong> for AI agents</a>. Think of it like a verifiable digital breadcrumb trail for AI identity and authorisation:</p><ol><li><strong>Verifiable Credentials (VCs) for Agents:</strong> We empower AI agents to hold tamper-proof digital credentials. Think of these like highly secure digital ID cards or passports specifically for AI agents. Unlike a simple label, these credentials contain rich, verifiable claims — like a digital badge proving the agent’s developer, its safety audits, or specific permissions it has been granted (e.g., ‘authorized to access booking systems’) — issued by trusted authorities like developers, companies, or industry bodies like the <a href="https://www.daiaa.org/">Decentralized AI Agent Alliance (DAIAA)</a>, which <a href="https://x.com/DAIAAlliance/status/1907738204540698864">cheqd recently joined</a>.</li><li><strong>Trust Registries:</strong> These credentials and their issuers can be anchored and verified against Trust Registries. Imagine these as highly secure, public directories acting as sources of truth — instead of listing phone numbers, they might list trustworthy credential issuers (like the official body that certifies an agent) or the accredited agents themselves. Because these registries are stored in a decentralized way on the cheqd network, they aren’t controlled by any single company, making them resistant to censorship or gatekeeping and highly available.</li><li><strong>Verification Tools:</strong> cheqd has worked on software such as the <a href="https://www.hci.iao.fraunhofer.de/de/identity-management/identity-und-accessmanagement/TRAIN.html"><strong>TRAIN Universal Resolver</strong> from Fraunhofer</a> (funded by the <a href="https://forum.cheqd.io/discussion/24731-proposal-universal-trust-registries">cheqd community’s decentralised governance</a>), which will allow any user to verify an AI agent’s credentials by tracing them back to a trusted root issuer through this decentralised chain. Crucially, TRAIN allows blending decentralised as well as centralised trust chains (using DNS/X.509 certificates), providing a pragmatic model for AI developers to manage digital trust.</li></ol><p>This creates a powerful, flexible system — all backed with innovations that cheqd has been building over the past few years, such as a highly scalable decentralised identity network and <a href="https://docs.cheqd.io/product/studio/did-linked-resources?utm_source=medium&amp;utm_medium=social">DID-Linked Resources</a>, which allow these decentralised trust chains to be published. An agent might carry multiple credentials, proving different things to different parties, all verifiable through this trust chain.</p><h3><strong>Leveraging cheqd’s MCP Server tooling for AI apps and agents</strong></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FsT6soNmMGIs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DsT6soNmMGIs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FsT6soNmMGIs%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/545a121ad3b9edc743dffe406a1beb92/href">https://medium.com/media/545a121ad3b9edc743dffe406a1beb92/href</a></iframe><p>Our MCP Server is <strong>one of the world’s first to enable AI agents to read and write Decentralized Identifiers (DIDs) — which are like permanent, unique digital addresses that the agents control themselves — and issue digital credentials</strong>. Developers can <a href="https://github.com/cheqd/mcp-toolkit">use <strong>cheqd’s MCP toolkit</strong> <em>today</em> to start building applications</a> where AI agents natively manage and present their own DIDs and <a href="https://learn.cheqd.io/decentralised-identity/credentials/what-is-a-vc?utm_source=medium&amp;utm_medium=social">Verifiable Credentials</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/0*9tr2VqYI8FJuLGZ4" /><figcaption><em>Validating a </em><a href="https://cheqd.io/blog/introducing-zero-knowledge-credentials-zkcreds-the-latest-addition-to-cheqd/?utm_source=medium&amp;utm_medium=social"><em>zero-knowledge credential</em></a><em> with cheqd’s MCP Server</em></figcaption></figure><p>While this early release is developer-focused, MCP as a specification itself has been rapidly evolving. Currently, it requires developer skills to <a href="https://docs.cheqd.io/product/advanced/tooling/mcp-server-setup?utm_source=medium&amp;utm_medium=social">run a Docker container on your desktop</a>. As recently as a week ago, <a href="https://blog.cloudflare.com/remote-model-context-protocol-servers-mcp/">core contributors announced that MCP would support <em>remote</em> MCP servers</a> — which would allow <em>any</em> user, without developer experience or knowledge, to authenticate their account with services that add a data source. We plan to fast-follow with the MCP community to add support for a remote MCP Server that allows any AI app or agent to easily interact with decentralised identity networks such as cheqd.</p><h3><strong>What comes next: Building the future of Verifiable AI</strong></h3><p>Our vision for the Agentic Trust Solution doesn’t just end with Trust Registries for AI agents; it is about enabling <strong>responsible innovation</strong> for the field of AI<strong>.</strong> By providing verifiable answers to questions of identity, capability, and authorisation, we plan to expand our MCP tooling to support:</p><ul><li><strong>Trusted AI agent/app trust chains:</strong> Engage with AI agents with greater confidence, knowing their claims can be verified, as well as AI agents to do this on their own. We will work with industry and alliance partners to establish these trust chains.</li><li><strong>Enhanced accountability:</strong> Establish clearer lines of responsibility with granular permissions for what you’ve allowed an agent to do or not to. We plan on implementing these by expanding the types of credentials an AI agent holds, from ones just issued to the agent (e.g., “Claude AI was created by Anthropic, Inc.”) to specific relationships between AI agents and their users (e.g., “<em>this</em> instance of Claude Desktop on Ankur’s laptop has been allowed to complete <em>these tasks</em>”). Every AI agent will come with their own identity wallets.</li><li><strong>Trust in the content</strong>: AI agents will not only be producing generated images, video, and audio but <em>also</em> consuming AI-generated media. Enabling <a href="https://cheqd.io/blog/how-verifiable-ai-enables-trust-for-ai-agent-adoption/?utm_source=medium&amp;utm_medium=social">AI agents to understand what content they can trust through Content Credentials</a> will become increasingly important when we rely on AI agents.</li><li><strong>True interoperability:</strong> Thanks to specifications like MCP, enable <em>any</em> AI agent ecosystem to consume and write to decentralised identity networks.</li><li><strong>New possibilities:</strong> Enable more complex and sensitive tasks to be delegated to AI agents, knowing robust trust mechanisms are in place. Our vision here is that it will expand beyond just simple proof-of-humanity to have</li></ul><p>We are actively developing and refining the <strong>Agentic Trust Solution</strong>, defining credential schemas, enhancing our MCP tools, and collaborating with partners across the ecosystem. The latest development can be tracked on <a href="https://cheqd.io/product-roadmap/?utm_source=medium&amp;utm_medium=social">our roadmap</a> while the <a href="https://cheqd.io/solutions/use-cases/verifiable-ai/?utm_source=medium&amp;utm_medium=social">Verifiable AI use case</a> is discussed in a dedicated section. The rise of AI agents is undeniable. By embedding verifiable trust from the outset, using open standards and decentralised principles, we can ensure this powerful technology evolves in a way that is safe, accountable, and ultimately beneficial for everyone.</p><h3><strong>Ready to build trust for your AI Agents?</strong></h3><ul><li>Explore the concepts behind <a href="https://docs.cheqd.io/product/build-trust-for-ai-agents?utm_source=medium&amp;utm_medium=social"><strong>Decentralised Trust Chains for AI agents</strong></a></li><li>Dive into our <a href="https://github.com/cheqd/mcp-toolkit"><strong>Github repo for cheqd MCP Toolkit</strong></a> and learn how to <a href="https://docs.cheqd.io/product/advanced/tooling/mcp-server-setup?utm_source=medium&amp;utm_medium=social"><strong>set up a cheqd MCP Server for development</strong></a></li><li>Contact us at <a href="/service/mailto:product@cheqd.io">product@cheqd.io</a> if you’re an AI developer or company that wants to learn more on how to utilise the Agentic Trust Solution</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c26265c99384" width="1" height="1" alt=""><hr><p><a href="https://blog.cheqd.io/pioneering-trust-in-the-age-of-ai-introducing-cheqds-mcp-enabled-agentic-trust-solution-c26265c99384">Pioneering Trust in the Age of AI: Introducing cheqd’s MCP-Enabled Agentic Trust Solution</a> was originally published in <a href="https://blog.cheqd.io/">cheqd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Verifiable AI by cheqd]]></title>
            <link>https://blog.cheqd.io/verifiable-ai-by-cheqd-7975d296fc9d?source=rss-c5166068a656------2</link>
            <guid isPermaLink="false">https://medium.com/p/7975d296fc9d</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[iva]]></category>
            <category><![CDATA[cheqd]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <dc:creator><![CDATA[Ankur Banerjee]]></dc:creator>
            <pubDate>Tue, 30 Jul 2024 11:43:18 GMT</pubDate>
            <atom:updated>2024-07-30T11:43:18.707Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>How cheqd can help your business embed trust in your AI strategy</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ss9yHEAhiUvzXZMHW8Mouw.png" /></figure><p>In the final piece of our five-part series, we will delve into how cheqd can assist any organisation in developing its Verifiable AI capabilities. Verifiable Credentials (VCs) and Decentralised Identifiers (DIDs) are highly versatile technologies which can be applied to various use cases.</p><h3>What are Verifiable Credentials and Decentralised Identifiers?</h3><p>As discussed in detail in <a href="https://cheqd.io/blog/origin-of-verifiable-aithe-interplay-of-ai-and-verifiable-credentials/?utm_source=medium&amp;utm_medium=social">the first part of our series</a> on Verifiable AI, Verifiable Credentials (VCs) are portable packets of data held by the individual or entity to which the data pertains. These packets are verified as true by another entity, which digitally signs the VC with their Decentralised Identifier (DID).</p><p>The advantage of using VCs is the reduced need for cross-referencing with third parties to verify the required information about the holder. The ‘holders’ of Verifiable Credentials can range from human beings to ethically sourced bananas to automated AI Agents. Given recent incoming regulations around identity in the EU, in which decentralised identity technology plays a central role, the integration of VCs into the wider economy seems highly likely.</p><h3>Why should your company care?</h3><p>Artificial Intelligence is widely viewed as a huge driver of growth over the coming decade, with statista reporting that the total addressable market size by 2030 could reach <a href="https://www.statista.com/outlook/tmo/artificial-intelligence/worldwide#market-size">15.72 trillion dollars</a>. For comparison, that would be the same as doubling the EU’s total GDP, which <a href="https://www.visualcapitalist.com/16-trillion-european-union-economy/">is roughly 16 trillion dollars</a><strong>.</strong></p><p>Moreover, the ongoing trend towards Open Source, more light-weight models being able to compete with the high-parameter models such as ChatGPT means that access to Artificial Intelligence is quickly becoming democratised, with hobbyists now getting increasing access to powerful tools. Similar to the ‘hobbyist stage’ of the internet, this period will likely see significant innovations as a generation of developers begin to tinker with and explore the underlying technology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q7rZmwJnQRcZeP3rSs6Z0g.png" /></figure><p>With a Cambrian Explosion of different models and methods on the horizon, and the clear financial opportunities AI makes possible, having an AI strategy for the future is essential. Not only to take advantage of the technology’s benefits, but also to mitigate its costs. With such powerful tools, misinformation can be created at scale; the datasets used to train models may become compromised with bad data or rendered unusable by synthetic (AI-produced) data. Ensuring safety against social engineering hacks will also become ever more complex as these models improve in output quality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PrNsEttKC8yn78IL" /><figcaption><em>The cost of data breaches worldwide has risen significantly over the past decade</em></figcaption></figure><p>Cybersecurity threats have themselves increased massively in recent years, with the victim count rising by 1417% from 2002 to 2021, and <a href="https://aag-it.com/the-latest-cyber-crime-statistics/#:~:text=With%20an%20average%20of%2097,their%20data%20leaked%20every%20second.">$787,000 being lost every hour to cyber crime.</a> Data particularly has become a poisoned chalice for companies. Data is not only valuable to the companies that collect it — but large valuable data collections invariably become honey pots for cyber criminals, with the average cost of a data breach to a company being 4.35 million dollars. 1 in 2 North Americans had an account breached in 2021, making data security a growing concern for consumers and a longstanding issue for regulators worldwide. The reputational damage of a data breach can be enormous — <a href="https://www.barclaysimpson.com/calculating-the-reputational-cost-of-cybersecurity-breaches/#:~:text=He%20quoted%20a%20YouGov%20poll,be%20devastating%20for%20a%20company.">around 40%</a> of the total cost of a breach is attributed to the tarnishing of the company brand among shareholders, customers and employees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tdwoESpXQhqB6OZq" /><figcaption><em>One of the most common consequences of data breaches is reputational damage</em></figcaption></figure><p>As the technology improves, regulators strive to keep pace — with the European Union often leading the way in setting the regulatory environment. In the EU, the<a href="https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai"> AI act</a> determines numerous rules around high-risk applications (such as those used in healthcare, education, policing etc) to ensure safe interactions with AI. Models in these high-risk areas must adhere to strict obligations, such as having high-quality, approved datasets, logging of activities to improve traceability of results and decisions, and maintaining high levels of security and accuracy. Coupled with <a href="https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation">EIDAS2 </a>EU regulations on electronic IDs and the mandate for interoperability to be built into the system to enable multiple forms of Electronic ID, it is clear that acceptance of digital forms of identity is going to increase over the coming years, making the integration of Verifiable Credentials into an organisation’s AI tech stack much easier.</p><p>Taken together, it becomes clear that Verifiable AI will be required in some form or another if organisations wish to capitalise on the massive growth opportunities while avoiding the potential pitfalls of fraud, misinformation and data loss.</p><h3>How can the cheqd network help?</h3><p>We at the cheqd network, founded in 2021, are a decentralised identity infrastructure company focused on making interacting with Verifiable Credentials as seamless as possible for our partners and their partners to plug into and use. In a young industry, we have made sure from the start to not only conform to emerging standards, but also have a seat at the table when they are established. We are leading members of the Decentralised Identity Foundation, W3C, Open Wallet Foundation, TrustOverIP, INATBA and Content Authenticity Initiative. Recently we were invited to join the European Blockchain Sandbox, where we are developing a ledger-agnostic approach to trust registries to aid our journey to become a ‘Qualified Electronic Ledger’ under EIDAS2.</p><p>In addition to building interoperable, compliant infrastructure, we offer credential payments, enabling any identity transaction to be commercialised, helping remove one of the main barriers to adoption — the lack of a commercial option to replace the current system for KYC providers and others in the identity stack. Using the cheqd network, holders, issuers and verifiers can pay or get paid quickly and easily with full account abstraction.</p><p>Throughout this piece, we will discuss how the global need for data is changing dramatically in various areas and how cheqd network can help your organisation develop Verifiable AI in a safe, compliant and efficient manner.</p><p>If you think your organisation could benefit from working with the cheqd network, please don’t hesitate to contact us at <a href="/service/mailto:partnerships@cheqd.io">partnerships@cheqd.io</a>.</p><h3>Content Credentials</h3><h4><strong>What is a content credential?</strong></h4><p>Discussed in detail in our 3rd article in the series, a Content Credential is, in essence, a verifiable credential embedded in a picture or video’s metadata. Just as a VC contains verifiable, trustworthy information signed with a DID, so too is a Content Credential signed with a trusted organisation’s DID. These Credentials can tell you many things about a piece of content- such as its creator, if it has been edited, when it was taken, and whether it was created digitally, captured with a camera, or generated by an AI model. Using content credentials ensures a traceable history of edits, providing more information about an image of video than would be available otherwise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i0mvUVfo6N3rvzfK" /><figcaption><em>Content credentials are already in use by organisations such as the </em><a href="https://www.bbc.com/mediacentre/2024/content-credentials-bbc-verify"><em>BBC</em></a><em>, which make clear how BBC journalists verify their stories.</em></figcaption></figure><h4><strong>The increased value of Intellectual Property Rights and Content Origin</strong></h4><p>AI-generated content has profound implications for intellectual property rights and content origin. Knowing where our content comes from is more important than ever, as it helps prevent the spread of misinformation, which can impact both markets and democracies.</p><p>The need to determine whether content is human- or machine-generated content extends beyond avoiding misinformation: AI-generated data can considerably reduce a model’s effectiveness if included in its training process — similar to how a photocopy of a photocopy is typically of lower quality than the original.</p><p>Additionally, It is likely that consumers will continue to appreciate human artistic endeavours over machine-generated ones, further emphasising the need to verify the origin of content. As companies have begun to realise the value of the IP they hold on their websites, ensuring that the data models trained on are properly licensed has become more important.</p><h4><strong>Creating opportunities to protect and monetise reputation</strong></h4><p>Any form of content on the internet is ripe for disruption with Content Credentials. The fast-moving world of social media means consumers often have to fact-check away from the content itself, with no guarantee of success. News organisations, entities we reply on to deliver truthful information, have faced immense challenges in recent decades as they strive to remain relevant and profitable in the decentralised world of social media journalism.</p><p>Content Credentials can help solve that. By enabling any IP holder to accurately label content as their own, and by clearly distinguishing between AI-generated and human-created content, they can drastically revolutionise how we interact with the content we consume every day.</p><h4><strong>How can cheqd help?</strong></h4><p>cheqd is members of the Content Authenticity Initiative and Coalition for Provenance and Authenticity — two organisations dedicated to the standardisation and proliferation of content credentials. This positions us alongside some of the largest organisations in the world, including Adobe, Samsung, Google and OpenAI.</p><p>With our emphasis on creating new commercial opportunities through Credential Payments and the broad interoperability of the DID:CHEQ method, the cheqd network is well-positioned to help any organisation lead the way into the future. Our Credential Payments services enable creators and ‘Trust Anchors’, such as News Organisations, to not only protect their IP but can also get paid for creating content or verifying information.</p><h4><strong>Creating commercial opportunities for Content Credentials in Practice:</strong></h4><ol><li>A camera takes a picture with tamper-proof hardware that records key metadata, such as location, time, and camera model.</li><li>The hardware ‘signs’ a Content Credential attesting to the recorded metadata.</li><li>As the picture is uploaded to editing software such as Adobe Photoshop, any changes made to it including AI generation or the removal of metadata, are recorded as additional Content Credentials.</li><li>Images or videos then published online with an organisation such as the Associated Press or the BBC, would come with a Content Credential which consumers can check to see its known origins and whether the picture was AI generated. If a picture was discovered to lack content credentials, or exhibit inconsistencies within them, a reputable news agency would not publish it.</li><li>Republishers who use this content then make payments to the publisher, and others rights holders, such as the photographer and editor. Publishers here in effect act as ‘Trust Anchors’, getting paid for their ‘stamp of approval’ on a picture.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N9rGgYx2NZus8lf8" /></figure><h3>Verified Datasets</h3><p>Just as we are increasingly eager to know the origins of our food, it is becoming equally crucial to understand the source of our data. The quality of data used to train an AI model is one of the most important factors in whether a model is effective and profitable, with implications in model quality, IP infringement, and societal biases. In the EU’s recent <a href="https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai">AI act, </a>ensuring high quality data for models used in sensitive areas, such as policing, taxation and hiring policies, is one of the act’s keystones. This means that any company involved in critical AI model MUST prioritise data quality, making trusted datasets significantly more valuable.</p><h4><strong>Large AI datasets vs small AI datasets</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U37EeZIQPkMgoaZQ" /><figcaption><em>Smaller datasets are easier to verify than larger datasets with 100s of TBs of information — a small scientific dataset from Nature is likely to be more accurate than the entire internet.</em></figcaption></figure><p>The type of data that one uses is completely dependent on what one is trying to train in a model. Some datasets are vast, encompassing a broad range of information, while others are specialised in very niche areas with comparatively smaller amounts of data.</p><p>A large dataset is enormous, filled with mountains of data. An example of this would be Common Crawl, which is a dataset that essentially covers the entire internet. These datasets, often consisting of 100s of terabytes, are mostly collected and sometimes sold by search engines and social media platforms — The extensive data availability is a key reason why companies like Google, Meta and X (through xAI) are heavily invested in Artificial Intelligence. These massive datasets are a requirement for Large Language Models such as ChatGPT or Claude, which require an endless inflow of data in order to improve their effectiveness.</p><p>However, using a large dataset is not always the best answer for every AI model. As a dataset grows larger, verifying the accuracy and compliance of the information usually becomes more challenging. With so much data, it is very difficult to confirm that all the information adheres to IP laws, maintains high quality for positive outcomes, and is free from AI-generated content that could lead to model collapse. The sheer size also limits who can effectively train models with them. Decentralised AI projects such as Bittensor, for example, face hardware and latency constraints when working with such enormous datasets.</p><p>In contrast, a small dataset, though still in the range of 10s to 100s of gigabytes, often consists of more niche, high-quality data that is easier to verify. If, for instance, one wishes to develop a model capable of recognising number plates from low-quality photos, there is no need to include data on face recognitionDevelopers would most likely seek datasets from trusted parties to ensure high quality — using dubious data could compromise the model’s effectiveness. Picking up specific, high-quality data on a specific area is of the utmost importance in ensuring the efficacy of a niche model.</p><p>Due to their smaller size and specialised nature, these datasets are perfect first use cases of Verifiable Credentials, especially in the Decentralised AI space where decentralised markets require better data labelling solutions to remain decentralised. Smaller sets are easier to verify and thus create early opportunities for ‘Trust Anchors’ to monetise their reputations whilst enabling datasets to carry their VCs as they are bought and sold on Decentralised Data Marketplaces.</p><h4><strong>How can cheqd help create commercial opportunities for large dataset providers?</strong></h4><p>Verifiable Credentials can be used by large dataset providers for a number of purposes in the future. As mentioned above, content credentials could be an extremely important use case for Verifiable AI, enabling search engines and other crawlers to selectively identify data confirmed as non-AI generated in order to avoid model collapse.</p><p>This presents a particular opportunity for more niche search engines, who may lack the heft of Google, but still have the capability to create new IP-compliant, organic large datasets. These organisations can then supply verifiable credentials to any model using one of their datasets, and potentially receive payment for ‘confirming’ that the supplied data meets the required standards.</p><h4><strong>Creating commercial opportunities for large dataset providers in practice:</strong></h4><ol><li>An image search engine places a dataset on a data marketplace that is confirmed to have no non-synthetic (AI generated) data</li><li>The search engine signs a verifiable credential verifying that it is 100% non-synthetic data</li><li>Placed on a data marketplace, an AI model developer requests verifiable credentials confirming that the dataset doesn’t contain synthetic material</li><li>A payment is made to the attestor image search engine for verifying the verifiable credential’s accuracy</li><li>Having confirmed that the data is accurate, the model developer purchases the dataset.</li><li>The originally issued Verifiable Credentials can be reused repeatedly with verifiers continually receiving payments</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GLSvNWJivc_FPTNg" /></figure><h4><strong>How can cheqd help create commercial opportunities for small dataset providers?</strong></h4><p>Small datasets present an early low-hanging fruit for Verifiable AI. Specific datasets for niche subjects require subject matter experts and other ‘trust anchors’ to vouch for the quality of the data contained within and their smaller size means these datasets are more likely to be found on the kind of decentralised marketplaces those working in the ‘Decentralised AI’ space would prefer to use. Current data marketplaces such as Kaggle and Hugging face are highly centralised sites in which social proof through a system of reddit-like up-and down-votes is used to establish ‘quality’ — a measure that is highly manipulable.</p><p>As Decentralised data marketplaces continue to evolve, ensuring that any included dataset has verifiable information about their licensing and quality will help build much greater trust in the datasets. As with larger datasets, this creates commercial opportunities for those verifying the quality of this data,Using cheqd’s Credential Payments, anytime someone wishes to verify that the information provided is correct, an opportunity for a small transaction is created.</p><h4><strong>Creating commercial opportunities for small dataset providers in practice:</strong></h4><ol><li>University publishes peer-reviewed data on a decentralised data marketplace.</li><li>The university and the scientific journal which published it attest to the data’s accuracy by signing verifiable credentials that confirm it is peer-reviewed.</li><li>Before purchasing a dataset, an AI model developer requests verification that the dataset is peer-reviewed.</li><li>Confirming that the data is accurate, the model developer purchases the dataset.</li><li>A payment is made to the university and science journal.</li><li>The originally issued Verifiable Credentials can be reused repeatedly with attestors continually receiving payments</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nO93kxFE4eJqa70c" /></figure><h3>Hardware verification — Dealing with localised clusters, compliance and energy in a decentralised setting.</h3><p>The past two years since the release of ChatGPT have seen a proliferation of new AI projects, with a strong focus in the web3 sector on the idea of <strong><em>DeAI</em></strong> (Decentralised AI) — that the training of AI (and other compute heavy activities) can be done not just by enormous corporations with the capital required to purchase and power thousands of GPUs (CeAI), but also by a network of distributed, decentralised GPUs owned by independent, smaller individuals or companies.</p><p>Proponents argue that using a decentralised approach offers an alternative to the highly centralised world of Artificial Intelligence, enabling a wider range of developers and users from outside of the tech AI bubble to train and use Artificial Intelligence in a way that is more censorship-resistant and open.</p><p>However, the nature of decentralisation creates a number of problems for DeAI projects, some of which Verifiable AI can help to solve:</p><ol><li><strong>Localising compute clusters</strong> — a centralised network training an AI model will use GPUs in the same facility, or very close by, in order to reduce the amount of latency in the system. Any decentralised, distributed system therefore faces training issues if GPUs are not close to each other. This is not information that can be verified easily with up-to-date specifications, as any vaguely technical person can quite easily obfuscate their IP address with a VPN.</li><li><strong>Compliance</strong> — Although many DeAI projects tend to live by a ‘build things and break stuff’ philosophy, that does not mean that everyone who wishes to train a model wants to do it with no thought for local regulations, industry standards or international sanctions. Even the most ardent crypto-anarchist may be a bit embarrassed to find out that they have been paying the Lazarus Group (North Korean Hackers) to train their AI model. If DeAI wishes to compete with Centralised AI, it will need to be able to offer the same legal and regulatory assurances, around working with sanctioned individuals and having the correct data protection certificates for example, as large corporations are able to, or the industry will not be able to gain any serious users past the occasional hobbyist.</li><li><strong>Energy </strong>— Similar to compliance around sanctions, aiming towards carbon-neutrality is increasingly something expected of organisations and will often be a deciding factor in which product to use. Training using GPUs is extremely energy intensive and thus can potentially be a big drain on Net Zero targets. Large AI companies, such as Microsoft, OpenAI and Google are able to <a href="https://www.ft.com/content/9e19353c-22ec-4790-b7b7-b5121c5a6258">make a carbon-neutral (or carbon-offset) offer </a>to potential clients, enabling any firm using their tech to claim that they are carbon neutral. If DeAI wishes to compete, they will need to be able to offer something similar.</li></ol><h4><strong>How can cheqd help assure the geo-location of GPUs to reduce latency?</strong></h4><p>Latency is primarily influenced by GPU performance and location, making accurate verification of these factors of the utmost importance. While GPU performance can be easily tracked with up-to-date information shared within a decentralised network, meaning that obfuscating information such as hardware and performance is very tricky. However, verifying geo-location is trickier due to the existence of VPNs. By using Verifiable Credentials through the cheqd network to confirm the location of different GPUs, a more trustworthy map of the network emerges, enabling developers to train modelspicking GPUs which fit the minimum requirements.</p><p>This approach not only saves the time and money for developers training their models, but also creates new commercial opportunities for auditing firms. These firms, acting as ‘Trust Anchors,’ would be responsible for verifying the supplied information, and their established credibility would be critical. This potentially presents an opportunity for these firms to get paid each time someone wishes to confirm the geo-location of a GPU.</p><h4><strong>Creating commercial opportunities for auditing companies related to geo-location in practice:</strong></h4><ol><li>Auditing company audits GPU owner, checking their exact geo-location. If coming from a centralised cloud provider, this data can be pulled from their APIs.</li><li>When confirmed, GPU owner is issued a Verifiable Credential attesting to their geo-location</li><li>User rents GPUs and requests verification that the chosen GPUs have the required geo-location to ensure low latency</li><li>User pays a small fee to the auditing company for the requested verification</li><li>Upon verification, User and GPU owner begin contract of work</li><li>Verifiable credential can be reused for other transactions, with continuous payments to auditor</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wXN-TowmfD3JZrUp" /></figure><h4><strong>How can cheqd help ensure DeAI network users do not work with sanctioned entities and countries?</strong></h4><p>In every developed nation, ensuring compliance with regulations is a necessary cost of doing business. Especially when it comes to anti-money laundering, data protection or Know-Your-Customer. Any serious company has to ensure (and be able to prove) that they are playing by the rules of the game. By utilising the cheqd network, auditing companies can verify that GPU providers have the correct certifications, such as being HIPAA or ISO compliant, then issue a credential which they can continuously be paid to verify each time someone wishes to confirm it.</p><p>Similarly, KYC companies could issue and verify either ‘Negative KYC’ credentials (“this GPU provider is NOT from a sanctioned entity”) or ‘Positive KYC’ credentials (“this GPU provider is this specific entity at this address with this Company/Passport number), and also get paid each time this has to be verified (<a href="https://cheqd.io/blog/introducing-the-first-regulatory-compliant-reusable-kyc-kyb-digital-credential-solution/?utm_source=medium&amp;utm_medium=social">see our article here on reusable KYC</a>).</p><p>Using this system simplifies compliance for those renting computing power, making it easier for GPU providers to confirm their compliance without repeatedly undergoing lengthy, expensive KYC and certification processes, and creates a new revenue stream for auditing companies.</p><h4><strong>Creating commercial opportunities for auditing companies related to sanctioned entities in practice:</strong></h4><ol><li>Auditing company audits GPU owner, checking that the owner is not from a sanctioned entity</li><li>When confirmed, GPU owner is issued a Verifiable Credential attesting to their non-sanctioned status</li><li>User rents GPUs and requests verification that the chosen GPUs have the correct non-sanctioned credentials.</li><li>User pays a small fee to the auditing company for the requested verification</li><li>Upon verification, User and GPU owner begin contract of work</li><li>Verifiable credential can be reused for other transactions, with continuous payments to auditor</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fUjANbP6SRa8nwOm" /></figure><h4><strong>How can cheqd help ensure the use of DeAI networks does not negatively affect company sustainability targets?</strong></h4><p>As with other hardware certifications done through Verifiable Credentials, the cheqd network can help GPU providers obtain the correct certifications in a reusable credential form. Auditing companies can perform their standard checks to ensure GPU providers use renewable energy or purchase carbon-offsetting credits. They can then issue their usual ‘certificate’ in Verifiable Credential form, allowing anyone planning to use a GPU in a cluster to quickly verify that their GPUs are fully sustainable and do not negatively impact their net zero targets.</p><h4><strong>Creating commercial opportunities for auditing companies related to sustainability in practice:</strong></h4><ol><li>Auditing company audits GPU owner, checking that the owner is fully carbon neutral.</li><li>When confirmed, GPU owner is issued a Verifiable Credential attesting to their carbon-neutrality</li><li>User rents GPUs and requests verification that the chosen GPUs have the correct green credentials.</li><li>User pays a small fee to the auditing company for the requested verification</li><li>Upon verification, User and GPU owner begin contract of work</li><li>Verifiable credential can be reused for other transactions, with continuous payments to auditor</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IvidOXJjclekNj9M" /></figure><h3>Proof of Personhood — how to reduce bot attacks without ruining the internet.</h3><p>Proof of personhood is a key safeguard against fraud and bot manipulation. DDOS (Distributed-Denial-of-Service) attacks, bot manipulation, sybil attacks and AML requirements mean that we can no longer interact online entirely anonymously, especially in situations where fraud can occur. The ‘proofs of personhood’ needed to demonstrate that one is indeed a human can range from a simple captcha to a notarised, KYC’d contract, but the lower end of the scale can be gamed — captchas are no longer completely effective at distinguishing between humans and bots. This is creating a challenging situation for any entity looking to secure their website and to interact only with humans — the greater the levels of assurance and reputation needed, the higher the costs and complexity, and the harder it will be to get real users to comply.</p><h4><strong>Proof-of-personhood exists on a matrix</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DbGmAL-gDLL0sTKr" /></figure><p>Whilst many in the Decentralised and Digital ID space fret around the need for a strong proof-of-personhood and the potential privacy and UX disadvantages of using a higher level of KYC for every interaction, it is important to remember that the level of proof-of-personhood needed depends on the type of interaction you are having. If one is just trying to prevent a large number of bots getting through, a captcha perhaps may suffice, but if one is dealing with money (or digital money), the chances for fraud to occur increase dramatically, meaning a much stronger level of assurance is needed. Biometric proofs such as those used by projects such as Worldcoin and Humanity Protocol are not, and should not be necessary for every interaction one has online.</p><p><strong>Low assurance </strong>proof-of-personhood would be methods such as using a CAPTCHA, whilst a site such as X requires only an email address to create an account (hence the deluge of bots). A site like X however, largely uses follower count, reputation and proof-of-payment (X verified) to define who is worth listening to or not — one’s reputation is somewhat divorced from the assurance that one is who they say they are.</p><p><strong>Low-Medium assurance</strong> proofs-of-personhood are identity points more difficult for a bot to collect. Things that can only be collected by a person, such as attendance of a real life event, can be used as a more solid form of Proof-of-Personhood, especially when achieved using Verifiable Credentials. These could be a potential option for replacing CAPTCHAs, as many of these could be collected by a person over the course of the life from many different sources and would say little about a person except the event they attended.</p><p><strong>High assurance </strong>proof-of-personhood can be thought of as forms of more in-depth KYC checks — going from just proving that you are in fact a person (negative KYC), to knowing exactly who you are (positive KYC) to also potentially checking one’s reputation, such as when someone applies for a mortgage and must supply their credit score. These kinds of proofs are absolutely essential for high-value interactions as the incentive to defraud and manipulate is much higher when money is involved.</p><h4><strong>How can cheqd help companies safeguard against fraud and bot manipulation?</strong></h4><p>There are many different forms of proof-of-personhood, appropriate for different settings and times. Along with ‘proof-of-attendance’, many different proofs can be turned into Verifiable Credentials to be held in a user’s identity wallet, such as Reusable KYC credentials, connected twitter accounts, github passes etc. Recently passed EU Identity regulations, eIDAS2, are gearing up to ensure every EU state has a wallet available for citizens capable of storing digital identity credentials by 2026, meaning that the use of verifiable credentials may soon become ubiquitous.</p><p>As leaders in the space, the cheqd network has built itself to the specifications required for EUDI wallets, ensuring our network will be interoperable with any wallet used to store government credentials. As a partner, we offer a plug-and-play solution for issuing and verifying the countless proof-of-personhood credentials users will pick up along the way, as well as a way for entities to monetise even small proofs if they wish to.</p><h4><strong>Creating opportunities to safeguard against fraud and bot manipulation in practice:</strong></h4><ol><li>Person collects proof for their various handles, e.g. email, Discord, Telegram</li><li>Person completes KYC process and collects re-usable KYC credential.</li><li>Person attends in-person events and collects POAPs.</li><li>Person attends online event and collects POAPs.</li><li>Person works for various companies or on multiple projects and collects either role credentials or endorsements for work done.</li><li>As required, person can select appropriate handles, credentials and POAPs to establish trust for any interaction. (e.g. they require 3 proof points, type depending on level of assurance needed)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UfqRz7Kg9fm5nblR" /></figure><h3>Personal AI Agents — Is your bot allowed to do that?</h3><p>The idea of a personal AI agent has transitioned from science fiction just over a decade ago (the movie <em>Her </em>was released in 2013) to nearly reality today with chat4pt4o, autoGPT and other LLM ‘agents’. These LLMs are capable of breaking down and implementing tasks in a digital environment. While we are still in the early stages of this technology, it is clear that AI agents will grow rapidly. Over time, ‘AI agents’ are likely to handle more tasks for human beings, starting with roles like customer service reps, trading bots and personal assistants, and eventually taking on increasingly complex tasks on behalf of their ‘owners’.</p><p>This evolution means that, just as humans require permissions and login details to work for a company, so will machines. Current permission systems are fairly disjointed and unable to smoothly handle the large number of interactions that are likely to be occurring with and between AI agents in the future. For example, if one wished to ask an AI agent to book them a holiday, one would first need to set up permissions to log into your account, to access your email and banking details.</p><p>Additionally, over time, it is likely that much of the work done by AI agents will be <em>between</em><strong> </strong>agents. This means that agents themselves will require methods to be able to trust each other — to be able to leave and read reviews, to verify that agents are indeed working for whom they claim.These identity features will be absolutely key to interacting with agents safely.</p><h4><strong>How cheqd can help create smooth, efficient permissions systems for AI agents using Verifiable Credentials.</strong></h4><p>Verifiable credentials can help create a portable reputation for AI agents without relying on a central third party to hold their reputation, which could turn into a very large database and prime target for cyberattacks. The use of VCs here would enable a much more seamless experience when requesting tasks that require access to multiple different platforms.Instead of requiring access to countless APIs, password details, and two-factor authentication gates, an agent could present a Verifiable Credential, which verifies they have permission from their owner to act on their behalf. This system would also help build reputation systems between AI agents, allowing them to issue VCs to each other for work completed and use these as proof of trustworthiness.</p><h4><strong>Creating commercial opportunities to create efficient permissions systems in practice:</strong></h4><ol><li>AI agent is requested to organise a small work party for an executive and is issued Verifiable Credentials by the executive that will give it access to their calendar, address, online shopping account and banking.</li><li>The Agent contacts the executives employee’s AI agents, to pick the optimal date. Each agent checks each other’s credentials to ensure they are representing the right people.</li><li>The optimal date is found between the agents and then shared to everyone’s calendars.</li><li>Online shopping website checks the agent’s credentials before allowing purchase of party hats</li><li>Once verified the website charges the executive’s bank account and send the party hats to their address.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PpU3MH70jlUJJmEK" /></figure><h3><strong>Intrigued? Contact Us!</strong></h3><p>As we have shown throughout this article, the cheqd network has great solutions for some of the trickiest issues brought about by artificial intelligence. If you want to learn more, or speak to us about how our verifiable AI products can be used to improve your organisation, please contact us <a href="https://cheqd.io/solutions/use-cases/verifiable-ai/">on this page</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7975d296fc9d" width="1" height="1" alt=""><hr><p><a href="https://blog.cheqd.io/verifiable-ai-by-cheqd-7975d296fc9d">Verifiable AI by cheqd</a> was originally published in <a href="https://blog.cheqd.io/">cheqd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Harnessing Verifiable AI to Defend Against Deepfakes]]></title>
            <link>https://blog.cheqd.io/harnessing-verifiable-ai-to-defend-against-deepfakes-6b8d91aa502d?source=rss-c5166068a656------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b8d91aa502d</guid>
            <category><![CDATA[verifiable-credentials]]></category>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[deepfakes]]></category>
            <category><![CDATA[content-credentials]]></category>
            <category><![CDATA[verifiable-ai]]></category>
            <dc:creator><![CDATA[Ankur Banerjee]]></dc:creator>
            <pubDate>Wed, 24 Apr 2024 17:26:49 GMT</pubDate>
            <atom:updated>2024-04-24T18:16:52.958Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>Re-establishing Trust with Content Credentials</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RqYM8s6uYm4265v-LCemOQ.png" /></figure><p>In October 2023, Slovakia went to the polls to elect a new government. Just days before the country went to vote, <a href="https://www.wired.com/story/slovakias-election-deepfakes-show-ai-is-a-danger-to-democracy/">an audio recording of the leader of the Liberal Progressive Party, Michal Šimečka</a>, speaking to a journalist about how they planned to rig the election spread like wildfire through social media apps like Telegram. The audio was immediately denounced as fake by both Šimečka and the journalist, but in the final two days of the election, in which politicians were not allowed to speak to the press, the damage was done. With few in-app tools available to consumers to verify the accuracy of what they saw online, only those willing to leave their platform of choice and actively check against other news sources would have been able to confirm that the recording was fake. A very close-run campaign, the election swung in favour of the rival party and the deepfake may have been directly attributed to this shift.</p><p>With <a href="https://time.com/6550920/world-elections-2024/">more than 64 countries around the world going to the poll booth this year</a>, it seems likely that misinformation using Generative AI may unfortunately play a huge part in the future of democratic states. We are quickly hitting a point where we are losing our ability to believe what we see with our eyes and hear with our ears. Deepfakes have the potential to impact society in a multitude of ways directly. Photoshop may have existed for a long time, but the ability to create misinformation <em>at scale</em> has only just arrived. Trust is quickly becoming the most important currency we have. In a digital world, where 90% of the material we consume may soon be AI-generated, we need to be able to trust the information in front of our eyes.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//twitter.com/WillSmith2real/status/1759703359727300880&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/f9cc6558041db5337902d558a439d5bb/href">https://medium.com/media/f9cc6558041db5337902d558a439d5bb/href</a></iframe><p><em>Could you tell if this latest video version was real or AI-generated?</em></p><p>Although this problem has rushed upon us, that is not to say we do not have the tools to begin combating it. It is a problem that some of the biggest companies in the world have been thinking about for some time. Through using <a href="https://contentcredentials.org/">Content Credentials</a>, a form of Verifiable Credentials, we can embed trust within the metadata of the content we see online so we know where that image or video was taken, who took it (whilst accounting for privacy concerns), and how (and by whom) it was edited. Verifiable AI (vAI) offers a way to rebuild trust and offer consumers the tools necessary to evaluate what they see and hear. A world where a 38-second deepfake that cost <a href="https://arstechnica.com/science/2019/12/how-i-created-a-deepfake-of-mark-zuckerberg-and-star-treks-data/">$522 in 2019</a> can now be created for free is in dire need of a solution.</p><h3>Deepfake: A History of Visual Manipulation</h3><p>1917 — Cardboard cutouts made to look like fairies are published in UK Magazine <em>Strand</em> and convince Sir Arthur Conan Doyle of the existence of magic beings</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*bvq2zE5nc1oMIIJj4C1j4g.png" /></figure><p>1988 — Photoshop is first developed</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*bT0DqwRuK56AlBjxGJA5ow.png" /></figure><p>1992 — The word ‘Photoshop’ enters the Oxford English Dictionary as both a noun and a verb</p><p>2003 — Kate Winslet speaks out against GQ magazine after they significantly alter her image, halving the size of her legs.</p><p>2004 — An image of Jane Fonda is edited into a picture of John Kerry to make it appear he was at an Anti-War protest during the Presidential Campaign</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/349/1*Xmw-j63mHpb4XgnPQ_fGLQ.png" /></figure><p>2008 — An image of Vice-Presidential candidate, Sarah Palin in a bikini is widely circulated by media and social media, before being revealed to have been photoshopped to discredit her</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/456/1*HFpIT03BdP3gQjN2SUJRqw.png" /></figure><p>2017 — a user on reddit called u/deepfakes publicly releases algorithms on the site, allowing anyone with the skills and computing power to have a go. The term ‘deepfake’ becomes popularised from the user’s name</p><p>2018 — FakeApp, an app to make Deepfakes more accessible, is released</p><p>2019 — Popular application FaceApp goes live with an age filter that allows users to see older versions of themselves</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*h7v1gznjkJj-VFJ1YHqvOw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*d3Vdx-U5W2yI44xnWghBwg.jpeg" /></figure><p>2019 — First fraud case using Deepfake techology is recorded. Criminals mimic the voice of a chief executive and walk away with €220,000 ($243,000).</p><p>2020 — <a href="https://www.youtube.com/watch?v=IvY-Abd2FfM">A deepfake Queen’s speech is done by channel 4 on Christmas Day</a></p><p>2021 — A lawyer in the United States goes viral with the phrase “I’m not a cat” whilst taking part in a court hearing whilst his streaming video was stuck on an image of a talking cat using deepfake tech</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x5voAR5pHyMPm5i5IWicXg.png" /></figure><p>2022 — Stable Diffusion is released, enabling non-technical users to create generative AI images using textual prompting</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*FGxz1L8cddDV9HCTOXPiIQ.png" /></figure><p>2023 — PhotoAI.com, known for its suite of AI tools for photo editing, launches significant enhancements including advanced face-swapping and photo manipulation tools</p><p>2024 — <a href="https://www.youtube.com/watch?v=HK6y8DAPN_0">OpenAI announces Sora</a> — a video generation AI platform capable of generating photo-realistic videos with realistic physics of up to one minute</p><h3>The Inherited Problem with Content</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k3nzctMzjt1dvOGiFdcxIw.png" /></figure><p><em>Can you spot the 11 telltale signs that this image was manipulated?</em></p><p>Image manipulation has been a problem for some time. Even before the advent of Generative AI and deepfake generation, Photoshop has already eroded trust in what we see with our eyes. The Princess of Wales, Kate Middleton, for example, invited weeks of social media speculation about herself a few weeks ago when she posted a <a href="https://www.wired.com/story/how-kate-middleton-conspiracies-spread-online/">Photoshopped image of herself</a> to social media, leading <a href="https://www.bbc.co.uk/news/uk-68526972">the Associated Press and other press agencies to issue a ‘kill notice’</a>, stating that “it appears that the source has manipulated the image…” and requesting that media organisations remove it from their media lists and online articles. Kill notices are issued when an image or story they have shared is flagged as being untrustworthy — a huge embarrassment for the Royal Family. Fuelled by the already-building speculation caused by her prolonged absence from the media, this kill notice sent the internet into a frenzy as people endlessly discussed, theorised and farmed engagement trying to work out what had happened to the Princess. This situation goes to show that consumers and citizens have a strong desire to know when they are being lied to, and that tools which reduce opacity in where our content comes from are needed. While in this situation, it was easy to spot the clear signs of Photoshopping, what happens when it is not so obvious? When transparency is built into the system, it becomes a lot harder to be dishonest and a lot easier for organisations or individuals to judge an image’s origin and accuracy.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//twitter.com/KensingtonRoyal/status/1771235267837321694&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/944102240b5461c755b7270f1c538157/href">https://medium.com/media/944102240b5461c755b7270f1c538157/href</a></iframe><p><em>Now people are even questioning whether this video is AI generated! Without Content Credentials, telling the difference will soon be almost impossible.</em></p><p>Although Generative AI offers huge benefits to all layers of society, it also makes our problems with trust in content 10x worse. Not only does Generative AI make the production of photorealistic images possible (soon the days of Generative AI struggling with hands, feet, and shadows will be gone), but it can also do so at scale. This means that we could soon see a digital world where companies can spin up deepfake adverts with <a href="https://x.com/beckylitv/status/1772407948481892396">‘real humans’</a> selling you a product with a script based around you and what your social media apps say about you. With <a href="https://openai.com/blog/sora-first-impressions">Sora by OpenAI</a> already capable of creating very realistic videos, it will not be long before these tools are in the hands of nefarious actors and fooling humans with video content becomes entirely possible. The implications for society are huge as now almost anyone, from a terrorist or rogue state actor to a teenager in their bedroom has access to tools capable of <a href="https://www.bloomberg.com/news/articles/2023-05-22/fake-ai-photo-of-pentagon-blast-goes-viral-trips-stocks-briefly">significantly moving markets</a>, affecting election results, or defrauding someone.</p><h3>The Solution: Verifiable Content Credentials</h3><p>The problem of verifying content is not a new one but has been something industry giants have been working on for some time. Even Fox News has been developing its <a href="https://variety.com/2024/digital/news/fox-verify-authentic-content-ai-misinformation-1235865243/">own verification system</a> on the Polygon Blockchain, known as <a href="https://www.verifymedia.com/">Verify</a>. Additionally, a larger group of different media organisations has got together to create a standards body capable of dealing with the complexities of technology and international organisations. Known as the <a href="http://c2pa.org/">Coalition for Content Provenance and Authenticity </a>(C2PA), with founding members including Adobe, BBC, Google, Intel, Microsoft and Sony, the coalition aims to set interoperable standards which enable consumers of content to understand where the content was made, by whom it was made or by what.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AQUwfoSyV92AichUkDq-_w.png" /></figure><p>By using a <a href="https://creator-assertions.github.io/identity/1.x-add-vc-v2/#_w3c_verifiable_credentials">form of Verifiable Credential</a>, it becomes possible to verify at the moment of a picture being taken, important metadata about its provenance, such as the location, the time, the fact a camera took it and was not AI-generated, and possibly the owner of the camera in question.</p><p>Any edits then made to the picture are also added to the metadata. It is important to note that not all edits are bad: news publications regularly retouch pictures to fix lighting or redact faces. Even metadata needs editing: it may be that a photographer wishes to remain anonymous, and instead, the press agency publishing it removes the Personal Identifying Information (PII) from the metadata. Editing is a necessary part of the journey; what is important is that these edits are recorded. The use of Verifiable Credentials creates a chain of trust which enables the privacy of individuals and the production of content ready for publication. This enables the creation of established trust anchors able to digitally sign and verify information, including that which has been removed or changed.</p><p>Content Credentials are a great tool to both protect against misinformation and yet protect individual privacy. They can establish a verifiable chain of custody for digital media, documenting its origins and any subsequent modifications. This information can be valuable for forensic analysis and attribution, helping to trace the source of deep fake content and identify the individuals or entities responsible for its creation. In the examples below, we illustrate how they would work with both the truth and falsehood if Content Credentials become widely adopted:</p><ol><li><strong>Content Creation</strong>: A protestor in a state governed by an authoritarian regime records acts of police brutality at a peaceful protest with their smartphone. Their smartphone is enabled with C2PA-enabled hardware, which records important metadata like the location and time, as well as information such as the owner of the phone’s Personal Identifying Information (PII). This information can be removed from the picture’s metadata at a later date (though this action will itself be recorded).</li><li><strong>Editing: </strong>The photographer edits the photo using C2PA-enabled editing software to blur the faces of some of the protestors; these changes are logged in the image’s metadata and signed by their Decentralised Identifier (DID). They then send the image, including its metadata to a journalist at a foreign publication, such as the BBC or al-Jazeera.</li><li><strong>Signing: </strong>The journalist looks at the image’s metadata and verifies that the photo they are looking at was shot on a C2PA-enabled device and therefore not AI-generated, as well as checking what edits were made by the photographer. He signs a content credential with his organisation’s DID, attesting to the accuracy of the photo</li><li><strong>Redaction: </strong>He redacts the photojournalist’s PII, signing a record of these changes into the content credential, attesting that they are a trustworthy source.</li><li><strong>Publication: </strong>After final edits are made to get the picture publication-ready, the journalist posts the image on his news publication’s website and social media.</li><li><strong>Verification:</strong> Readers are then able to look at the image metadata and check the Content Credentials to see that:<br>(a) The image was not AI-generated.<br>(b) It was taken at the time and location they claim it was taken at.<br>(c) The faces of the protestors were blurred.<br>(d) The photographer’s PII was removed<br>(e) No other edits were made.<br>(f) The news agency has vouched for the trustworthiness of the photographer</li></ol><p>Meanwhile, a government misinformation officer from the authoritarian regime wishes to create evidence showing the protestors being violent to justify the police attack:</p><ol><li><strong>Content Creation: </strong>The misinformation officer quickly generates images and videos of protestors holding weapons at the same rally using an image generator such as Dalle or MidJourney. The image generator attaches Content Credentials to the metadata attesting that the image is AI-generated.</li><li><strong>Editing: </strong>They then use PhotoShop to make further edits which are logged as Content Credentials in the image’s metadata.</li><li><strong>Signing: </strong>As the information officer does not have a good reputation, they must sign with a DID from an unknown account without a public reputation (or may not attest to the accuracy at all)</li><li><strong>Publishing</strong>: The misinformation actor posts their image on social media and amplifies the post through multiple bot accounts.</li><li><strong>Verification:</strong> When readers check the still-intact metadata of the image, they can see that:<br>(a) The image does not have a credential proving that it was taken by a device<br>(b) The image has a credential showing that it was generated by AI<br>(c) The image has a credential showing that multiple manipulative edits were made.<br>(d) The image’s has not been attested to by any trust anchor of good standing</li></ol><p>Demonstrably, Content Credentials, in this case, make it much easier for people to spot misinformation, but if the misinformation officer is smart, he would remove the Content Credentials from the image’s metadata. However, even if removed, the lack of Content Credentials proving the image’s provenance will increase scepticism in the provenance of the image, preventing it (at least) from being publicised by major news organisations. By creating tools that enable us to inspect and create a base standard for information (e.g. this is AI generated, this was taken at the correct location etc), we can start relearning how to trust the information we see or apply greater scepticism to content which lacks a chain of custody or provenance of how it was generated.</p><h3>Why might an organisation or individual be incentivised to adopt Content Credentials?</h3><p>Content credentials solve huge problems that we face in the wake of the proliferation of at-scale deepfakes and AI-generated misinformation, but they also offer huge opportunities.</p><p><strong>Reducing the spread of misinformation</strong>: The greatest benefit of this kind of technology is how it aids in helping better inform the public about the provenance of what they are seeing online. The better informed the public is, the greater the capacity to critically examine what they are consuming and the less likely people are to be taken in by misinformation.</p><p><strong>Brand protection</strong>: The use of a company’s brand in a fake news article or screenshot can cause a lot of damage to public trust in that organisation. Content credentials can create a useful source of truth that brands can point to as being their official facts, or used to establish if an AI model with the correct licensing generated an image.</p><p><strong>Brand Legitimacy:</strong> Being a <a href="https://learn.cheqd.io/decentralised-identity/start#id-1.-trust-anchor-issuer-registers-a-digital-signature-to-the-blockchain">trust anchor</a> in an established chain of content provenance also improves the legitimacy of brands by enabling them to become established sources of truth that people trust to give them the facts.</p><p><strong>Meeting compliance requirements: </strong>Many industries have legal requirements for content authenticity and attribution. For example, <a href="https://www.asa.org.uk/news/generative-ai-advertising-decoding-ai-regulation.html">the UK Advertising Standards Authority (ASA) recently reminded brands that ads using AI-generated content will need to comply with existing advertising rules</a> such as the rules on misleading advertising, especially the rules concerning testimonials and endorsements. Content Credentials can support compliance by providing a verifiable trail of the content’s origin and claims. With <a href="https://digital-strategy.ec.europa.eu/en/policies/code-practice-disinformation">codes of practices being refined</a> and the political spotlight likely to once again fall on disinformation over the coming years, it seems likely that many companies will use Content Credentials to improve compliance with regulations and standards.</p><p><strong>Agreeing to disagree</strong>: Organisations on different sides of the political spectrum, for example, CNN and Breitbart, may have very different perspectives and facts on an unfolding situation. However, it is still important that users have the opportunity to choose <em>which </em>organisation they should trust within the same framework. As long as everyone agrees on shared rules, for example, that an image should show if it is a genuine picture or something created or adjusted by AI, then we can begin having more trust in the images shared across the political spectrum.</p><p><strong>Decentralisation of Trust: </strong>Many people today get their news from social media influencers, freelance journalists or other non-traditional news sources. By agreeing to a shared system of attestation, independent reporters, photographers and fact-checkers can establish themselves as trust anchors outside of traditional news media organisations and networks.</p><p><strong>Financialisation of Trust</strong>: Establishing oneself as a ‘trust anchor’ may enable new commercial models for organisations currently struggling with their commercial model. Being a Trust Anchor holds value, and payment systems capable of microtransactions will enable new ways to monetize one’s credibility.</p><p><strong>Seamless integration: </strong>Content credentials can seamlessly integrate into existing authentication pipelines. By embedding content credentials into the metadata of digital content, verification is made much simpler. Deepfake detection systems can cross-reference Content Credentials with detection results to confirm or refute suspicions about the content’s authenticity.</p><h3>What challenges might we still face with Content Credentials?</h3><p>Although Content Credentials present huge opportunities, they are not a <em>deus ex machina </em>which can solve all our problems related to establishing Verifiable AI(vAI). Many issues still be dealt with and explored to ensure a working system of trust based on Content Credentials.</p><p><strong>Metadata can be redacted: </strong>The ability to remove information from the metadata, or just to not have any metadata in a piece of content at all is up to the person sharing that content. If the majority of the media does not adopt these standards, then it will become a mark of establishment-approved content, rather than an overarching system used by everybody to establish a shared truth.</p><p><strong>Who do you trust?</strong> Unless you are getting your news directly from the source, or the source is happy to be public, you still have to trust whatever organisation is attesting to a fact before believing it. Just because a picture of a UFO has been confirmed as real by <em>InfoWars, </em>it does not follow that you should believe it is a UFO. However, it may be that others think an image attested to by InfoWars is more trustworthy than one attested to by the BBC. Although Content Credentials do create more space for the truth, who you believe will always remain a factor.</p><p><strong>Can the system still be gamed?</strong> A smart misinformation spreader could generate a picture with AI, then take a picture if it using a C2PA-enabled camera, thus starting the chain of provenance later than where it <em>actually</em> started.</p><p><strong>Do you trust the tech</strong>? Owning the right Content Credentials may become synonymous with being accurate, but if this can be gamed, or the technology can be hacked, it creates opportunities for<em> </em>misinformation that has been verified to spread.</p><p><strong>Are Content Credentials fake news? </strong>Those who have interest in spreading misinformation to large audiences are incentivised to discredit a content credential systems (just as many attempt to discredit peer-reviewed scientific papers) which may potentially lead to mistrust in the technology as an ‘establishment surveillance tool’</p><h3>How can the cheqd network help?</h3><p>Here at cheqd, we have been working on Verifiable Credential technology for over 3 years. We have done seminal work in the creation of trust registries and helped to create the w3c standards on which Verifiable Credentials are based. Our products are fully compliant with eIDAS2 EU regulations on identity and we are in the process of becoming an EU-recognised <a href="https://x.com/cheqd_io/status/1726361486216544415"><em>Electronic Distributed Ledger</em></a><em>. </em>As well as being fully compliant, we are one of the most <a href="https://cheqd.io/blog/anoncreds-indy-pendence-part-two/?utm_source=medium&amp;utm_medium=social">interoperable DID methods</a> on the market, meaning our Verifiable Credentials can interact with multiple DID networks, and we have the capability of enabling payments for microtransactions.</p><p>Our unique privacy-preserving <a href="https://cheqd.io/blog/credential-payments-are-live-%f0%9f%8e%89%f0%9f%a5%b3/?utm_source=medium&amp;utm_medium=social">payment rails for Verifiable Credentials</a> unlock the possibility of new commercial models for trust anchors involved in the issuance of Content Credentials. For example, perhaps a news organisation can use its established reputation to charge for fact-checking an independent journalist’s work or improve the possibility of royalty payments for photojournalists not previously associated with a news organisation.</p><p>Coming back to our first example of a photojournalist getting a photo from a violent protest verified and published, payment rails enable the commercialization of this model at the <strong>republishing </strong>stage. Websites that wish to redistribute or republish the image could verify that they have the stamp of approval from the publishing press agency, and once established as attested for, pay for the rights to the image. Due to the <a href="https://docs.cheqd.io/identity/credential-service/payments?utm_source=medium&amp;utm_medium=social">customisable nature of cheqd’s payment rails for Verifiable Credentials</a>, this would also allow for split payments for the multiple parties involved, enabling both the news agency and the photojournalist to be paid for their work, creating a new potential automated royalties commercial model built around microtransactions.</p><h3>Conclusion</h3><p>Content credentials are poised to become a significant growth area and a major use of Verifiable AI (vAI) in the coming years. Given the mushrooming of deepfake misinformation and the breakdown in trust in our societies, a new way to track trust is desperately needed to provide some kind of faith in a shared version of the truth for society. We believe that the cheqd network offers a range of tooling as an infrastructure partner that will be of use to any organisation which sees itself as part of the content verification process.</p><h3>Contact us</h3><p>Are you a content creation platform, a publisher, news aggregator or media agency? Contact cheqd to see how you can use Verifiable AI to add trust and authenticity to content and your brand, and how we can help to unlock new business models. We are always up for a chat — contact us at partnerships@cheqd.io!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b8d91aa502d" width="1" height="1" alt=""><hr><p><a href="https://blog.cheqd.io/harnessing-verifiable-ai-to-defend-against-deepfakes-6b8d91aa502d">Harnessing Verifiable AI to Defend Against Deepfakes</a> was originally published in <a href="https://blog.cheqd.io/">cheqd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dynamic & Decentralized Reputation for the Web of Trust: What We Can Learn from the World of…]]></title>
            <link>https://blog.cheqd.io/dynamic-decentralized-reputation-for-the-web-of-trust-what-we-can-learn-from-the-world-of-533a015f40ee?source=rss-c5166068a656------2</link>
            <guid isPermaLink="false">https://medium.com/p/533a015f40ee</guid>
            <category><![CDATA[trusted-data]]></category>
            <category><![CDATA[verifiable-credentials]]></category>
            <category><![CDATA[web-of-trust]]></category>
            <category><![CDATA[decentralized-reputation]]></category>
            <dc:creator><![CDATA[Ankur Banerjee]]></dc:creator>
            <pubDate>Mon, 13 Nov 2023 14:38:20 GMT</pubDate>
            <atom:updated>2023-11-13T14:38:20.543Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>Dynamic &amp; Decentralized Reputation for the Web of Trust: What We Can Learn from the World of Sports, Tinder, and Netflix</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgu2cQIYoPy_knGsXCDOlQ.jpeg" /></figure><h3><strong>Web of Trust, As We Know It, Is Flawed</strong></h3><p>The core concept behind the <a href="https://en.wikipedia.org/wiki/Web_of_trust">original Web of Trust</a> is based on actors (through cryptographic keys) vouching for each other. Quoting directly from Phil Zimmerman (emphasis mine):</p><p>“As time goes on, you will accumulate keys from other people that you may want to designate as trusted introducers. Everyone else will each choose their own trusted introducers. And everyone will gradually accumulate and distribute with their key a collection of certifying signatures from other people, with the expectation that anyone receiving it will trust at least one or two of the signatures. This will cause the emergence of a decentralized fault-tolerant web of confidence for all public keys.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w2vjtkuobBTtyC_0.png" /><figcaption><em>Figure 1: Original Web of Trust illustrated (</em><a href="https://bitcoinmagazine.com/technical/bitcoin-and-trust-are-equally-unavoidable"><em>source</em></a><em>)</em></figcaption></figure><h4>Reputation should often naturally decay over time</h4><p>Proof-of-authority systems like the one above often model for reputation to go in only one direction: <em>upwards</em>. Actors who have been around longer gather more “stamps” of approval. This can be an issue because:</p><ol><li>What if the actor was <em>once</em> reputable, but has had a change of heart on their morals? Or, in the case of companies, been <a href="https://www.msn.com/en-gb/money/other/analysis-ben-26-jerrys-unilever-fight-shows-risks-of-ceding-control/ar-AA10HBn9?fromMaestro=true">acquired by new owners who have a vastly different ethical/reputational stance</a>?</li><li>Although the <em>ideal</em> of such decentralised PKI/reputation systems is to decentralise control so that no single actor becomes too powerful, <a href="https://w3techs.com/technologies/overview/ssl_certificate">the reality is that such power tends to coalesce towards a handful of actors</a>. How can we escape the pull towards formations of <a href="https://en.wikipedia.org/wiki/Natural_monopoly">natural monopolies</a>?</li><li>Regardless of whether once-trustworthy actors start behaving like their evil-twin-from-another-dimension, high-reputation actors become <em>even more valuable</em> targets for hacks, such as when <a href="https://www.wired.com/2012/08/apple-amazon-mat-honan-hacking/">Wired writer Mat Honan lost much of his online presence due to hackers wanting to take control of his three-letter <em>@mat</em> Twitter handle</a>.</li></ol><h4>Doesn’t meaningfully capture the multidimensional nature of reputation</h4><p>Records of which keys/handles/identifiers vouch for others only goes so far as to say <em>I believe this key/handle/identifier is trustworthy</em>. That doesn’t model the multi-faceted way in which humans interpret reputation:</p><ol><li>A person could have a <em>stellar</em> reputation as a skilled doctor/engineer/teacher/artist/(insert profession here)…but have a <em>terrible</em> reputation in other aspects of life, e.g., credit score, being a good parent, ability at swimming, etc.</li><li>A company could be <a href="https://ycharts.com/companies/AMZN/pe_ratio">delivering great returns to shareholders</a> but have a <a href="https://www.marketwatch.com/story/amazon-is-proof-of-a-major-weakness-in-esg-ratings-11636553274">terrible reputation for ESG (environmental, social, governance)</a> or worker rights.</li></ol><p>This is highlighted in previous RWOT proceedings, such as <a href="https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/anonymous-credentials-in-sovrin.md#trust-establishment">the discussion on Anonymous Credentials in Sovrin</a>:</p><p>“Sovrin also supports reputation events. These transactions may be public (unencrypted) or private (encrypted) and can support any type of reputation assertion. At the most basic level, reputation events enable an observer to trust that the ledger entry identifying an Issuer really is the issuer. This bootstrapping of trust could of course also be established “off-ledger”, for example by pointing to the Sovrin ledger entry from the Issuer’s website or distributing an X.509 certificate of the Issuer’s public key.”</p><p>But, trusting an X.509 certificate or a DID <em>on its own</em> doesn’t contain enough semantic information on whether to trust the issuer <em>on that particular topic</em>.</p><h3>Reputation lies in the eyes of the beholder</h3><p>Even if there was a model to capture multi-dimensional reputation, what <em>is</em> trustworthiness or reputation, anyway?</p><ol><li>Extending that example of company ratings/certifications, <a href="https://moneyweek.com/investments/investment-strategy/605229/the-irresistible-rise-of-esg-investing">should oil &amp; gas companies count in ESG stocks</a>? Is it better if a coffee brand is <a href="https://sustainability.stackexchange.com/q/6262/14293">Fairtrade or Rainforest Alliance certified</a>?</li><li>Wildly different <a href="https://news.gallup.com/poll/328637/last-trump-job-approval-average-record-low.aspx">approval ratings for politicians such as Donald Trump</a>, based on political affiliation.</li></ol><p>It is extremely tempting, like <a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4105763">Vitalik Buterin and other authors of the “soul-bound tokens” paper</a> did, to try build “on-ledger” reputation systems that provide a single “source of truth” for reputation. What this misses is <em>if I’m a professional in a certain field, my clients may want to check my professional skills, but they have no business also knowing my credit-worthiness</em>.</p><h3><strong>Taking a Page Out of Sports Rankings</strong></h3><p>How could we find a <em>decentralized</em> mechanism for reputation that addresses the shortcomings outlined above? The answer could lie in similar complex systems in the field of sports.</p><p>Ranking systems for chess, tennis, football, video games etc often rank players/teams using a system called <a href="https://en.wikipedia.org/wiki/Elo_rating_system">Elo ratings</a>. This is done by <a href="https://medium.com/purple-theory/what-is-elo-rating-c4eb7a9061e0">modelling interactions as a series of zero-sum games, where at a basic level</a>:</p><ul><li>If the higher-rated player wins, a few points are taken from the lower-rated player.</li><li>If the lower-rated player wins, a lot of points are taken from the higher-rated player.</li><li>If it’s a draw, the lower-rated player gains a few points from the higher rated player.</li></ul><p>A more common term that some may know these systems is <em>brackets</em> or <em>playoffs</em>, as <a href="https://worldcuppass.com/bracket/">visualised below from a FIFA Football World Cup 2022 bracket chart</a>…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rUHpZKcvaMhp6Gy9.png" /></figure><h3><strong>An unlikely inspiration from Tinder and Netflix</strong></h3><p>To understand how this concept could apply to dynamically bootstrapping a reputation system, we can <a href="https://www.theverge.com/2019/3/15/18267772/tinder-elo-score-desirability-algorithm-how-works">take a look at how Tinder used Elo ratings to rank profiles</a> in their app. Essentially:</p><ol><li>If any two users <em>both</em> swiped right on each others’ profiles, it count as a “win” in Elo rating terms.</li><li>Similarly, <em>both</em> users swiping left counted as a loss.</li><li>If one user swiped right and the other left, that would count as a loss too — but would have a different impact on rankings based on their relative rankings.</li></ol><p>It is worth acknowledging that sometimes such Elo rating systems can be gamed, and if designed badly, can lead to inequitable outcomes. (Tinder <a href="https://www.tinderpressroom.com/powering-tinder-r-the-method-behind-our-matching/">moved away from using Elo ratings</a> themselves.)</p><p>Another example of this is how <a href="https://about.netflix.com/en/news/goodbye-stars-hello-thumbs">Netflix moved from stars to a thumbs-up/thumbs-down rating system</a> (sometimes called a “Nero rating system”, after the Roman emperor), essentially turning their rating signals to a zero-sum game between <em>their estimate</em> of how much they think a viewer will enjoy a title <em>versus</em> how what the viewer rated it as.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/0*kwccoJnpjxj0cb7A.png" /><figcaption><em>ratings distribution (source: </em><a href="https://www.businessinsider.com/leaked-charts-show-how-ubers-driver-rating-system-works-2015-2"><em>Business Insider</em></a><em>)</em></figcaption></figure><p>The key insight there was that <a href="https://ux.stackexchange.com/questions/4200/rate-vs-like-dislike">given a 5-point rating system, people gravitate either towards 1 or 5</a>: the rating scales in the middle see much fewer choices being made. This is not an isolated example: <a href="https://techcrunch.com/2009/09/22/youtube-comes-to-a-5-star-realization-its-ratings-are-useless/">YouTube came to the same conclusion</a> switched away from stars. <a href="https://www.businessinsider.com/leaked-charts-show-how-ubers-driver-rating-system-works-2015-2">Uber driver ratings below 4 are basically a strong enough signal to kick a driver off the platform</a>, since 2s and 3s hardly get used. This also <a href="https://theatlas.com/charts/4y8zfUM9">mirrors Uber passenger ratings distribution scale</a>.</p><h3><strong>Other examples of zero-sum games to “rank” things</strong></h3><ol><li><a href="https://www.wired.com/2016/05/google-alpha-go-ai/">AlphaGo and other AI systems</a> use <a href="https://en.wikipedia.org/wiki/Adversarial_machine_learning">adversarial machine learning</a> to rank game strategies.</li><li><a href="https://en.wikipedia.org/wiki/ReCAPTCHA">reCAPTCHA</a> uses zero-sum game elements for <em>known</em> inputs while training for <em>unknown</em> inputs at the same time.</li></ol><h3><strong>Applying Elo ratings to decentralized reputation</strong></h3><p>A decentralized reputation system could similarly bootstrap <em>reputation scores per topic or attribute</em> much faster than trying to accumulate “stamps” over time.</p><p>Some thoughts on potential benefits could be:</p><ol><li>Reputation scores could go <em>up</em> as well as <em>down</em>. Elo ratings naturally decay over time due to inactivity, just like how sportspeople who drop out of a sport drop out of league tables. Applied to reputation, this provided a sliding time window over which reputation could decay.</li><li>Crucially, even “new”, low-ranked actors in a certain domain could trigger a reputation event that states <em>This higher-ranked actor is no longer nice</em>. On their own, a <em>single</em> lower-ranked actor couldn’t significantly impact a higher-ranked one — which prevents <a href="https://en.wikipedia.org/wiki/Sybil_attack">Sybil attack</a> scenarios. But, given <em>enough</em> actors stating positive/negative experiences, scores will change over time.</li><li>This does <em>not</em> mean an actor has a single reputation score — or a single score on how trustworthy their key/handle/identifier is. They could <em>dynamically</em> maintain <em>different</em> reputation scores on different topics. E.g., a company could have a high “buy” rating for their stock on financial metrics, but a low reputation on ESG. These can tied to Decentralized Identifiers (DIDs), for example, and assessed by the beholder differently.</li><li>Doesn’t <em>necessarily</em> need to be on-chain. It could be off-chain/off-ledger and shared on a case-by-case basis: the same way Verifiable Credentials are.</li><li>Finally a potential alternative to the question <em>How do I know this issuer/DID is trustworthy?</em> instead of sharing lists of trusted DIDs manually or <a href="https://identity.foundation/specs/did-configuration/">.well-known DID configuration</a> which is <em>basically</em> back to relying on centralised PKI / domain name reputation.</li><li>Extending that same idea, it could also apply to <em>trust frameworks</em>, <em>governance frameworks</em>, <em>schemas</em> etc. When a verifier is presented a credential from an isssuer/framework/schema they have never seen before, they can dynamically query the Elo rating based reputation score of each of those <em>on that particular topic/domain</em> and assess whether to trust the credential.</li></ol><h3><strong>Closing comments</strong></h3><p>Obviously, there are <em>lot</em> of things to map out on how to make this work in technical implementation, threat-modelling scenarios such as Sybil resistance, and ensuring there are safeguards to prevent unethical behaviour. I would love to collaborate at RWOT to map out other pros/cons not listed here.</p><p>However, this Elo ratings could provide a <em>radically</em> different reputation model than centralised PKI, WOT-based decentralised PKI, or soul-bound tokens / SBTs (which offers no consent-led mechanisms to <em>reject</em> malicious reputation statements). Instead of having to invent something entirely novel, Elo ratings are a well-researched and rigorously-modelled mathematical field.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=533a015f40ee" width="1" height="1" alt=""><hr><p><a href="https://blog.cheqd.io/dynamic-decentralized-reputation-for-the-web-of-trust-what-we-can-learn-from-the-world-of-533a015f40ee">Dynamic &amp; Decentralized Reputation for the Web of Trust: What We Can Learn from the World of…</a> was originally published in <a href="https://blog.cheqd.io/">cheqd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A New Hope in the Data Wars: Our first-ever “non-fungible” DID on the cheqd network]]></title>
            <link>https://blog.cheqd.io/a-new-hope-in-the-data-wars-our-first-ever-non-fungible-did-on-the-cheqd-network-7649cad8cb06?source=rss-c5166068a656------2</link>
            <guid isPermaLink="false">https://medium.com/p/7649cad8cb06</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[self-sovereign-identity]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[verifiable-credentials]]></category>
            <dc:creator><![CDATA[Ankur Banerjee]]></dc:creator>
            <pubDate>Wed, 04 May 2022 13:01:10 GMT</pubDate>
            <atom:updated>2022-08-25T08:33:45.950Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>Co-written by </em><a href="https://ankurb.medium.com/"><em>Ankur Banerjee</em></a><em> (CTO/co-founder), </em><a href="https://blog.cheqd.io/@rosspower"><em>Ross Power</em></a><em> (Product Manager), and </em><a href="https://blog.cheqd.io/@alex-tweeddale"><em>Alex Tweeddale</em></a><em> (Governance Lead)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0TSizmg1tX_E-2Lq" /></figure><h3>💫 About a month ago, in a Cosmos far, far away…</h3><p>…we spoke about the <a href="https://blog.cheqd.io/q1-round-up-from-cheqd-weve-upgraded-our-network-s-identity-features-bridged-to-ethereum-and-4012aacfc5b6">top 10 highlights of Q1 at cheqd</a>, where we touched upon the work we have been doing on adding and improving the identity functionality for app developers and users of our network.</p><p>Today, I’m excited to share the first-ever Decentralized Identifier (DID) on the cheqd network and what that means for real-world usage of our network for anchoring digital identities. This is an important milestone in our journey to help our partners and community reclaim their data.</p><p>Decentralised Identifiers (“DIDs”) are essential cornerstones of how decentralised identity works at a technical level. This <a href="https://resolver.cheqd.net/1.0/identifiers/did:cheqd:mainnet:zF7rhDBfUt9d1gJPjx7s1JXfUY7oVWkY">first DID we created on the cheqd mainnet</a> uses <a href="https://docs.cheqd.io/node/architecture/adr-list/adr-002-cheqd-did-method">the cheqd DID method</a>, and is permanently available on our immutable ledger.</p><p>Think of this as a web URL/address, much like how <a href="https://blog.cheqd.io/">https://blog.cheqd.io</a> does. In our case, the DID created by cheqd looks like this:</p><blockquote>did:cheqd:mainnet:<strong>zF7rhDBfUt9d1gJPjx7s1JXfUY7oVWkY</strong></blockquote><p>The random letters and numbers above are a unique “address”, where the cheqd team published details that relate to cheqd, as a company.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxTiIzAjgTOdqUvwRWM%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxTiIzAjgTOdqUvwRWM%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FxTiIzAjgTOdqUvwRWM%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="186" frameborder="0" scrolling="no"><a href="https://medium.com/media/5e7c34d3f64b340307f786656d09c070/href">https://medium.com/media/5e7c34d3f64b340307f786656d09c070/href</a></iframe><h4>These <em>are</em> the DID Documents you are looking for 👋</h4><p>To access the contents that are stored on the ledger for a DID, which are called “DID Documents, you need a “browser” for DIDs. Think of this the same way Chrome is a common web browser for web URLs. The <a href="https://github.com/decentralized-identity/universal-resolver">Decentralized Identity Foundation (DIF) Universal Resolver</a> is the “browser” for DIDs that app developers use to interact with digital identity networks.</p><p>Over the last month, we have been working on adding support for the cheqd network driver to the Universal Resolver project. When you use this to access the DID Document for <a href="https://resolver.cheqd.net/1.0/identifiers/did:cheqd:mainnet:zF7rhDBfUt9d1gJPjx7s1JXfUY7oVWkY">the DID we created</a>, you will see:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0cdDkgv1N6IOaA0tSBiAqQ.png" /><figcaption>DID Document for <a href="https://resolver.cheqd.net/1.0/identifiers/did:cheqd:mainnet:zF7rhDBfUt9d1gJPjx7s1JXfUY7oVWkY">did:cheqd:mainnet:zF7rhDBfUt9d1gJPjx7s1JXfUY7oVWkY</a></figcaption></figure><p>DID Documents are a bit like droids. They are not <em>always</em> understood by humans, <em>beeep-beeeep boooop-boooop</em>, but they are incredibly useful for machines to understand useful information about digital identities. In DID Document above, the contents describe <em>keys</em> using which cheqd (the company) could use to issue secure digital credentials.</p><p>It also describes links to web/social media profiles controlled by cheqd, such as our <a href="https://www.cheqd.io/">website</a>, <a href="https://twitter.com/cheqd_io">Twitter</a>, and <a href="https://www.linkedin.com/company/cheqd-identity/">LinkedIn</a>. And sometimes, just like droids, DID Documents can even carry secret messages. 🤫</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FoSyfZR3V4rZDi%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FoSyfZR3V4rZDi%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FoSyfZR3V4rZDi%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/9bb84391ecaedb90bc1ee13fb6074978/href">https://medium.com/media/9bb84391ecaedb90bc1ee13fb6074978/href</a></iframe><h4>Do (click). Or do not. There is no try. 🤓</h4><p>Pay close attention to this part in the DID Document (“DIDDoc”) and you’ll see…</p><blockquote>{<br> “id”: “did:cheqd:mainnet:zF7rhDBfUt9d1gJPjx7s1JXfUY7oVWkY#<strong>non-fungible-image</strong>”,<br> “serviceEndpoint”: “<a href="https://gateway.ipfs.io/ipfs/bafybeihetj2ng3d74k7t754atv2s5dk76pcqtvxls6dntef3xa6rax25xe"><strong>https://gateway.ipfs.io/ipfs/bafybeihetj2ng3d74k7t754atv2s5dk76pcqtvxls6dntef3xa6rax25xe</strong></a>&quot;,<br> “type”: “LinkedDomains”<br> }</blockquote><p>InterPlanetary File System — or <a href="https://ipfs.io/">IPFS</a>, as it’s more popularly known — is a global, decentralised, file storage system. Think of it as a file storage service such as Dropbox, except, with no single controlling entity behind securely storing the files.</p><p>If you look up the IPFS link above through any valid IPFS gateway, you’ll find <a href="https://gateway.ipfs.io/ipfs/bafybeihetj2ng3d74k7t754atv2s5dk76pcqtvxls6dntef3xa6rax25xe">our <strong>Data Wars</strong> poster</a>, showing every <em>single</em> person who has been working hard over the past year to bring <em>new hope</em> to a vision for decentralised identity which gives control back to the people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WTpChQPqRKLjTYt2Lj4XNw.jpeg" /><figcaption>The cheqd team in the Data Wars</figcaption></figure><p>I’m extremely proud — especially of our product &amp; engineering team — of the part they have played to make the technical work happen. ❤️</p><h3>The DID Document “non-fungible” Data Wars 🖼</h3><p>Non-Fungible Tokens (NFTs) have been often-mentioned in the context of being used to create a decentralised, on-chain unique identifier. We brought up how popular this concept has become in <a href="https://blog.cheqd.io/top-5-trends-in-decentralized-self-sovereign-identity-and-privacy-preserving-technology-in-web-3-0-b677926bcfc7#:~:text=of%20identity%20and-,NFTs,-Much%20like%20the">our analysis piece on Web 3.0 trends on the intersection of NFTs and identity</a>.</p><p>One of the basics of an NFT is that the image/media associated with is not <em>itself</em> encoded in the token, but referenced through a link/URL where the image/media is available (usually, decentralised storage such as IPFS).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fyuu95iUUP4iX23XvfT%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fyuu95iUUP4iX23XvfT%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fyuu95iUUP4iX23XvfT%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/f70066d16de39b3b88a876105366aa2c/href">https://medium.com/media/f70066d16de39b3b88a876105366aa2c/href</a></iframe><p>That’s <em>very</em> similar to what we had in our DID: <strong>a unique on-chain identifier that contains a link to an image/media asset off-chain, stored on decentralised IPFS storage</strong>. What’s more, by transferring control of a DIDDoc, it’s also possible for owners of a DID to switch hands. While it doesn’t exactly have the same (non-)fungibility properties of a “real” NFT, we thought this would be a fun and interesting way of how flexible the Decentralized Identifiers (DID) format is. 😉</p><h3>How to create a DID on cheqd’s mainnet?</h3><p>We are excited that it is now time for our community of cheqd validators, many of which are leading SSI vendors, to begin experimenting with creating a DID on cheqd. You can do so using the cheqd CLI or through VDR Tools.</p><p><a href="https://docs.cheqd.io/identity/building-decentralized-identity-apps/veramo-sdk-for-cheqd/did-operations">If you want to get started with anchoring DIDs and DID Documents, head over to the tutorials available here</a>.</p><h3>Building <em>real</em> digital identity apps using cheqd 🛂</h3><p>We demonstrated a demo web-based wallet at <a href="https://internetidentityworkshop.com/"><strong>Internet Identity Workshop #34</strong></a><strong> </strong>in San Francisco last week (26–28 April 2022). Check out <a href="https://twitter.com/ankurb/status/1519486635959746562">this tweetstorm we did during the conference</a>, which explains how we used this to demonstrate DIDs anchored on cheqd to which secure digital credential issuance can be linked.</p><h3>Ankur Banerjee on Twitter: &quot;😎 Try out the @cheqd_io demo yourself, get a Verifiable Credential for #IIW 34, and read more about the background for how we built this... https://t.co/UI4uWASlGx💡 Our starting principle for this #IIW demo: we wanted to build a non-custodial wallet, which works in a browser. / Twitter&quot;</h3><p>😎 Try out the @cheqd_io demo yourself, get a Verifiable Credential for #IIW 34, and read more about the background for how we built this... https://t.co/UI4uWASlGx💡 Our starting principle for this #IIW demo: we wanted to build a non-custodial wallet, which works in a browser.</p><p>You can also read a summary here if you find Twitter threads hard to follow:</p><p><a href="https://typefully.com/ankurb/PDcaiMP">Summary of cheqd&#39;s identity wallet demo at #IIW | Ankur Banerjee</a></p><p>We want more app developers, including the many partners of cheqd, to be able to build similar experiences as we did in a short timeframe for the conference. In a more technical tutorial in the future, we’ll explain how to do this yourself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4uSFpunv-KUUz4ZQW0Yunw.png" /><figcaption><a href="https://wallet.cheqd.io/">Demo wallet for IIW</a> built by cheqd</figcaption></figure><p>Give <a href="https://wallet.cheqd.io/"><strong>wallet.cheqd.io</strong></a> a spin to get a demo credential. <strong>May the Fourth be with you as you join our rebel alliance in the Data Wars</strong>! 🫶</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7649cad8cb06" width="1" height="1" alt=""><hr><p><a href="https://blog.cheqd.io/a-new-hope-in-the-data-wars-our-first-ever-non-fungible-did-on-the-cheqd-network-7649cad8cb06">A New Hope in the Data Wars: Our first-ever “non-fungible” DID on the cheqd network</a> was originally published in <a href="https://blog.cheqd.io/">cheqd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Q1 round-up from cheqd: We’ve upgraded our network’s identity features, bridged to Ethereum and…]]></title>
            <link>https://blog.cheqd.io/q1-round-up-from-cheqd-weve-upgraded-our-network-s-identity-features-bridged-to-ethereum-and-4012aacfc5b6?source=rss-c5166068a656------2</link>
            <guid isPermaLink="false">https://medium.com/p/4012aacfc5b6</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[web-3-point-0]]></category>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[self-sovereign-identity]]></category>
            <category><![CDATA[cosmos-network]]></category>
            <dc:creator><![CDATA[Ankur Banerjee]]></dc:creator>
            <pubDate>Wed, 06 Apr 2022 17:13:03 GMT</pubDate>
            <atom:updated>2022-04-12T19:19:59.762Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>Q1 round-up from cheqd: We’ve upgraded our network’s identity features, bridged to Ethereum, plus much more… 🚀</h3><p><em>Co-authored by </em><a href="https://zero-cool.medium.com/"><em>Fraser Edwards</em></a><em> (CEO/co-founder), </em><a href="https://ankurb.medium.com/"><em>Ankur Banerjee</em></a><em> (CTO/co-founder), </em><a href="https://alex-tweeddale.medium.com/"><em>Alex Tweeddale</em></a><em> (Governance &amp; Compliance Lead), and </em><a href="https://medium.com/@rosspower"><em>Ross Power</em></a><em> (Product Manager)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_LATlpTYmiG6VA1p" /></figure><p>cheqd is moving fast as we build out the decentralised network for trusted data on Cosmos. Three months into 2022, and we’ve been blowing past our quarterly milestones: making headway in the identity features of the network, bridging to Ethereum, listing on more high-profile cryptoasset exchanges, improving the validator and token holder experience, and much more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ERNThM-ai-c1135-X2BtvA.png" /><figcaption>A recap of cheqd’s product roadmap priorities for Q1 2022</figcaption></figure><p>At the start of the year, we shared <a href="https://blog.cheqd.io/cheqds-product-vision-for-2022-6a92e8e4d296"><strong>cheqd’s product vision for 2022</strong></a> where we laid out our plans for the year ahead, beginning with some ‘quick wins’ across identity and Web 3.0. In this blog post, we’ll give a summary of what we achieved in Q1 — and what to look forward to beyond.</p><h3>Top 10 Highlights from Q1 for cheqd</h3><ol><li>Completed <strong>two successful upgrades of the network</strong>. This is a large step in the right direction to firm up the <a href="https://docs.cheqd.io/node/docs/identity-api"><strong>identity capabilities of the network</strong></a> as we prepare to move into Q2, which will bring with it some exciting ways to make it easier for anyone to interact with the identity functionalities.</li><li><a href="https://blog.cheqd.io/cheq-tokens-are-now-available-on-ethereum-106ef4bd040d"><strong>Created a CHEQ-ERC20 wrapped token</strong></a> using Gravity Bridge. This means you can now engage in <a href="https://uniswap.org/"><strong>Liquidity Pools on Ethereum based DEX’s such as UniSwap</strong></a>! The Cosmos-based CHEQ token was already available on <a href="https://app.osmosis.zone/">Osmosis DEX</a> and was <a href="https://medium.com/emeris-blog/emeris-adds-7-new-chains-stargaze-rizon-sommelier-lum-network-chihuahua-desmos-and-cheqd-dd5c73bcc9b7">also listed on Emeris DEX</a>.</li><li>Welcomed some of the major validators in Cosmos ecosystem onboard as trusted partners: <a href="https://everstake.one/"><strong>Everstake</strong></a><strong>, </strong><a href="https://informal.systems/"><strong>Informal systems</strong></a>, <a href="https://citadel.one/"><strong>Citadel.One</strong></a><strong>, </strong><a href="https://www.forbole.com/"><strong>Forbole</strong></a><strong>, </strong><a href="https://github.com/notional-labs"><strong>Notional</strong></a><strong>, </strong><a href="https://www.whispernode.com/"><strong>WhisperNode</strong></a><strong>, </strong><a href="https://smartnodes.one/"><strong>Smartnodes</strong></a><strong>, </strong><a href="https://enigma-validator.com/"><strong>Enigma</strong></a><strong>, </strong><a href="https://www.ezstaking.io/"><strong>EZstaking</strong></a><strong>, </strong><a href="https://blockfend.com/"><strong>Blockfend </strong></a><strong>and </strong><a href="https://www.lavenderfive.com/"><strong>Lavender.Five Nodes</strong></a><strong>.</strong></li><li>Welcomed our second cohort of SSI vendors: <a href="https://animo.id/"><strong>Animo Solutions</strong></a><strong>, </strong><a href="https://www.gravity.earth/"><strong>Gravity</strong></a><strong>, </strong><a href="https://www.mavennet.com/"><strong>Mavennet</strong></a><strong>, </strong><a href="https://www.ayanworks.com/"><strong>AyanWorks</strong></a><strong>, </strong><a href="https://www.umazi.io/"><strong>Umazi</strong></a><strong>, </strong><a href="https://monokee.com/en/homepage/"><strong>Monokee</strong></a><strong>, </strong><a href="https://www.gayadeed.it/en/"><strong>Gaya</strong></a><strong>, </strong><a href="https://verio.id/"><strong>Verio</strong></a> (and 5 more to be announced shortly).</li><li>Been showered with press love — from<a href="https://www.bloomberg.com/press-releases/2022-03-09/cheqd-meta-analysis-finds-the-self-sovereign-identity-market-is-worth-over-550-billion"> <strong>Bloomberg</strong></a> to<a href="https://thefintechtimes.com/gametech-understanding-the-metaverse-its-relationship-with-gametech-and-its-future/"> <strong>The FinTech Times</strong></a>, and from<a href="https://www.globalbankingandfinance.com/2022-the-year-of-further-decentralisation/"> <strong>Global Banking and Finance Review</strong></a> to<a href="https://blockchaintribune.com/self-sovereign-identity-the-technology-to-kickstart-to-electronic-identities/"> <strong>Blockchain Tribune</strong></a>,<a href="https://bitcoinist.com/cheqd-partners-with-the-cedefi-alliance-to-build-a-self-sovereign-identity-protocol-for-defi/"> <strong>Bitcoinist</strong></a>, and many more!</li><li>Successfully completed our<a href="https://www.cheqd.io/blog/cosmos-community-airdrop"> <strong>Cosmos Community Rewards</strong></a>, with cheqd growing the number of wallets from <strong>6,000</strong> to <strong>71,000+</strong>. This also took our community engagement to new levels with <strong>23,000+ </strong><a href="https://t.me/cheqd"><strong>Telegram</strong></a><strong> group members</strong>, <strong>47,000+ </strong><a href="https://twitter.com/cheqd_io"><strong>Twitter</strong></a><strong> followers</strong>, and <strong>10,000+ </strong><a href="https://discord.com/invite/zjNCNZRZb6"><strong>Discord</strong></a><strong> users</strong>.</li><li><a href="https://www.cheqd.io/press/bitmart-to-list-cheq-native-token-for-the-cheqd-network"><strong>Listed on BitMart</strong></a>, a premier global digital asset trading platform with more than nine million users worldwide and ranked among the top crypto exchanges on CoinGecko.</li><li>Formed <a href="https://www.cheqd.io/press/indacoin-announces-strategic-partnership-with-cheqd"><strong>a strategic partnership with Indacoin</strong></a> — a leading fiat-to-crypto exchange company — to allow people to<strong> </strong><a href="https://buy.cheqd.indacoin.io/"><strong>buy $CHEQ tokens more easily</strong></a> and drive mass adoption. Millions of credit and debit cardholders are now able to purchase $CHEQ in more than 180 countries to accelerate the adoption of SSI.</li><li>Published our analysis of the ​​<a href="https://blog.cheqd.io/top-5-trends-in-decentralized-self-sovereign-identity-and-privacy-preserving-technology-in-web-3-0-b677926bcfc7"><strong>Top 5 trends in Decentralised Self-Sovereign Identity and Privacy-preserving Technology in Web 3.0</strong></a>, based on a survey of general audiences and experts in the field of self-sovereign identity.</li><li>Made it easier to engage in <a href="https://commonwealth.im/cheqd/"><strong>governance voting and discussions</strong></a> through the integration with <a href="https://commonwealth.im/cheqd/"><strong>Commonwealth</strong></a></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*SRCaloYeuJALfDCPtgIhow.png" /><figcaption>More ways to engage and interact with cheqd</figcaption></figure><p>In Q2 2022, we aim to bring more ways to interact with cheqd: both on the $CHEQ token, as well as identity functionality. Let’s dive in…</p><h3>Update on product roadmap progress</h3><h4>✅ Our upgraded cheqd mainnet</h4><p>The <a href="https://commonwealth.im/cheqd/discussion/4140-software-upgrade-proposal-upgrade-cheqdmainnet-v04xv05x">cheqd mainnet upgrade in March 2022</a> was a major step for us as we wrapped up much of the improvements to the identity aspects of the network we needed to do. This upgrade fixed technical debt issues and overall offered significant enhancements to the identity functionality and security of the network. You’ll find a more in-depth explanation of the March upgrade further in a separate blog post as well as our <a href="https://github.com/cheqd/cheqd-node/releases/tag/v0.5.0">release notes for cheqd node v0.5.0</a>.</p><h4>📚 Improved documentation for validators and community</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GNsWuAz9NSRKfGzteObcvw.png" /></figure><p>Last week we launched <a href="https://learn.cheqd.io/">our new learning site on <strong>learn.cheqd.io</strong></a>. We believe it is vital that we play our part in improving knowledge of what the possibilities are with the cheqd network and generally about self-sovereign identity. This new site will act as a <a href="https://learn.cheqd.io/">central location for all things decentralised identity, SSI and Web 3.0</a>, as we draw on our existing knowledge and new discoveries to help educate our community members and partners alike.</p><p>We’ve updated <a href="https://docs.cheqd.io/node/">the documentation for cheqd node software</a>. Many of our SSI partners and other validators noted in our product roadmap survey that more clarity is needed in our documentation, and improvements made to the overall onboarding experience.</p><p>We have made improvements in the node installation and upgrade process through <a href="https://github.com/cheqd/cheqd-node/releases">Debian packages</a> as well as <a href="https://github.com/cheqd/cheqd-node/pkgs/container/cheqd-node">Docker images</a>. We also created <a href="https://snapshots.cheqd.net/"><strong>snapshots.cheqd.net</strong></a> to serve up daily ledger snapshots to speed up the setup/restore process for node operators.</p><p>We hope these improvements will reduce the time it takes to set up a node, reduce the need to seek support, and free up more of our engineering team’s time for building functionality on the network.</p><h4>🪙 CHEQ-ERC20 wrapped token using Gravity Bridge</h4><p>As we build payment rails for trusted data, we want to offer issuers, verifiers (the receivers of trusted data), and holders a choice on the means of settlement. We expect a preference for <a href="https://en.wikipedia.org/wiki/Stablecoin">stablecoins</a> to eliminate the volatility in either pricing or settling payments for trusted data. More on this in our <a href="https://www.cheqd.io/blog/cheqds-tokenomics-for-ssi-explained-part-3-payment-models">tokenomics for payment models</a>. Building a link to Ethereum was one of the most heavily requested Web 3.0 features/functionality that the cheqd community wanted in <a href="https://blog.cheqd.io/youve-seen-our-product-vision-for-2022-now-we-want-to-hear-from-you-47b63e6ad7de">our product survey</a>.</p><p>A blockchain bridge or ‘cross-chain bridge’ enables users to transfer assets or any form of data seamlessly from one entirely separate protocol or ecosystem to another (i.e. Solana to Ethereum, or in our case Cosmos to Ethereum and vice versa).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/0*qWujqw6VFeVgeAlS" /><figcaption><a href="https://info.uniswap.org/#/pools/0xa305f3aad48e285c002a2dbadbbba58fea10ad45">CHEQ-ERC20:USDT pool</a> on Uniswap</figcaption></figure><p>Therefore, we <a href="https://blog.cheqd.io/cheq-tokens-are-now-available-on-ethereum-106ef4bd040d">partnered with Gravity Bridge to create an ERC20 representation of the Cosmos-based CHEQ token</a>. You can transfer CHEQ between its Cosmos and ERC20 versions now using the <a href="https://spacestation.zone/">SpaceStation InterChain Bridge web app</a> and <a href="https://learn.cheqd.io/getting-set-up-on-cheqd/cheq-erc20-wrapped-token/how-to-add-cheq-tokens-to-uniswap-liquidity-pools">participate in liquidity pools on Uniswap</a>. This brings the CHEQ token to even more DEXs, besides <a href="https://app.osmosis.zone/">Osmosis DEX</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tkAyaYu_6PPUPmdz" /></figure><p>You can <a href="https://etherscan.io/token/0x70edf1c215d0ce69e7f16fd4e6276ba0d99d4de7">add the CHEQ-ERC20 token to MetaMask</a> by clicking on <em>More</em> under the profile summary, and then <em>Add Token to MetaMask (Web 3)</em>.</p><h4>📖 Tutorials for identity functionality on cheqd network</h4><p>Making cheqd’s functionality easily digestible and accessible has been a core goal for the team in this quarter. This one is the top-ranked feedback point from our network partners.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FkDbqO%2F2%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FkDbqO%2F2%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FkDbqO%2Fplain-s.png%3Fv%3D2&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="600" height="456" frameborder="0" scrolling="no"><a href="https://medium.com/media/0d0bcff988aeb9286eadbc72da44f048/href">https://medium.com/media/0d0bcff988aeb9286eadbc72da44f048/href</a></iframe><p>In the background, we have been working on multiple tutorials for creating Decentralised Identifiers (DIDs) and DID Documents using the <a href="https://github.com/cheqd/cheqd-node">cheqd node command-line interface (CLI)</a> as well as <a href="https://gitlab.com/evernym/verity/vdr-tools">Evernym Verifiable Data Registry (VDR) Tools</a>. Stay tuned for more on this soon 🤓</p><h4>🛠 Migrating cheqd’s testnet from AWS, with more DevOps automation</h4><p>We initially ran most of cheqd’s own mainnet and testnet nodes on Amazon Web Services (AWS), but over the series of months we’ve been running the network, we identified a number of <em>fundamental</em> issues that make AWS not commercially competitive for running nodes at the scale we need to do our infrastructure. (Perhaps worth its own blog post.)</p><p>Our mainnet currently runs on a blend of <a href="https://hetzner.cloud/?ref=tODNsVrSDe7m">Hetzner</a>, <a href="https://m.do.co/c/5852e5b4aa1a">DigitalOcean</a>, and Cloudflare — and we’ve now completed this transition for our testnet as well. We’ve also worked on completely refactoring our repositories for DevOps and cloud automation tooling, which we plan on open-sourcing.</p><h4>💳 Simpler ways to buy $CHEQ, through Indacoin</h4><p>Easy access to $CHEQ has been a major priority for the team here, and we are happy to announce that <a href="https://indacoin.io/buy-cheq-with-card"><strong>buying $CHEQ is now a simple process, with just a debit or credit card</strong></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*doflTm9PZI5Nh1XGsTWzOw.png" /><figcaption>You can now easily <a href="https://buy.cheqd.indacoin.io/">buy $CHEQ with fiat currencies</a></figcaption></figure><p>This is made possible <a href="https://indacoin.io/buy-cheq-with-card">through our integration with Indacoin</a>, which currently allows highly efficient on-ramps into cheqd and other large crypto projects. Indacoin is also currently working on developing similarly efficient off-ramps which will genuinely revolutionise how cryptocurrency is accessed, bought and sold. No complex, onerous and time-consuming commercial agreements to negotiate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RZIJDPUgZKDdG2Od.png" /></figure><h3>🪂 Airdrops for the Cosmos community</h3><p>We ran <a href="https://blog.cheqd.io/cosmos-community-airdrop-32fdb1c0cfd0">a series of community rewards (“airdrops”) for the Cosmos community</a>. Airdrops are a common method used to reward community members who engage in various activities such as staking CHEQ tokens, or other networks selected, providing Liquidity on pools and generally for being loyal and engaged supporters. Check out if your wallet is eligible on <a href="https://rewards.cheqd.io/"><strong>rewards.cheqd.io</strong></a>, which will allow you to claim $CHEQ token rewards.</p><p>Out of the Cosmos ecosystem wallets we calculated eligibility for, <strong>approximately 180,000 wallets</strong> are entirely new to cheqd: as in, they weren’t staking or LPing $CHEQ before our campaigns began. The cheqd airdrop helped us achieve a number of milestones in our overall presence, and significantly increased the amount of cheqd wallets, now at <strong>71,000+ unique cheqd wallets</strong>. We welcome these Cosmonauts from the Cosmos ecosystem onboard!</p><p>However, the airdrop was not without its difficulties and has offered us an interesting insight into more of the challenges that exist within Web 3.0 which largely come down to issues relating to identity. Across the airdrop, we were able to identify a significant amount of fraudulent behaviour based on <a href="https://en.wikipedia.org/wiki/Sock_puppet_account">sockpuppeting</a>. At the same time, <a href="https://support.cheqd.io/support/solutions/articles/101000391485-update-on-mission-two-staking-and-liquidity-pool-rewards">we made omissions that initially resulted in far lower wallets being calculated as eligible</a> than they should have been.</p><p>We sincerely apologise to the Cosmos and cheqd community for this error and hope to make future airdrop campaigns go smoother based on the lessons learned from this one.</p><p>We <em>do</em> have a final airdrop mission coming soon, so watch this space… oh, and <strong>Happy Easter</strong> 😉🥚🐇</p><blockquote><em>Also check out…</em></blockquote><blockquote><em>👉 cheqd’s meta-analysis reasoning that the </em><a href="https://www.cheqd.io/press/cheqd-meta-analysis-finds-the-self-sovereign-identity-market-is-worth-over-550-billion"><strong><em>self-sovereign digital identity market size could be worth $500 billion+</em></strong></a><strong><em><br>🔖 </em></strong><em>Our survey-based analysis on the </em><a href="https://blog.cheqd.io/top-5-trends-in-decentralized-self-sovereign-identity-and-privacy-preserving-technology-in-web-3-0-b677926bcfc7"><strong><em>Top 5 trends in Decentralised Self-Sovereign Identity and Privacy-preserving Technology in Web 3.0</em></strong></a></blockquote><h3>🔮 Looking forward: Q2 and beyond…</h3><p>Over the coming months, we’re continuing to work on key identity aspects of the network, largely improving the overall developer/user experience and making the identity functionality come to life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*foEcyjHQdfX2BNOGOduS2w.png" /><figcaption>Q2 and beyond product roadmap for cheqd</figcaption></figure><h4>🔍 Universal DID Resolver</h4><p>We are in the final stages of wrapping up the design and architecture for <a href="https://github.com/decentralized-identity/universal-resolver">a Universal Resolver driver</a> for the did:cheqd method. While there <em>are</em> REST APIs on the node/ledger software to produce the underlying data for DID and its associated DIDDoc, the JSON produced by the default REST API cannot be fully conformant to the DID Core spec because of limitations in the conversion from on-ledger to JSON format.</p><p>This DID Resolver that we’re building will enhance data fetched from ledger to provide <a href="https://w3c.github.io/did-core/#representations">DID Core specification conformant JSON DIDDoc production</a>. The objective is to provide two distinct modes of running DID resolution, to meet the needs of different developer audiences.</p><ol><li><strong>“Full” DID Resolver</strong> that directly talks to a ledger node. This will likely be required by app developers or SSI vendors looking at processing high volumes of requests, and/or if they want the highest levels of assurance that the data was pulled untampered from the ledger.</li><li><strong>“Light” DID Resolver</strong>, designed as a serverless application that relays requests to a remote/external “full” DID Resolver API. This will allow app developers who don’t want to run a full node + full DID Resolver to be able to run their own, extremely scalable, and lightweight infrastructure for servicing DID read requests.</li></ol><h4>🧑‍💻 Client-application SDKs</h4><p>Software Development Kits (SDKs) are important for providing third parties functionality to use cheqd. Within an SDK for a network such as cheqd’s, it is important to provide easy functionality to (among other things):</p><ul><li>Creating, updating, retrieving DIDs and associated DID Documents</li><li>Issuing, holding, verifying, and revoking Verifiable Credentials</li><li>Creating, updating, and reading schemas for Verifiable Credentials</li></ul><p>Our aim is to make a single, modular SDK that supports the cheqd DID method while offering compatibility with Hyperledger Aries-based SDKs such as <a href="https://github.com/hyperledger/aries-framework-javascript">Aries Framework JavaScript</a>.</p><h4>🗃 A web-based wallet for $CHEQ tokens… and credentials</h4><p>A common question we get from our SSI vendor/partners as well as from our community is a <strong>simple</strong> way to visualise and understand the token + identity functionality that our network offers. We want to bring together the work we are doing on DID Resolvers and client-app SDKs into a <strong>web-based app that allows people to engage with CHEQ tokens, as well as to hold digital credentials</strong>.</p><p>We see this as a way to demonstrate how the various parts of the tech stack fit together, and to provide a reference implementation that can be used by our SSI vendor-partners. To be clear, we do not want to directly compete with the existing rich ecosystem of wallets and credential-handling applications — but create <a href="https://blog.cheqd.io/top-5-trends-in-decentralized-self-sovereign-identity-and-privacy-preserving-technology-in-web-3-0-b677926bcfc7">simple user experiences, focused on Web 3.0 use cases, that were ranked highly in our SSI trends research</a>.</p><h4>🧾 Scalable revocation registries and payment rails</h4><p>cheqd’s USP is that it provides a way for <a href="https://learn.cheqd.io/overview/introduction-to-decentralised-identity/what-is-a-verifiable-credential-vc">Verifiable Credentials</a> to be monetised using its native token, $CHEQ.<strong> </strong>There are various commercial models that may be created by using the cheqd network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gmaZ4fo74n4mi5Cc" /><figcaption>An example payment flow for digital credential exchanges</figcaption></figure><p>A verifier could pay the issuer for Verifiable Credentials it receives from the holder. This gives the issuer a recurring revenue stream each time the Credentials it issues need to be live-checked by the issuer.</p><p>The mechanism for this payment is through a privacy-preserving revocation registry that the issuer establishes.</p><p>The verifier will make a payment only if it wants to check whether the holder’s credentials have been revoked or not.</p><p>Over the next quarter, we will begin to fully define the Revocation Registry architecture and the building blocks for payment rails.</p><h3>Conclusion</h3><p>It’s been a very busy start to the year for the team and we’ve achieved a lot of our objectives and key results in the first quarter of 2022. This provides a fantastic foundation for the rest of the year, and to continue building our vision of becoming the payment layer for self-sovereign identity ecosystems.</p><p>Alongside our partners, we want to showcase what cheqd can really do to affect the way we interact online and offline — adding a trust layer — and incentive mechanisms.</p><p>We’d finally like to give a big shout out to our community of node operators, and the ever-growing community of supporters who motivate us to keep achieving new heights as we build on our vision.</p><p><strong>Keep it up cheqmates — and we will continue to work with your best interests at heart</strong>! ❤️</p><p><em>We would love to know your thoughts as always either as comments on the article or via any of our other channels below.</em></p><p><em>Make sure to join our rapidly growing </em><a href="https://t.me/cheqd"><em>Telegram community</em></a><em> to stay updated with our most recent news and insights.</em></p><p><em>P.S. We’re also on </em><a href="https://twitter.com/cheqd_io"><em>Twitter</em></a><em>, </em><a href="https://www.linkedin.com/company/cheqd-identity/"><em>LinkedIn</em></a><em>, and </em><a href="https://cheqd.link/discord"><em>Discord</em></a><em> make sure to cheq in!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4012aacfc5b6" width="1" height="1" alt=""><hr><p><a href="https://blog.cheqd.io/q1-round-up-from-cheqd-weve-upgraded-our-network-s-identity-features-bridged-to-ethereum-and-4012aacfc5b6">Q1 round-up from cheqd: We’ve upgraded our network’s identity features, bridged to Ethereum and…</a> was originally published in <a href="https://blog.cheqd.io/">cheqd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 5 trends in Decentralized Self-Sovereign Identity and Privacy-preserving Technology in Web 3.0]]></title>
            <link>https://blog.cheqd.io/top-5-trends-in-decentralized-self-sovereign-identity-and-privacy-preserving-technology-in-web-3-0-b677926bcfc7?source=rss-c5166068a656------2</link>
            <guid isPermaLink="false">https://medium.com/p/b677926bcfc7</guid>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[ssi]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[trends]]></category>
            <category><![CDATA[decentralization]]></category>
            <dc:creator><![CDATA[Ankur Banerjee]]></dc:creator>
            <pubDate>Fri, 25 Mar 2022 10:42:13 GMT</pubDate>
            <atom:updated>2022-04-04T23:02:38.282Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>Top 5 trends in Decentralised Self-Sovereign Identity and Privacy-preserving Technology in Web 3.0 (2022)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Olt0EYqWlBu0FTmnWQYQg.png" /></figure><p><em>Co-authored by </em><a href="https://alex-tweeddale.medium.com/"><em>Alex Tweeddale</em></a><em> (Governance &amp; Compliance Lead), </em><a href="https://medium.com/@rosspower"><em>Ross Power</em></a><em> (Product Manager), and </em><a href="https://ankurb.medium.com/"><em>Ankur Banerjee</em></a><em> (CTO/co-founder)</em></p><p>In the early months of 2022, the <a href="https://www.cheqd.io/"><strong>cheqd</strong></a> team conducted two surveys diving into self-sovereign identity (SSI) and digital identity in Web 3.0. We analysed responses from a general audience, as well as from an expert audience, to tease out key trends in how identity plays a role in decentralised systems and Web 3.0.</p><p>The first article focuses on trends and key takeaways that we derived from combining a <strong>general survey</strong> and a <strong>deep-dive survey</strong>, where the respondents were a blend of <a href="https://blog.cheqd.io/cheqds-product-vision-for-2022-6a92e8e4d296">experts from our list of 45+ partners</a> as well as general audience members through outreach we did on our social media channels on <a href="https://twitter.com/cheqd_io">Twitter</a>, <a href="https://t.me/cheqd">Telegram</a>, and <a href="https://www.linkedin.com/company/cheqd-identity/">LinkedIn</a>.</p><p>In a future article, we will deep-dive into the technical and industry-standard topics in self-sovereign identity (SSI), from an extended survey that was shown to an expert audience on the two topics.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FD17yv%2F3%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FD17yv%2F3%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FD17yv%2Fplain-s.png%3Fv%3D3&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="600" height="587" frameborder="0" scrolling="no"><a href="https://medium.com/media/102bb33ff87bf80486b561b4ced89bae/href">https://medium.com/media/102bb33ff87bf80486b561b4ced89bae/href</a></iframe><p>Overall, we had <strong>114 completed respondents</strong> to the general survey (with a <strong>completion rate of 65.8%</strong> with a <strong>confidence level of 95% </strong>for the trends and conclusions drawn from this survey. We describe the methodology and statistical analysis of survey respondents in more detail at the end of this article. We’ve also included links to the anonymised, aggregated responses for those interested in diving deeper into the data.</p><blockquote>Read <a href="https://www.cheqd.io/press/cheqd-meta-analysis-finds-the-self-sovereign-identity-market-is-worth-over-550-billion">cheqd’s meta-analysis reasoning that the self-sovereign digital identity market size could be worth $500 billion or more</a>.</blockquote><h3>Key Trends in Digital Identity from cheqd’s survey</h3><ol><li><strong>Trend #1: </strong>Maintaining privacy and control of their own data is of paramount importance to web users</li><li><strong>Trend #2: </strong>Users — and the companies/organisations where they want to use self-sovereign identity — have vastly different motivations</li><li><strong>Trend #3:</strong> Privacy-preserving commercial models for digital identity exchange could radically accelerate the adoption of self-sovereign identity</li><li><strong>Trend #4:</strong> Identity is a foundational building block for DeFi and Web 3.0</li><li><strong>Trend #5</strong>: Healthcare, Social Media, and Government use cases lead the pack among “traditional” sectors where SSI can be applied</li></ol><h3>Trend #1: Maintaining privacy and control of their own data is of paramount importance to web users</h3><h4>People do NOT feel in control of their data</h4><p>An <strong>overwhelming majority — 68% — felt that they had limited/no control over their personal data</strong>, and what happens once it’s shared with companies. Perhaps not unsurprisingly, given the composition of our survey respondents, a lot of them believed that <a href="https://www.cheqd.io/ssi-self-sovereign-identity-explained">self-sovereign identity (SSI)</a> — a new paradigm in portable and interoperable digital identity — would be the default method of handling digital identity in a 5+ years time horizon.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FCdsWQ%2F10%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FCdsWQ%2F10%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FCdsWQ%2Fplain-s.png%3Fv%3D10&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="700" height="278" frameborder="0" scrolling="no"><a href="https://medium.com/media/13015c9b81524c5633b163dee3ec9fe3/href">https://medium.com/media/13015c9b81524c5633b163dee3ec9fe3/href</a></iframe><p>Obviously, in a lot of scenarios people <em>have</em> to give their data to a company. For example, when buying a product from a Shopify store, a customer <em>needs</em> to give Shopify / the store their name and address (so that they can send the items bought).</p><p>An SSI solution doesn’t automatically solve the problem of whether a company decides to take someone’s personal/business data, and repurposes it. What it does offer a <em>possibility</em> of is to make asking for fewer correlatable data points or cloaked data points and make that the norm. This is <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/principles/data-minimisation/">a principle called <strong>data minimisation</strong></a>.</p><blockquote><strong>What do does ‘data minimisation’ mean?</strong></blockquote><blockquote>Data minimisation means <strong>collecting the minimum amount of personal data</strong> that you need to deliver an individual element of your service. It means you cannot collect more data than you need to provide the elements of a service…</blockquote><blockquote>- Derived from <a href="https://ico.org.uk/">UK Information Commissioner’s Office (ICO)</a> guidance</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yEalHJ8eRZ9S4QF4DTl52A.png" /><figcaption>Source: <a href="https://www.spreadprivacy.com/introducing-email-protection-beta/">DuckDuckGo “Spread Privacy” blog</a></figcaption></figure><p>Two good examples of data minimisation in active usage are <strong>Apple’s </strong><a href="https://support.apple.com/en-gb/HT210425"><strong>Hide My Email</strong></a> and <a href="https://www.spreadprivacy.com/introducing-email-protection-beta/"><strong>DuckDuckGo Email Protection</strong></a>: both offer the ability to <em>hide</em> the real email addresses as well as <em>remove</em> trackers that could leak personal data. Albeit these offerings are not built using SSI, it demonstrates a path forward that people <em>will</em> adopt privacy-preserving solutions when it is offered to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*msW8EWC_rxAbSX9OaBSESQ.gif" /><figcaption><em>Companies hide trackers in your emails that can capture personal information. (</em>Source: <a href="https://www.spreadprivacy.com/introducing-email-protection-beta/">DuckDuckGo “Spread Privacy” blog</a>)</figcaption></figure><p><strong>Self-sovereign digital identity</strong> expands this concept beyond just email addresses and enables data portability across different companies, industries, and even geographies — for far more types of personal/business data. Techniques such as <a href="https://academy.affinidi.com/selective-disclosure-share-what-you-want-8ae367655b7b"><strong>selective disclosure</strong></a> allow people to control <em>what</em> they share and minimise it in a fashion that moves data ecosystems towards giving people more control over their data.</p><blockquote>“For far too long, blanket terms of service agreements have forced consumers to either ‘agree’ to all of a company’s conditions or lose access to a website or app entirely…No negotiation, no alternative, and no real choice.”</blockquote><blockquote>— Rep. Lori Trahan (D-MA)</blockquote><h4>Existing data protection regulation is NOT good enough</h4><p><strong>66% of our respondents said they <em>don’t</em> feel existing data privacy regulations are sufficient to give people control of their data</strong>. This is no surprise when we consider that regulations such as GDPR <em>have</em> resulted in more compliance on part of companies…<a href="https://gizmodo.com/gdpr-iab-europe-privacy-consent-ad-tech-online-advertis-1848469604">but with limited effect in the control a person can exercise</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cHjBfiu4JHrS2oGRXu16Ag.png" /><figcaption>Screenshot of <a href="https://tosdr.org/">ToS;DR</a> home page</figcaption></figure><p>It’s extremely common even under the scope of GDPR that people are prompted to accept long-winded terms of service, where they blindly grant access to companies to their personal data that they understand little about.</p><p>This situation has gotten ridiculous enough, to the extent that it has spawned projects such as <a href="https://tosdr.org/">ToS;DR (“Terms of Service; Didn’t Read”)</a>, where community volunteers annotate ToS policies into a more digestible format; and the <a href="https://www.theverge.com/2022/1/13/22882110/tldr-act-lori-trahan-lujan-cassidy-facebook-twitter-terms-of-service-agreement">Terms-of-service Labeling, Design and Readability Act</a> (<a href="https://trahan.house.gov/uploadedfiles/tldr_act.pdf">TLDR Act</a>, a nod to the term “too long, didn’t read”) to legally compel companies to provide more tangible controls to people.</p><h3>Trend #2: Users — and the companies/organisations where they want to use self-sovereign identity — have vastly different motivations</h3><h4>Motivations of users are largely centred around controlling the privacy and access to their data</h4><p>We asked our survey respondents why did they, <em>personally</em>, care about self-sovereign identity. The choices presented here were based on commonly-quoted reasons the team at <a href="https://www.cheqd.io/">cheqd</a> had heard during working during the past five years in the space of self-sovereign identity.</p><p>Some of the choices presented were <em>directly</em> beneficial to them, such as the <strong>privacy of personal/company data</strong>, which was ranked as the <strong>top reason for their interest in SSI by 62.3%</strong> of all respondents.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2F1ssPP%2F2%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2F1ssPP%2F2%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2F1ssPP%2Fplain-s.png%3Fv%3D2&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="800" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/49a296dda3a81023fcd71ad82dd4df0d/href">https://medium.com/media/49a296dda3a81023fcd71ad82dd4df0d/href</a></iframe><p>While the overall ranking <em>disproportionately</em> skewed towards privacy and control of their data, <strong>personal control</strong> (ranked <strong>2nd</strong> overall) and <strong>efficiency gains</strong> (ranked <strong>3rd</strong> overall) were the next closest motivations. Control and efficiency are things that <em>both</em> users — and the companies/organisations they interact with — care about.</p><p><strong>Portability</strong>, <strong>better inclusivity</strong>, and <strong>technological innovation</strong> brought the middle of the pack with relatively similar spreads. Given the demographics of our respondents, there was a slight uptick at <strong>1st/2nd ranks </strong>for concepts such as tech innovation and decentralisation than others.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2F3znVM%2F1%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2F3znVM%2F1%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2F3znVM%2Fplain-s.png%3Fv%3D1&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="800" height="376" frameborder="0" scrolling="no"><a href="https://medium.com/media/99fcbd601415240f5219c5aa8222d3d9/href">https://medium.com/media/99fcbd601415240f5219c5aa8222d3d9/href</a></iframe><p><strong>Scope for commercial gains/profits</strong> had low ranks at position 1 or 2 (still higher than both innovation and inclusivity), with a big bump around <strong>5th rank</strong> — a bit more on this later.</p><h4>Why would companies/organisations bother with privacy-preserving digital identity?</h4><p>Stating that people in our survey wanted SSI is a <em>tad</em> obvious…and hopefully we’ve also shown through examples <em>outside</em> of the sphere why people care about and adopt privacy-preserving digital identity. But why would the <em>companies</em> that these users interact with care?</p><p>To dig into that question, we asked our expert audience of executives and industry experts from digital identity companies why <em>their</em> own existing/prospective clients cared about SSI.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FbOvUE%2F3%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FbOvUE%2F3%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FbOvUE%2Fplain-s.png%3Fv%3D3&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="800" height="332" frameborder="0" scrolling="no"><a href="https://medium.com/media/93e01cc0b1d6d58ad2e64678a908616f/href">https://medium.com/media/93e01cc0b1d6d58ad2e64678a908616f/href</a></iframe><p><strong>Reducing compliance risk</strong> was chosen by far by more than 2/3rds of the respondents who answered this question (<strong>70%</strong> of respondents), which is undoubtedly aided by <strong>clearer regulatory frameworks that promote privacy-preserving digital identity </strong>(<strong>55%</strong> of respondents). (We cover the evolution of the use cases and regulatory frameworks later in <em>Trend 5</em>.)</p><p>Tied in the second spot was a desire to <strong>stay ahead of the curve by adopting new technology</strong> (also at <strong>55%</strong>), which contrasts with the relatively-low ranking of “technological innovation” as a factor from a user perspective.</p><p><strong>Reduction in costs</strong>, <strong>cost of existing identity verification providers</strong>, or <strong>generating new revenue</strong> was selected by fewer respondents, which could be due to an <em>existing</em> lack of solutions that enable this in the space.</p><blockquote><strong>Other reasons we heard from our expert audience on why their clients care about SSI…</strong></blockquote><blockquote>“Providing new privacy enhanced experience for end users”<br><br>“Overcome surveillance capitalism”<br><br>“Increased trust and removing friction”<br><br>“End-to-end transparency &amp; correlatability for compliance use cases; protecting business confidentiality”<br><br>“A recognition that the public favors solutions that value their privacy.”</blockquote><h4>If everyone WANTS self-sovereign identity, why isn’t it being adopted more widely?</h4><p>The wide range of partners we have here at cheqd allowed us the opportunity then to flip the previous question and ask our expert audience what the biggest <em>blockers</em> they have heard from their clients in being able to consider SSI adoption.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2Fpiu4O%2F2%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2Fpiu4O%2F2%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2Fpiu4O%2Fplain-s.png%3Fv%3D2&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="800" height="297" frameborder="0" scrolling="no"><a href="https://medium.com/media/af3f9a26c9935c7ba1ca2fb0b462b558/href">https://medium.com/media/af3f9a26c9935c7ba1ca2fb0b462b558/href</a></iframe><p>The picture that emerges is an <em>impression — </em>whether justified or not — of <strong>technical standards not being mature enough </strong>(<strong>60%</strong> of respondents)<strong> </strong>and <strong>lacking/limited interoperability with products of other SSI software or existing enterprise systems </strong>(<strong>55% </strong>of respondents). To be fair, this is a <em>clear</em> rallying cry for the self-sovereign identity software industry: the developer experience of integrating, for example, <em>Sign-in with Apple</em> takes only a few lines of code, but implementing an SSI solution could take <em>dozens to hundreds of person-hours</em> of effort.</p><p>That might be slightly unfair as a comparison to make, or comparing apples to oranges since SSI goes far beyond what a simple single sign-on achieves. But the reality is that enterprise clients are, in all likelihood, <em>actually</em> comparing it to Apple’s (or Facebook’s / Google’s / traditional identity verification providers’) developer experience at a surface level.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2F06jS9%2F1%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2F06jS9%2F1%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2F06jS9%2Fplain-s.png%3Fv%3D1&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="800" height="310" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd18fd79b2a11bac526d8ef413b43209/href">https://medium.com/media/dd18fd79b2a11bac526d8ef413b43209/href</a></iframe><p>This neatly brings us to the rest of the top 5 blockers: <strong>unclear understanding of return-on-investment</strong> for investing in SSI solutions (<strong>55% </strong>of respondents), <strong>lack of knowledge of the benefits SSI brings among decision-makers </strong>(<strong>50%</strong> of respondents), and <strong>lack of commercial/business models </strong>(<strong>30% </strong>of respondents). These all broadly fit into the theme of being able to articulate the <em>business value</em> of why SSI is beneficial. <strong>Educating stakeholders</strong> is a common refrain that comes up in the free-text responses.</p><p>Our purpose here in showing these answers is <em>not</em> to cast a shadow of doom-and-gloom on the prospects that self-sovereign identity has. Instead, we wanted to transparently highlight the areas the industry experts themselves have identified as spots where the <em>whole</em> sector could improve. We’re assessing and responding to this data ourselves at cheqd to see where we could improve.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FndRSL%2F3%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FndRSL%2F3%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FndRSL%2Fplain-s.png%3Fv%3D3&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="600" height="250" frameborder="0" scrolling="no"><a href="https://medium.com/media/78a10fa246f29575da066db5c385907e/href">https://medium.com/media/78a10fa246f29575da066db5c385907e/href</a></iframe><p>Going back to the general survey for a second, it’s interesting to note that <strong>a larger portion of the <em>general</em> audience thinks the technical standards in SSI are mature enough for widespread use</strong> (<strong>28%</strong> agree, <strong>38%</strong> neutral) compared to the results we saw from blockers faced by the expert audience.</p><p>Once again, an overwhelming portion of respondents (<strong>61%</strong>) agreed that <strong>Web 3.0 / blockchain apps need integrated digital identity solutions</strong>. They are also <em>passionate</em> that there <strong>aren’t any alternatives besides SSI</strong> they strongly believe in.</p><p>There <em>is</em> one thing that <strong>more than 70%</strong> of respondents from our expert audience agreed would have the <strong>biggest impact</strong> in driving the adoption of SSI among their enterprise customers: <strong>payment mechanisms for digital identity exchanges</strong>. Onwards to <strong>Trend #3</strong>…</p><h3>Trend #3: Privacy-preserving commercial models for digital identity exchange could radically accelerate the adoption of self-sovereign identity</h3><p>One of the core hypotheses behind cheqd’s inception is that a lack of commercial models — which are privacy-preserving as well — is hampering the lack of SSI adoption. We described this in <a href="https://blog.cheqd.io/the-business-models-of-identity-bb3336773727"><strong><em>The business models of identity</em></strong></a> as follows (excerpted):</p><blockquote>…<strong>the time and resource cost an issuing/verifying organisation incurs must not be ignored</strong> for a viable and sustainable self-sovereign identity ecosystem.</blockquote><blockquote>For instance, <strong>government-issued credentials should be made free / as cheap as possible to acquire as they are funded through taxes and/or one-off fees</strong>. This is crucial as government-issued credentials are often the genesis of trusted data in many industry contexts.</blockquote><blockquote>However, in other scenarios<strong> where an issuing/verifying organisation is <em>not</em> a publicly-funded organisation, we do see an unmet need for compensating organisations that carry out the work of verifying digital identity</strong>. These organisations are the root of trust that make SSI credentials held by an identity subject more trustworthy and have greater utility.</blockquote><p>In that blog post, we described this as the <em>flywheel</em> for SSI adoption: trustworthy digital credentials that are cheaper to consume <em>and</em> produce compared to the current costs of KYC/KYB verification services will, over time, increase the volume of credentials in circulation and hence drive these costs down for <em>all</em> users and companies to make consumption cheaper and easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*UXCgkXTSRydS3nPpAVo35w.png" /><figcaption>The virtuous cycle of SSI adoption, <a href="https://blog.cheqd.io/the-business-models-of-identity-bb3336773727">accelerated by viable commercial models</a></figcaption></figure><p>As we saw in <strong>Trend #2</strong>, maintaining the <em>privacy</em> of users while they interact with companies is something that people <strong>deeply</strong> cared about. After all, if the gains that were gained from adopting self-sovereign identity were compromised by correlating payments recorded on an immutable ledger, these benefits are washed away. Obviously, cheqd will be designing and building with this in mind!</p><p><strong>70.3%</strong> of respondents from the expert audience agreed with our internal thinking that <strong>privacy-preserving payment mechanisms for identity exchange</strong> would have a large impact on driving SSI adoption. The challenge, so far, has been models that achieve <em>value exchange</em> while maintaining privacy in transactions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FDC46C%2F1%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FDC46C%2F1%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FDC46C%2Fplain-s.png%3Fv%3D1&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="800" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/36ba56e37526153f36ce51d37ef2fb5f/href">https://medium.com/media/36ba56e37526153f36ce51d37ef2fb5f/href</a></iframe><p>The <a href="https://sovrin.org/library/sovrin-protocol-and-token-white-paper/">Sovrin whitepaper in 2018 proposed a payment mechanism called <strong><em>holder-pays-issuer</em></strong></a>; an example of this is when I pay a government agency a fee to be issued a passport document. There’s a direct exchange of value here since it costs the government agency <em>some</em> money to process the request.</p><p>This model can also be extended to <strong><em>verifier-pays-holder</em></strong>; an example of this would be if <em>I</em> charged a bank that wants to KYC me for access to a copy of a digital passport credential. These two models clocked in at about <strong>32–41% of respondents believing holder-pays-issuer or verifier-pays-issuer would have a large impact</strong>.</p><p>However, our hypothesis here at cheqd has always been that while there may be <em>some</em> credentials where people are willing to “buy” them (paying to get the credential) or where companies would be willing to “buy” the rights to have a peek at a holders’ wallet, it would be hard to convince all people in an ecosystem to change their behaviour towards this.</p><p>What we believe is a more viable commercial model is one where <strong><em>verifier-pays-issuer</em></strong>, i.e., the recipient of the information pays the person who created the credential. <strong>62.2% of the expert audience respondents said verifier-pays-issuer would have a “large impact” on SSI adoption</strong>.</p><p>We don’t take it lightly that establishing such a model is <em>hard</em> to do while maintaining privacy. Our methodology here is to <em>not</em> create a locked credential — as that breaks interoperability and portability — but to allow issuers to charge for access to the revocation status of a credential.</p><blockquote><strong>Drivers licenses as an example of verifier-pays-issuer</strong></blockquote><blockquote>I could show my drivers license to at a grocery store to prove my age when buying alcohol. Since the checkout staff only care about deriving my age from the date of birth, they don’t need to care whether the drivers license is <em>actually</em> valid (e.g., it could have been “cancelled” if it was reported as stolen) as long as it is document that was issued by a competent authority. <strong>This is analogous to showing a Verifiable Credential, where the recipient can see that the credential is cryptographically untampered</strong>.</blockquote><blockquote>However, if I took the <em>same</em> drivers license to go rent a car, the car rental agency would likely way to check if the license was issued by a competent authority <em>and</em> that it wasn’t otherwise disqualified/revoked (e.g., reported as stolen, revoked due to dangerous driving, etc). <strong>This is analogous to presenting the Verifiable Credential and being able to read it being free, with the receipient/verifier having the <em>option</em> of paying for a revocation status check</strong>. The revocation status here is an attribute of the drivers license <em>document</em> controlled by the issuer, and <em>not</em> an attribute of the license holder themself.</blockquote><p>It’s important to clarify here that there is no one-size-fits-all, and we don’t plan on <em>mandating</em> any particular price point for credentials on the cheqd network. Instead, we believe that <em>some</em> credentials will likely be free to consume as well as check revocation statuses for, <em>some</em> will be charged out by holders of the credentials, and <em>some</em> will be “free” to present with an additional charge to check revocation status.</p><p>On that point, we recognise that having <strong>stable-pricing mechanisms</strong> is important for this economy of function. <strong>40.6% of respondents said stable pricing would make a large impact</strong>, with <strong>45.9% saying it would make a moderate impact</strong>. This aligns with our thinking in terms of how we plan on <a href="https://blog.cheqd.io/cheqds-product-vision-for-2022-6a92e8e4d296">handling payments in stable dollar-equivalent payment means such as stablecoins</a>. It forms part of <a href="https://blog.cheqd.io/cheqds-tokenomics-for-ssi-explained-part-3-4c6a813dee88">our tokenomics vision that encourages flexibility and competition in the market</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8rRFtu8TgQU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8rRFtu8TgQU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8rRFtu8TgQU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a9b098cef21ecbaab5e90c0f9e9ae177/href">https://medium.com/media/a9b098cef21ecbaab5e90c0f9e9ae177/href</a></iframe><h3><strong>Trend #4: </strong>Identity is a <em>foundational</em> building block for DeFi and Web 3.0</h3><p>cheqd is a rapidly-growing digital identity startup, and we always want to ensure that we’re targeting our resources on areas that will have the greatest impact/traction.</p><p>While it may not be 100% correlatable, instead of asking our survey audience <em>generically</em> about where self-sovereign identity might have the most impact, we phrased the question to ask them where <em>we</em> should focus our efforts.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FXZGkH%2F5%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FXZGkH%2F5%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FXZGkH%2Fplain-s.png%3Fv%3D5&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="600" height="478" frameborder="0" scrolling="no"><a href="https://medium.com/media/88971a5959b9e767166b71739c748414/href">https://medium.com/media/88971a5959b9e767166b71739c748414/href</a></iframe><p>DeFi and Web 3.0 applications are unique in the sense that <a href="https://future.a16z.com/decentralized-identity-on-chain-reputation/">“your reputation travels with you”, as described by a16z</a>. Web 3.0 services have a high degree of <em>switchability</em>: don’t like a particular wallet, exchange, or dApp? There’s probably a different app or service to which you can port your user experience to while retaining history.</p><p>Regulations such as <a href="https://notabene.id/product-travel-rule">the Travel Rule bring new compliance requirements on crypto businesses</a> (which <a href="https://notabene.id/">Nota Bene</a> focuses on), and as more regulators get interested in “<a href="https://www.reuters.com/business/finance/digital-dollar-project-launch-five-us-central-bank-digital-currency-pilots-2021-05-03/">digital dollars</a>” or <a href="https://en.wikipedia.org/wiki/Central_bank_digital_currency">Central Bank Digital Currencies (CBDCs)</a>, <a href="https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-blockchain">cryptocurrencies will face greater scrutiny</a>. Other efforts have arisen more natively from the blockchain industry, such as <a href="https://www.centre.io/verite">Centre Consortium’s Verite</a>, which aims to <a href="https://www.centre.io/blog/welcome-to-verite-a-message-from-centre-ceo-david-puth">bring decentralized identity to crypto finance</a>.</p><p>A lot of these <a href="https://blog.cheqd.io/why-centralised-decentralised-finance-cedefi-and-self-sovereign-identity-ssi-work-together-7e49d0e0993a">CeDeFi use cases above are a variation of Know Your Customer (KYC) and Know Your Business (KYB) processes</a> — but the concept of identity isn’t <em>just</em> related to KYC / KYB. For instance, it’s painfully common for <a href="https://www.ledger.com/academy/what-is-a-rug-pull">low-reputation crypto projects to be a “rug pull”</a>. (<a href="https://twitter.com/sytaylor">Simon Taylor</a>’s <a href="https://sytaylor.substack.com/"><em>Fintech Brain Food</em> newsletter</a> covers the intersection of DeFi and identity pretty well on a regular basis.)</p><p>Interestingly, our survey respondents were relatively lukewarm towards the idea of applying SSI to traditional finance (or, “TradFi”). Our hypothesis is that this might be due to either…</p><ul><li>…an acknowledgement that the traditional finance sector moves <em>very slowly</em>. We’d phrased the question as what we should focus on <em>this</em> year.</li><li>…a bias due to our audience demographics.</li></ul><h4>The intersection of identity and NFTs</h4><p>Much like the issue of uncertain reputation in the case of <em>“Who’s behind this particular crypto transaction, anyway?” </em>— as demonstrated in <a href="https://www.bloomberg.com/news/articles/2022-03-17/nft-price-jump-before-deal-reignites-market-manipulation-chatter">the case of potential insider-trading of the Meebits NFT collection</a> or <a href="https://blog.chainalysis.com/reports/2022-crypto-crime-report-preview-nft-wash-trading-money-laundering/">Chainalysis’s report on rampant “wash trading” for these digital assets</a>. A transaction involving a valuable NFT has the same issues as a high-value (fungible) token transfer does. <a href="https://www.theverge.com/2022/2/15/22935143/opensea-nft-metalink-launch-verified-dm-scammers-discord">OpenSea, one of the world’s largest NFT marketplaces, had to bring in special countermeasures to combat scammers</a> who pretended to be from their <em>own</em> support team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Lf7idE2J7AQ7WwT6si3u1Q.jpeg" /><figcaption><a href="https://boredapeyachtclub.com/#/">Bored Ape Yacht Club (BAYC)</a> NFTs</figcaption></figure><p>Widespread interest in the NFT space is regardless <a href="https://www.windley.com/archives/2021/10/nfts_verifiable_credentials_and_picos.shtml">creating a <em>dangerous</em> proliferation of projects that attempt to create “digital credentials” using NFTs</a>. <em>Pseudonymous</em> identity, tied to a user handle or to a wallet address — the way that an NFT would be — is still an <em>identity</em>. The fundamental problem with using transferrable tokens to handle identity or reputation is that it’s hard to determine whether <a href="https://future.a16z.com/reputation-based-systems/">the reputation was earned or bought</a>. Think of an employee pass, a driver&#39;s license — or even something more pseudonymous such as a gamer profile. These are digital footprints that are <em>earned</em> through effort, and should <em>not</em> be transferrable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jL5hCf9axMFVbnbi" /><figcaption><a href="https://ens.domains/">Ethereum Name System (ENS) domains </a>— like the one above — make the user experience of wallets simpler with the trade-off of making interactions more correlatable</figcaption></figure><p>Then there’s the issue of how strongly correlatable and privacy-leaking NFTs can be, due to the nature of them being linked to on-chain handles such as <a href="https://ens.domains/">Ethereum Name System (ENS) domains</a>. Many people willingly <a href="https://twitter.com/search?q=.eth&amp;src=typed_query&amp;f=user">mention their .eth addresses on their social media, such as Twitter</a>, making it trivially easy to follow <em>any</em> interactions with other wallet addresses, and understand what specific NFTs/assets <em>that</em> particular person owns.</p><p>It’s interesting to see the emphasis on DeFi / Web 3.0 in contrast to NFTs. This is a strong sign that there is an understanding of the distinction between these, despite the overall dominance of NFTs adoption in the marketplace. NFTs were the <em>lowest-ranked</em> use case in our survey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1_dGRadr1kdL4Z6jsgZyuA.png" /><figcaption><a href="https://pestcontroloffice.com/auth1.asp">Pest Control</a> is the official authentication group for Banksy artwork</figcaption></figure><p>With <a href="https://www.nytimes.com/2021/03/11/arts/design/what-is-an-nft.html">valuations of non-fungible tokens such as Bored Ape Yacht Club (BAYC) soaring exponentially</a>, NFT buyers may also care about the provenance of their digital artwork. This doesn’t mean the same as KYC: for instance, <a href="https://pestcontroloffice.com/auth1.asp">the official artwork authentication group for Banksy is a service called Pest Control</a>. Many NFT artists also similarly skew towards pseudonymous identities and may want to offer the assurance on the provenance of <a href="https://www.vice.com/en/article/5dgzed/what-the-hell-is-right-clicker-mentality">easily right-clickable</a> digital artwork — which helps provide assurance that maintains high valuations for an NFT collection — while preserving the privacy of buyers, sellers, and creators.</p><h4>The case for self-sovereign identity in DeFi/Web 3.0</h4><p>One of the breakout use cases we saw for SSI was <strong>“one-click sign-in with cheqd”</strong>, with identity verification baked into onboarding. This is analogous to the ubiquitous <em>Login with Google / Facebook / Twitter / [insert other large Web 2.0 service] </em>buttons that you may see online. (More recently, <a href="https://medium.com/magiclabs/magic-raises-27m-to-future-proof-authentication-79d8c63b2813">Magic.link raised a $27 million Series A</a> to bring such single sign-on technology to Web 3.0 apps as well.)</p><p>However…the traditional <em>Login with X</em> button <strong>doesn’t</strong> prove my <em>real</em> identity: it’s <em>just</em> a shortcut method to bypassing a username and password setup. You wouldn&#39;t really expect a username+password to be sufficient enough to prove reputation in the context of Know Your Customer (KYC), and also in scenarios where <em>pseudonymous</em> identity is sufficient. For example, a lot of decentralised finance (DeFi) or <a href="https://ethereum.org/en/dao/">decentralised autonomous organisations (DAOs)</a> may not require KYC in the traditional finance (TradFi) sense, but would perhaps care about preventing <a href="https://en.wikipedia.org/wiki/Sock_puppet_account">sockpuppet accounts</a> from influencing governance decisions in their community.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FAkSCR%2F5%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FAkSCR%2F5%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FAkSCR%2Fplain-s.png%3Fv%3D5&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="600" height="375" frameborder="0" scrolling="no"><a href="https://medium.com/media/35b321cf25f1065201e4da1cf6250583/href">https://medium.com/media/35b321cf25f1065201e4da1cf6250583/href</a></iframe><p>Overall, we saw strong interest in this space on <em>pseudonymous</em> forms of identity and online reputation to various degrees. Crypto adopters might care about an <em>inherently</em> private means of proving their own reputation, the provenance of digital assets, or strong privacy-preserving mechanisms for validating whether they are transacting with the <em>actual</em> person/project they intend to interact with.</p><p>In the SSI context, one of the areas we’re keen to explore is to move beyond the usage of <a href="https://github.com/decentralized-identity/.well-known">“well-known URIs” (Uniform Resource Identifier) to determine whether a Decentralized Identifier (DID) is trustworthy</a>. This is achieved by tying a DID back to a web endpoint/domain name…which ultimately anchors things back to the <em>very</em> centralised <a href="https://en.wikipedia.org/wiki/Public_key_infrastructure">public-key infrastructure (PKI)</a> that DIDs aim to disrupt.</p><p>A pseudonymous online reputation is <em>also</em> valuable for traditional real-world and Web 2.0 services. We explore this in the next section.</p><h3>Trend #5: Healthcare, Social Media, and Government use cases lead the pack among “traditional” sectors where SSI can be applied</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FkR6Ab%2F4%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FkR6Ab%2F4%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FkR6Ab%2Fplain-s.png%3Fv%3D4&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="600" height="902" frameborder="0" scrolling="no"><a href="https://medium.com/media/5f1f1c144267a92324aa515ca49c701e/href">https://medium.com/media/5f1f1c144267a92324aa515ca49c701e/href</a></iframe><h4>Healthcare &amp; Travel</h4><p>The Covid-19 pandemic has undoubtedly been one of the largest-scale and most deeply-impactful periods in recent human memory, with loss of life and health effects that will likely linger for decades. It has also been a period of <a href="https://www.ben-evans.com/benedictevans/2020/4/13/covid-and-forced-experiments">“forced experiments”</a> that accelerated the adoption of digital/online services, as large parts of the world came to grips with new realities of what a hybrid workforce looks like.</p><p><a href="http://news.windley.com/issues/building-an-ssi-ecosystem-health-passes-and-the-design-of-an-ecosystem-of-ecosystems-technometria-issue-16-648982"><em>“How do I prove my Covid-19 vaccination status, or test results, with a high degree of trustworthiness?”</em> has been an especially important question that societies and governments</a> have had to grapple with. Given this lived experience, it’s unsurprising that <strong>healthcare</strong> stood out as one of the top use cases in our survey. Covid-19 vaccination/testing results, provided through self-sovereign digital credentials, provide one possible solution to this question — without the need to create massive, global/regional databases of health records (arguably a bad idea) or having to rely on paper/PDFs (easily spoofed).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*lPUKpkOcfTrTGjNTRjLo-w.png" /><figcaption>A wide range of airlines are trialling Covid-19 records under the <a href="https://www.iata.org/en/youandiata/travelers/iata-travel-pass-for-travelers/">IATA Travel Pass scheme</a>, built on SSI credentials</figcaption></figure><p>For example, one of cheqd’s key partners — <a href="https://www.evernym.com/">Evernym</a> — built the <a href="https://www.evernym.com/travelpass/">International Airport Transport Association (IATA)’s Travel Pass scheme</a>. Local governments, health agencies, and international organisations such as IATA allow travellers to <a href="https://www.iata.org/en/youandiata/travelers/iata-travel-pass-for-travelers/">easily, securely, and digitally prove their compliance with Covid-19 regulations</a>. This is now officially accepted by <a href="https://www.iata.org/en/pressroom/travel-pass-mediakit/">dozens of airlines and governments around the world</a>, as the world takes tentative steps to re-open.</p><blockquote>cheqd’s co-founders have personal/professional experience with the use of SSI in travel and healthcare…</blockquote><blockquote><strong>Fraser Edwards (CEO)</strong> worked on the <a href="https://ktdi.org/"><strong>Known Traveler Digital Identity (KTDI)</strong> initiative</a>, a collaboration for the use of SSI digital ID for international travel between the World Economic Forum (WEF), the Dutch government, and the Canadian government.</blockquote><blockquote><strong>Ankur Banerjee (CTO)</strong> was one of the key architects for the early trial phase of <a href="https://beta.staffpassports.nhs.uk/">NHS Digital Staff Passports</a>. Since then, <a href="https://www.nhsx.nhs.uk/information-governance/guidance/digital-staff-passport/">Digital Staff Passports has evovled to an NHSX initiative</a> being rolled out across certain NHS trusts with invovlement from <a href="https://truu.id/">Truu</a> (a cheqd network partner), <a href="https://docs.microsoft.com/en-us/azure/active-directory/verifiable-credentials/">Microsoft (who built Azure AD Verifiable Credentials)</a>, <a href="https://condatis.com/case-studies/nhs-digital-staff-passport/">Condatis</a>, and Evernym.</blockquote><h4>Government</h4><p>Without the involvement of governments across the world, these healthcare (and travel) use cases described above would have never really seen the light of day. One of the pioneers in terms of laying legal/regulatory framework guidance as well as funding technical research in this has been <strong>the European Union government</strong>, especially through its <a href="https://www.ngi.eu/">Next Generation Internet Initiative</a>: the <a href="https://essif-lab.eu/"><strong>European Self-Sovereign Identity Framework Lab (eSSIF-Lab)</strong></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VL2t0CoQ5zLZFHQLYqo3XQ.png" /><figcaption>European Union’s <a href="https://essif-lab.eu/">Self-Sovereign Identity Framework Lab (eSSIF-Lab)</a> is one of the</figcaption></figure><blockquote>Read <a href="https://www.evernym.com/blog/eu-digital-identity/">Evernym’s analysis of the <strong><em>EU Digital Identity Architecture and Reference Framework</em></strong></a>, written in collaboration with <a href="https://www.validatedid.com/">ValidatedID</a>, <a href="https://www.intesigroup.com/en/">Intesi Group</a>, and <a href="https://www.ilabs.ai/">iLabs</a> which explains the latest developments in how the EU guidance impacting SSI is evolving.</blockquote><p>It’s no surprise that the EU, with its multi-nation bloc, recognised the need for portable digital identity credentials that would work across all the EU nations without needing to resort to massive EU-wide databases. The <a href="https://ec.europa.eu/digital-building-blocks/wikis/display/ebsi"><strong>European Blockchain Services Infrastructure (EBSI)</strong></a> and eSSIF-Lab provide an early look at what an ecosystem focussed on user-controlled digital identity could look like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nAgyyoOJ4RlwVMrYQBH9DA.png" /><figcaption>European Blockchain Services Infrastructure (EBSI) potential market, by the numbers</figcaption></figure><p>Other early pioneering government initiatives in self-sovereign identity are <a href="https://idunion.org/?lang=en">the <strong>IDUnion network</strong> in Germany</a> (which has cheqd network partners <a href="https://danubetech.com/">Danube Tech</a>, <a href="https://esatus.com/?lang=en">eSatus</a>, <a href="https://eecc.info/">European EPC Competence Center</a>, and <a href="https://spherity.com/">Spherity</a> as members); and <strong>the </strong><a href="https://trbouma.medium.com/canada-enabling-self-sovereign-identity-efcfda2aa044"><strong>Government of Canada</strong></a> with <a href="https://tykn.tech/digital-identity-canada/">has a rich ecosystem of national and provincial initiatives</a> for SSI.</p><p>Governments have a strong fit with the identity space, as a lot of the “genesis” of identity attributes are often derived from government-issued credentials. Many governments around the world are also keen on improving the citizen/resident experience, building on technology stacks that <em>don’t</em> have strong vendor lock-in.</p><p><strong>Trend 5</strong>, therefore, helps us show the growing interest in how the <em>first</em> credentials in any SSI ecosystem can be created from government entities.</p><h3>Methodology</h3><p>We feel it’s worth providing some insight into how we constructed and ran the survey. Overall, we had <strong>114 completed respondents</strong> to the general survey (with a <strong>completion rate of 65.8%</strong>; pretty high given that <a href="https://www.questionpro.com/blog/good-survey-response-rate/#:~:text=Benchmarks%20for%20a%20good%20rate%20of%20survey%20responses">average survey completion rates are around 10–33%</a>). The estimated audience/population size this survey was offered to was ~12,000. Taking the sample size of respondents into consideration, it allows us to state a <strong>confidence level of 95% </strong>(with a <strong>margin of error of 9%</strong>) for the trends and conclusions drawn from this survey.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FD17yv%2F4%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FD17yv%2F4%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FD17yv%2Fplain-s.png%3Fv%3D4&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dwcdn" width="600" height="587" frameborder="0" scrolling="no"><a href="https://medium.com/media/4b40e72d1b3c0517d9e790d9b426713b/href">https://medium.com/media/4b40e72d1b3c0517d9e790d9b426713b/href</a></iframe><p>We also asked all respondents to self-score their knowledge of decentralised digital identity and Web 3.0 from low to high. Our audience composition likely resulted in most rating themselves average to high (between 5–10 on our scale), due to their industry background in these topics.</p><p>At the end of the general survey, we identified 45 respondents as either pre-qualified experts from our partners or self-identified as having a high degree of knowledge of digital identity / Web 3.0. We had <strong>37 completed respondents</strong> to this <strong>deep-dive survey</strong> (with a <strong>completion rate of 84.6%</strong>). This group included experts from some of the world’s most prestigious early-stage to late-stage digital identity companies and Web 3.0 partners. Given the estimated population size (~90 qualified individuals) this survey was offered, the sample size of respondents allows us to state a <strong>confidence level of 90% </strong>(with a <strong>margin of error of 10%</strong>) for additional insights derived from the expert audience group.</p><h4>Tools</h4><p>We used <a href="https://typeform.com/">Typeform</a> for this survey as we both valued the branching options it offers, whilst also appreciating the overall user experience it offers. One of the consistent pieces of feedback that we received was that the respondents <em>enjoyed</em> answering the survey and found it a “slick” experience.</p><p>One of the issues we encountered with Typeform was that we used its <em>auto-estimation</em> feature to calculate the estimated length of the survey (in minutes). This led us to state that the survey would take “7+ minutes” to complete. What we didn’t realise at the time is that <a href="https://www.typeform.com/help/a/time-to-complete-360052533131/">Typeform stops counting survey length after 7 minutes</a>. We also validated the “7 minutes” length by running through the survey internally, but during this internal testing, we didn’t provide extended free-text answers — which many of our respondents did. As a consequence, the average completion time was <strong>approx. 31 minutes</strong>, which was significantly higher than the expectations we set with people. (Since this is an average figure, some people would have spent significantly shorter, while others longer. This may even include the time when the survey was left open in the background in a tab.)</p><p>Another issue we ran into was Typeform being unable to export answers to <em>multi-select</em> questions in a consistent format, which took us 2+ weeks of back-and-forth with their customer support team. (Thankfully, they were proactive in offering us service credits.)</p><p>Despite the challenges we faced, the extremely high completion rate and overall positive sentiment towards the survey showed us that when a survey is designed to be engaging and <em>feel</em> quick, it makes respondents likely to respond in detail and offer rich insights. We’ll be more careful about setting the expectations right when designing future surveys on the time commitment needed. Typeform enabled us to build this experience, and we foresee us continuing to use it, above tools such as SurveyMonkey.</p><p>We also used <a href="https://www.datawrapper.de/">Datawrapper</a> to generate visualisations that could be embedded easily, since they offer the ability to have dynamic and interactive embeds, the ability to download static images, and auto-suggest “sensible” defaults for visualisations. They also guarantee to keep the charts alive regardless of whether our account there is deleted, thus preventing link rot, and don’t track as much data as competing solutions such as Google Charts.</p><h4>Question formulation</h4><p>Generally, we tried to keep to consistent usage of ranking scales and <a href="https://en.wikipedia.org/wiki/Likert_scale">Likert Scales</a> because these offer a clear picture of how badly something is wanted, rather than a simple indication that there is somewhat of a desire without a clear way of comparing one to another. For example, just asking respondents whether to pick amongst a list would tell us what percentage overall voted for a choice, but wouldn’t tell us how they ranked the options <em>against</em> each other when forced to make the choice.</p><p>Similarly, the usage of “<a href="https://en.wikipedia.org/wiki/Likert_scale">Strongly Agree to Strongly Disagree</a>” allows us to understand degrees of agreement/disagreement to a statement, rather than a simple yes/no binary choice. We took a lot of care to phrase statements in a neutral fashion (as far as possible) and then present a choice against Likert Scale, as well as blending in statements that implied the <em>opposite</em> sentiment to previous statements — as this allows us to check whether the spread of opinions is a mirror image or not. This helps validate whether someone is simply going down a column, picking the same choice, to breeze through the survey as quickly as possible.</p><p>We wanted to make this survey overall more quantitative as it is far easier to retrieve more results, plus analyse and inform our strategy with a more data-driven approach. That said, the offering of free-text input proved worthwhile; we loved the range of comments and opinions, as can be seen from some of the quotes we pulled out above.</p><h4>Audience demographics of the respondents</h4><p>When approaching this survey, we had two key objectives. First, we wanted to uncover deep insights from our partners that could help strengthen our understanding of what is most needed from cheqd. Secondly, we wanted to be open enough to resonate with those with less specific knowledge, since such persons can help provide a more objective and generalist perspective on us as a company and the direction we should head in.</p><p>We created this survey in a way that not all questions were meant to be completed by every respondent. For example, if someone was to indicate in certain questions that they held limited knowledge of self-sovereign identity, we used branching logic to ensure these individuals did not provide answers without enough prior insight as this could taint the overall results. We also chose to accommodate a larger audience to improve the overall reliability survey, as if we had just surveyed those immediately involved in SSI (i.e. current and prospective partners), we’d likely witness a level of confirmation bias about the overall level of understanding of the space and what is more sorely needed.</p><p>We also noted that surveys that take too much time drastically worsen the overall results, as questions towards the beginning get more love. Therefore, on top of leveraging branching logic to help improve the accuracy of results, we also used the branching logic feature to help limit time spent on questions that either didn’t have relevance to the respondent or would leave them unable to answer, thereby simply selecting any option so to proceed.</p><h4>Anonymity/pseudonymity of respondents</h4><p>This was important to us for obvious reasons: both for what we stand for at cheqd but also for the validity of results. When forced to provide their identity people will generally answer less honestly and often overly positively. However, we did want to be able to guide respondents down the right path based on their level of experience and area of expertise.</p><p>To balance these somewhat competing needs, we opted to ask for aggregated demographic information to guide the branching logic of the survey and waited until the end to offer the opportunity to provide any more personal information.</p><h3>What’s next</h3><p>To recap, we identified the following key trends from our survey:</p><ol><li><strong>Trend #1: </strong>Maintaining privacy and control of their own data is of paramount importance to web users</li><li><strong>Trend #2: </strong>Users — and the companies/organisations where they want to use self-sovereign identity — have vastly different motivations</li><li><strong>Trend #3:</strong> Privacy-preserving commercial models for digital identity exchange could radically accelerate the adoption of self-sovereign identity</li><li><strong>Trend #4:</strong> Identity is a foundational building block for DeFi and Web 3.0</li><li><strong>Trend #5</strong>: Healthcare, Social Media, and Government use cases lead the pack among “traditional” sectors where SSI can be applied</li></ol><p>There is plenty more that could be extracted from the survey, which is a testament to our community and respondents for providing such thought-provoking insight. Stay tuned for our following blog posts, where we go into greater detail about trends in the Web 3.0/Cosmos ecosystems, and in the standards stack of self-sovereign identity.</p><p>All of our charts can be found on <a href="https://app.datawrapper.de/river">Datawrapper River</a> and are reusable under a <a href="https://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 License</a>. The <a href="https://cheqd.typeform.com/report/qJqKCHXw/5Wy7Sf3vZhudFAeD">aggregated, non-identifiable survey responses</a> can also be accessed under the same licensing terms for anyone who is interested in re-using this survey.</p><p><em>We’d love to hear your thoughts and take about the state of self-sovereign identity and how it intersects with the Web 3.0 ecosystem. To find out more about SSI and digital identity, follow </em><a href="https://www.cheqd.io/"><strong>cheqd</strong></a><em> on</em><a href="https://www.linkedin.com/company/cheqd-identity/"><em> LinkedIn</em></a><em> or</em><a href="https://twitter.com/cheqd_io"><em> Twitter</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b677926bcfc7" width="1" height="1" alt=""><hr><p><a href="https://blog.cheqd.io/top-5-trends-in-decentralized-self-sovereign-identity-and-privacy-preserving-technology-in-web-3-0-b677926bcfc7">Top 5 trends in Decentralized Self-Sovereign Identity and Privacy-preserving Technology in Web 3.0</a> was originally published in <a href="https://blog.cheqd.io/">cheqd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[cheqd’s product vision for 2022]]></title>
            <link>https://blog.cheqd.io/cheqds-product-vision-for-2022-6a92e8e4d296?source=rss-c5166068a656------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a92e8e4d296</guid>
            <dc:creator><![CDATA[Ankur Banerjee]]></dc:creator>
            <pubDate>Tue, 18 Jan 2022 11:28:41 GMT</pubDate>
            <atom:updated>2022-05-12T10:56:00.511Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>Co-authored by </em><a href="https://blog.cheqd.io/@zero-cool"><em>Fraser Edwards</em></a><em> (CEO/co-founder), </em><a href="https://blog.cheqd.io/@rosspower"><em>Ross Power</em></a><em>, and </em><a href="https://blog.cheqd.io/@alex-tweeddale"><em>Alex Tweeddale</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tyF8RZ7WEPpljvNddXZ3Bg.png" /></figure><p>We’re incredibly excited to begin the year after the successful launch of the <strong>cheqd network </strong>and <strong>CHEQ token</strong> at the end of 2021 and can’t wait to share with you what’s coming next. Read more about what we’ve achieved in <a href="https://www.cheqd.io/blog/a-year-in-review">cheqd’s 2021 year in review</a> from our CEO and co-founder, <a href="https://twitter.com/fraser_again">Fraser Edwards</a>.</p><p>This blog will offer insights into our priorities and next steps for the cheqd network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a3VDxslcjUiMtdNl" /><figcaption>cheqd’s ecosystem of partners: ranging from self-sovereign identity vendors to Web 3.0 companies</figcaption></figure><h3>Bringing onboard a wide range of partners and participants</h3><p>Our priority at <a href="https://www.cheqd.io/blog/welcome-to-a-new-era-for-decentralised-identity">the launch of cheqd network</a> was to establish a public, decentralised network with core decentralised identity functionality and governance mechanisms. It has been exciting to welcome <a href="https://explorer.cheqd.io/validators">45+ validators</a> on-board, including 20+ self-sovereign identity (SSI) application vendors, digital identity startups, investors, and Cosmos-native / cross-chain network validators. Many individual entities and organisations who participated as validators in the <a href="https://www.cheqd.io/blog/the-new-version-of-cheqd-testnet-is-out-were-gearing-up-for-the-mainnet-launch">cheqd testnet</a> also helped to make our software releases more stable and provided invaluable feedback, and we were excited to welcome many of them onto our mainnet as well.</p><p>Special shoutouts go to the <a href="https://app.osmosis.zone/">Osmosis DEX</a> team and <a href="https://www.mintscan.io/osmosis/proposals/84">community for incentivising out token pairs on the DEX</a>; <a href="https://github.com/notional-labs">Notional Labs</a> for relaying us to other Cosmos chains (and for a lot of support during the launch phase); and to <a href="https://cheqd.omniflix.co/">OmniFlix</a> for providing us with the ability to proving the ability to transfer, stake, and vote on governance proposals via their <a href="https://www.cheqd.io/blog/were-launching-our-network-very-soon-heres-how-you-can-get-ready">Keplr wallet integration</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-0j5dLusbxdauHdl" /><figcaption>Metrics from the <a href="https://explorer.cheqd.io/">cheqd blockchain explorer</a></figcaption></figure><h4>Key achievements, by the numbers</h4><ol><li>CHEQ was listed on <a href="https://app.osmosis.zone/">Osmosis</a>, the largest DEX (decentralised exchange) in the Cosmos ecosystem, with <a href="https://app.osmosis.zone/pool/602">CHEQ:OSMO</a> (<a href="https://info.osmosis.zone/pool/602">Osmosis pool #602 statistics</a>) and <a href="https://app.osmosis.zone/pool/617">CHEQ:ATOM</a> (<a href="https://info.osmosis.zone/pool/617">Osmosis pool #617 statistics</a>) liquidity pools established by the community.</li><li><a href="https://www.gate.io/trade/cheq_usdt">CHEQ was listed by Gate.io</a>, a <a href="https://coinmarketcap.com/view/centralized-exchange/">top 10 trading CEX</a> (centralised exchange), with millions of CHEQ tokens in volume traded. We hope to be available in more venues soon.</li><li>Approximately <a href="https://explorer.cheqd.io/">25% of the total supply of the network is being staked on validators</a>, giving our community the ability to reap staking rewards and participate in decentralised governance that controls the network.</li></ol><h3>TL;DR: What’s coming next in cheqd?</h3><p>We are excited to expand on <a href="https://www.cheqd.io/blog/welcome-to-a-new-era-for-decentralised-identity">our vision for a public, decentralised identity network</a> that establishes <a href="http://cheqd.io/blog/the-business-models-of-identity">business models for self-sovereign identity</a>. To do this, we will build on top of the core identity and token functionality that we shipped with our mainnet launch towards the end of last year. Future releases of cheqd product software would ship, once accepted by the network and community using governance proposals, at the end of every calendar month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v9DwVYAPSwtetnDgc7ZBkw.png" /><figcaption>cheqd product roadmap overview for 2022</figcaption></figure><p>Our three focus areas for product roadmap development in the year ahead can be broken down into:</p><ol><li><strong>Identity:</strong> Core identity functionality for our partners to build <a href="https://www.cheqd.io/blog/self-sovereign-identity-use-cases">compelling self-sovereign identity use-cases</a> on top of the cheqd network.</li><li><strong>Web 3.0 Core: </strong>Core Web 3.0 functionality adds deeper integration for our network and token into the Cosmos and other blockchain ecosystems.</li><li><strong>Web 3.0 Exploratory:</strong> Emerging Web 3.0 use-cases such as decentralised exchanges (DEX) ecosystems; decentralised autonomous organisations (DAOs); identity for non-fungible tokens (NFTs), and in general, DeFi applications.</li></ol><blockquote>We would love to hear feedback from our community and our partners on our product roadmap described below. Within the next few weeks, our team will launch a product roadmap survey that allows everyone to provide feedback on what matters to you and where we should be focussing. If you’re interested in taking part in this, please ensure you have <a href="https://share.hsforms.com/1CYZbxLdrQx2xMhXlSIR96Ac0rlz">signed up for our newsletter</a> or are in our <a href="https://t.me/cheqd">Telegram group</a>. Stay tuned for more details!</blockquote><h3>Deep-dive into cheqd’s product roadmap for 2022</h3><p>Our focus is to expand the utility of the cheqd network for decentralised identity use cases. This is our core mission and vision and — the reason why — we have such a broad interest within the self-sovereign identity (SSI) vendor ecosystem.</p><p>We want to get to a point, quickly, where we can provide compelling answers to <em>“What identity capabilities does cheqd network provide, and how do I build it into my apps as an app developer/software vendor?”</em></p><p>Equally important as a focus area is deeper integrations with the Cosmos and wider Web 3.0 ecosystem. Digital identity is a burning need across DeFi, CeDeFi, and “traditional” Web 2.0 apps that cuts across as a “horizontal”, as well as being extremely important in “verticals” such as NFTs and online/offline reputation.</p><p>In the sections below, we’ll talk you through our immediate product roadmap priorities, as well as future product improvements later in the year, based on these two categories.</p><h3>Quick Wins product roadmap items (Q1 2022)</h3><p>Each new release of cheqd software that we ship would aim for incrementally improving core functionality, which improves life for users (individual and enterprise), token holders, node operators and app developers. In this category (which we’ve called “Quick Wins”), we have product features and improvements where the approach is well-known and understood within the SSI and Web 3.0 industries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*No3sVWQXCOkvBu6MQxJ-GA.png" /><figcaption>Product roadmap items related to digital identity for cheqd in 2022</figcaption></figure><h3>Identity</h3><p>Much of the basic identity functionality is currently live on the cheqd mainnet, but we’ve been working on stability and security improvements (due to go-live by the end of January 2022) before we begin guiding app developers in earnest. Here are our product ideas in the identity space we believe will have the greatest impact in the short-term.</p><h4>Tutorials for developers on using the identity and token functionality of cheqd network</h4><p>Simple tutorials that help app developers answer the question <em>“How can I integrate cheqd into my app?”</em> is a clear improvement in developer experience we will offer soon. Our <a href="https://docs.cheqd.io/node/">documentation site</a> (and our <a href="https://blog.cheqd.io/">Medium blog</a>) will be the home for these resources.</p><p>We are also eternally grateful to the members of <a href="http://cheqd.link/join-cheqd-slack">our cheqd Community Slack</a> for helping each other out and often highlighting tips, tricks, and resources.</p><h4>Integrations with industry-standard identity projects such as DIF’s Universal DID Resolver project</h4><p>Not every app developer needs the ability to write Decentralised Identifiers (DIDs) onto the cheqd network ledger: some would only need the ability to query and resolve DID Documents for did:cheqd identifiers. Even developers who <em>do</em> want to write DIDs typically rely on projects such as <a href="https://github.com/decentralized-identity/universal-resolver">DIF’s Universal DID Resolver</a> to handle reading DIDs for a wide range of methods.</p><p>Publishing a Universal Resolver driver for did:cheqd will simplify the experience for SSI vendors and app developers to utilise REST APIs and other interfaces to resolve DIDs on the cheqd network.</p><h4>New &amp; improved decentralised identity functionality</h4><p>We designed <a href="https://docs.cheqd.io/node/architecture/adr-list/adr-002-cheqd-did-method">the did:cheqd method</a> to account for new developments in the World Wide Web Consortium (W3C) <a href="https://w3c.github.io/did-core/">Decentralized Identifiers (DIDs) specification</a> that are not present in <a href="https://hyperledger.github.io/indy-did-method/">the did:indy method</a>, such as the ability to have multiple controllers associated with a DID. We also believe that there are alternatives within the DID Core specification now (such as <a href="https://w3c.github.io/did-core/#verification-methods">Verification Methods</a>) that remove the need for separately publishing <a href="https://hyperledger.github.io/indy-did-method/#claim-def">credential definitions</a> as their own separate entity; and a more DID-spec compatible way of publishing schemas on ledger on the cheqd network.</p><p>We know though that there are still areas we can improve on. Looking further, we aim to publish an implementation report for our DID method against the <a href="https://w3c.github.io/did-test-suite/">DID Core Specification Test Suite</a> to transparently show what capabilities our DID method has, and a roadmap on how we aim to improve it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LYh_TUwg5d4qfAQyUE3Ujg.png" /><figcaption>Product roadmap items related to Web 3.0 Core for cheqd in 2022</figcaption></figure><h3>Web 3.0 Core</h3><h4>Wider integration with Cosmos ecosystem</h4><p>CHEQ tokens are currently only usable on the <a href="https://www.keplr.app/">Keplr Wallet</a> browser <a href="https://chrome.google.com/webstore/detail/keplr/dmkamcknogkgcdfhhbddcghachkejeap">extension for Chrome</a>, since only the browser plug-in supports <a href="https://github.com/chainapsis/keplr-wallet/blob/master/docs/api/suggest-chain.md">auto-discovering new Cosmos networks</a>.</p><p>We recognise that this is a clear area where we can improve the user experience for token holders, for instance, by providing native support for CHEQ tokens in <a href="https://cosmos.network/ecosystem/wallets">other Cosmos wallet applications and on mobile platforms</a>. Making CHEQ available on mobile wallet apps takes time, as wallet developers need to manually add support for the cheqd network and then get software updates approved by the Apple App Store or Google Play Store. (Foiled by centralised gatekeepers!)</p><p>We also know a niche of token holders in our community who prefer to protect their tokens with higher-grade security offered by hardware wallets (such as <a href="https://www.ledger.com/">Ledger</a>), which also require a manual approval and validation process.</p><p>Participation in governance proposals and staking to validators is currently possible due to our friends at <a href="https://cheqd.omniflix.co/">OmniFlix</a>, and without them, we would not have been able to launch our mainnet. We want to expand this in Q1, by offering further choices of platforms that offer this functionality to our token holders.</p><h4>Bridge to Ethereum networks</h4><p>As we build payment rails for digital identity (more on that below), we want to offer issuers, verifiers, and holders a choice on the means of settlement. We believe that widely-adopted <a href="https://en.wikipedia.org/wiki/Stablecoin"><em>stablecoins</em></a> such as <a href="https://en.wikipedia.org/wiki/USD_Coin">USDC</a> offer price-stable currencies to designate such transactions, and therefore bridging to Ethereum makes obvious sense.</p><p>We also want to provide access to the ability to acquire CHEQ tokens using ERC-based tokens, not just Cosmos-based tokens, and therefore further secure our decentralised governance on our proof-of-stake network.</p><h4><strong>Improved automation &amp; tooling for managing validator nodes on cheqd network</strong></h4><p>We’re thrilled with the engagement we’ve had to date from the 45+ node operators validating on the cheqd network. Many of these are SSI vendors new to the Cosmos ecosystem, and therefore, we want to significantly simplify the experience for running and managing validator nodes for the long-term health of the network.</p><p>We will also continue to maintain our testnet as a playground for app developers to build and test applications. In the coming weeks, we’ll launch a testnet faucet, making it easier to request test CHEQ tokens instead of the current manual process.</p><p>All of this will mean our own product &amp; engineering team can spend more time building groundbreaking functionality!</p><h3>Strategic product roadmap items (Q2 2022 and beyond)</h3><p>This category is for big, audacious goals (which we’ve called “Strategic”) for product features that are new, never-seen-before innovations that are tougher to implement because there’s a lot more research and development that goes into them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*No3sVWQXCOkvBu6MQxJ-GA.png" /><figcaption>Product roadmap items related to digital identity for cheqd in 2022</figcaption></figure><h3>Identity</h3><h4>Payment rails for digital identity exchange</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*alt3K7S0KA2m4CVy" /><figcaption>Payment flows in exchange for digital credentials overview for cheqd network</figcaption></figure><p>We believe that for self-sovereign identity to take a foothold in the Web 3.0 ecosystem, it needs customisable payment mechanisms that allow for various <a href="http://cheqd.io/blog/the-business-models-of-identity">different business models for Verifiable Credential (VC) exchange</a>. Our product principles when designing these payment rails are:</p><ol><li><strong>Payment mechanisms <em>must</em> be robust, secure, and privacy-preserving</strong>: The single most important feedback that we’ve heard time and again from the SSI community is they are cautiously optimistic about viable commercial models but don’t want it to come at the expense of compromising the privacy of data holders. We have dedicated a lot of time and research internally to define an implementation roadmap that allows us to achieve this, by leveraging the additional capabilities <a href="https://www.cheqd.io/blog/why-cheqd-has-joined-the-cosmos">switching to the Cosmos blockchain framework</a> gives us. The approach we aim to implement would offer capabilities beyond those currently defined in the <a href="https://github.com/hyperledger/aries-rfcs/blob/main/features/0075-payment-decorators/README.md">Hyperledger Aries Payment Decorator RFC</a>.</li><li><strong>No single payment fits every use case, so enable flexibility</strong>: Fundamentally, <em>cheqd isn’t going to mandate a single payment mechanism across our network</em>, as we recognise that different industries, use cases, and ecosystems have different needs. Some credentials (such as those issued by a government or regulatory agencies) will likely be free or priced to recover costs only, whereas other digital credentials may allow either issuers or the holders of credentials to charge the recipient. We aim to offer multiple options, thus offering choice to the issuers and/or holders of credentials to adopt models such as holder-pays-issuer (“As an individual, I’d like a way to pay the issuer of digital credential”, e.g., paying the government to get a digital passport); verifier-pays-holder (“As a recipient of a credential, I’m happy to pay a small fee to the holder”; e.g., the holder giving access to a digital passport credential); and verifier-pays-issuer (“As a recipient of a credential, I’m happy to pay the issuer of the credential a small fee for additional metadata”; e.g., checking the revocation status of a credential.)</li><li><strong>“Payment” doesn’t <em>necessarily</em> mean “locked” credential</strong>: A common misconception is that adding payments to an identity exchange flow means the credential is somehow “locked” (or encrypted), with access only granted on payment. That is certainly one possible model, but we also believe there are other, viable alternatives which <em>don’t</em> have the same hurdles. An example of this would be <a href="https://en.wikipedia.org/wiki/Freemium">freemium</a> models of payment, where basic credential exchanges are always free, and an optional payment may be made for access to certain metadata.</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8rRFtu8TgQU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8rRFtu8TgQU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8rRFtu8TgQU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a9b098cef21ecbaab5e90c0f9e9ae177/href">https://medium.com/media/a9b098cef21ecbaab5e90c0f9e9ae177/href</a></iframe><p>We presented a session called the <a href="https://www.youtube.com/watch?v=8rRFtu8TgQU"><strong>Seven Deadly Sins of Commercialising SSI</strong></a> at last year’s <a href="https://internetidentityworkshop.com/">Internet Identity Workshop (IIW)</a>, where we shared our thoughts on the gotchas of adding commercial models to decentralised identity. I encourage you to watch this video, as it lays out a lot of our internal thinking on how we plan on tackling these pitfalls.</p><h4>Client SDKs in more programming languages</h4><p>The current implementation of a client SDK that integrates identity and token functionality on the cheqd network is based on <a href="https://gitlab.com/evernym/verity/vdr-tools">Verifiable Data Registry (VDR) Tools SDK</a>, from one of our key partners <a href="https://www.evernym.com/">Evernym</a> (one of the largest SSI software vendors in the world, recently <a href="https://www.evernym.com/blog/joining-forces-with-avast/">acquired by cybersecurity software company Avast)</a>. VDR Tools SDK is an open-source library that is an offshoot of <a href="https://github.com/hyperledger/indy-sdk">Hyperledger Indy SDK</a>, which many SSI software vendors are familiar with and use in their products.</p><p>However, we also recognise that other software vendors prefer to use programming languages/frameworks based on JavaScript, Python, and Go (instead of Rust, which VDR Tools SDK uses). This could be down to other languages being easier to hire developers for, engineering choice to align with the rest of their tech stack, etc. We’ve had significant interest from SSI software developers who currently use <a href="https://github.com/hyperledger/aries-cloudagent-python">Hyperledger Aries Cloud Agent Python (ACA-Py)</a>, <a href="https://github.com/hyperledger/aries-framework-go">Hyperledger Aries Framework Go</a>, and <a href="https://github.com/hyperledger/aries-framework-javascript">Hyperledger Aries Framework JavaScript (written in TypeScript)</a> and have expressed a desire for cheqd network support in programming frameworks they currently use.</p><p>More broadly, to handle token functionality, Cosmos SDK offers <a href="https://docs.cosmos.network/master/core/grpc_rest.html">a variety of APIs using RPC, REST, and gRPC endpoints</a>, but this requires the client app developer to understand and construct Cosmos transactions. One of the ways we’re looking at making this simpler is to build alternatives to native CHEQ token support in VDR Tools SDK using <a href="https://github.com/cosmos/cosmjs">CosmJS</a>, a widely-adopted TypeScript library for handling Cosmos interactions.</p><p>This would offer flexibility to app developers and software vendors with a choice of different programming frameworks to simplify the task of integrating cheqd’s identity <em>as well as</em> token functionality in their existing apps.</p><h4>Better interoperability and support for emerging identity standards</h4><p>We are also excited to explore the possibilities that are enabled by emerging standards in identity, such as <a href="https://w3c-ccg.github.io/ldp-bbs2020/">BBS+ signatures</a> (read more for an explanation on <a href="https://www.evernym.com/blog/bbs-verifiable-credentials/">why BBS+ signatures provide significant advancements to Verifiable Credentials</a>) and Decentralized Identity Foundation (DIF) <a href="https://identity.foundation/waci-presentation-exchange/">Wallet and Credential Presentation Exchange (WACI PEx)</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LYh_TUwg5d4qfAQyUE3Ujg.png" /><figcaption>Product roadmap items related to Web 3.0 Core for cheqd in 2022</figcaption></figure><h3>Web 3.0 Core</h3><h4><strong>Native, cross-chain identity primitives for Cosmos ecosystem</strong></h4><p>DIDs on the cheqd network are specifically stored on our mainnet ledger. Since <a href="https://w3c.github.io/vc-data-model/">Verifiable Credentials (VCs)</a> are stored off-ledger for privacy reasons, integrating identity functionality doesn’t necessarily need on-chain resolution, unlike most other blockchain use cases.</p><p>However, the <a href="https://cosmos.network/ecosystem/apps">Cosmos blockchain ecosystem</a> also has other identity efforts underway, such as the <a href="https://github.com/allinbits/cosmos-cash">Cosmos Cash DID method</a> and <a href="https://github.com/cosmos/cosmos-sdk/discussions/9337?sort=top">Interchain Identifiers (IIDs)</a> which we are keeping our eyes on and are excited to see materialise. We are proud to be backed by <a href="https://www.cheqd.io/press/tendermint-ventures-backs-cheqd-in-latest-investment-round">Tendermint Ventures</a> (among others) and want to bring our expertise in digital, self-sovereign identity that can be leveraged by all Cosmos projects.</p><h4><strong>Smart contracts using CosmWasm</strong></h4><p>For those who are not aware of the term, <a href="https://www.cosmwasm.com/">CosmWasm</a> is <a href="https://blog.cosmos.network/announcing-the-launch-of-cosmwasm-cc426ab88e12">a secure, multi-chain smart contract framework that uses WebAssembly (Wasm) virtual machines on top of the Cosmos SDK</a>.</p><p>CosmWasm will allow us to customise further aspects of payment mechanisms offered via the cheqd network, for instance, allowing for reputation management of issuers/verifiers, and techniques to preserve privacy during credential exchanges. It will also enable third-party app developers to extend the functionality of cheqd products.</p><p>Similar to the previous cross-chain identity primitives goal, CosmWasm also utilises the <a href="https://ibcprotocol.org/">Inter-Blockchain Communication (IBC) Protocol</a> for multi-chain support.</p><h4><strong>Establish ourselves as a leader in decentralised governance for identity</strong></h4><p>Core to our vision for the cheqd network is inspiring others within the identity space to <a href="https://www.cheqd.io/blog/entropy-in-decentralised-governance-part-three">make decentralised governance a de-facto aspect of identity networks</a>. Many existing decentralised identity networks rely on closed, permissioned governance mechanisms. This is due to a belief that controlling the validators (who can write to the network) somehow adds “more trust”.</p><p>But…the reality is that even on permissioned identity networks, validators <em>don’t</em> attest to or validate the <em>contents</em> of a DID document for accuracy. Limiting governance to a select set of participants is sometimes <em>really</em> due to technical limitations, which then gets <a href="https://en.wikipedia.org/wiki/Retroactive_continuity">retconned</a> to also include governance frameworks.</p><p>In our opinion, trust, whether in the <em>contents</em> of DID documents or credentials, <a href="https://www.trustoverip.org/news/2021/11/12/toip-releases-additional-tools-for-governance-and-trust-assurance-in-digital-trust-ecosystems/">sits within trust frameworks as described by Trust Over IP (ToIP)</a>. Just because a user presents a digital credential, even in current SSI networks assuming that as trustworthy isn’t and shouldn’t be automatic.</p><p>We see DID reads/writes on the cheqd network ledger behaving as a neutral <a href="https://guide.transmute.industries/learning-center/why-verifiable-credentials/verifiable-data-registries/">verifiable data registry</a>, backed by <a href="https://docs.cheqd.io/governance/">a public permissionless governance framework</a> that ensures <em>not even the core team at cheqd</em> can unilaterally make changes. Since governance votes on a proof-of-stake Cosmos network can also be cast by token holders, for the first time it also offers the actual users and organisations — our community — the ability to participate in and influence the direction of the cheqd network.</p><p>By enabling democratic, decentralised decision making and governance at the network level, organisations, and in particular, consortiums, will be able to create specific ecosystem governance frameworks quickly and efficiently, which tie into cheqd network governance. This will increase the efficiency of decisions whilst maintaining full transparency for those involved in the ecosystem.</p><p>We’ll also be continuing to engage with working groups in the SSI space, such as <a href="https://identity.foundation/">Decentralized Identity Foundation (DIF)</a>, <a href="https://trustoverip.org/">Trust over IP (ToIP)</a>, <a href="https://decentralized-id.com/web-standards/w3c/">World Wide Web Consortium (W3C)</a> <a href="https://w3c-ccg.github.io/">Credentials Community Group (CCG)</a>, <a href="https://ec.europa.eu/cefdigital/wiki/pages/viewpage.action?pageId=379913698">EU Self-Sovereign Identity Framework (eSSIF)</a>, <a href="https://inatba.org/">International Association for Trusted Blockchain Applications (INATBA)</a>, and <a href="https://www.goodhealthpass.org/">Good Health Pass</a>, to name a few. We’re excited to announce the appointment of our very own Governance Lead at cheqd, <a href="https://www.linkedin.com/in/alex-tweeddale/?originalSubdomain=uk">Alex Tweeddale</a>, who will be playing a key role in the <a href="https://wiki.trustoverip.org/display/HOME/Utility+Foundry+Working+Group">ToIP Utility Foundry Working Group</a>.</p><h3>Web 3.0 Exploratory</h3><p>As the year progresses, we will keep an eye out to explore emerging Web 3.0 use cases such as new developments in decentralised exchanges (DEX) ecosystems (especially when they integrate with Cosmos DEXs); decentralised autonomous organisations (DAOs); identity for non-fungible tokens (NFTs), and in general, DeFi applications. If you see an issue you think we should be solving, let us know as there is so much out there and we don’t want to miss other compelling uses of our technology!</p><p>We have a few <em>really</em> cool ideas in this category that combine product features described above in new and interesting ways that we’re cooking up inside the product &amp; engineering team. I can’t go into too much detail and spoil the surprise there, but watch this space. 😉</p><h3>Tell us what you think!</h3><p>We would love your feedback on our product vision for 2022. We welcome engagement and feedback across a range of different forums, such as our <a href="http://cheqd.link/join-cheqd-slack">Community Slack</a> and <a href="https://github.com/cheqd/cheqd-governance/discussions">Governance Framework discussion board</a> (best for extended, in-depth discussions), or right here on <a href="https://blog.cheqd.io/">Medium</a>.</p><p>Within the next few weeks, our team will launch a product roadmap survey that allows everyone to provide feedback on what matters to you and where we should be focussing. In addition to the forums listed above, if you’re interested in taking part in this please ensure you have <a href="https://share.hsforms.com/1CYZbxLdrQx2xMhXlSIR96Ac0rlz">signed up for our newsletter</a> or are in our <a href="https://t.me/cheqd">Telegram group</a>. Stay tuned for more details!</p><p><em>We, at cheqd, help companies </em><a href="https://www.cheqd.io/solution"><em>leverage SSI</em></a><em>. cheqd’s network is built on a blockchain with a dedicated token for payment, which enables new business models for verifiers, holders and issuers. In these business models, verifiable credentials are exchanged in a trusted, reusable, safer, and cheaper way — alongside a customisable fee. Find out more </em><a href="https://www.cheqd.io/solution"><em>about cheqd’s solutions for self-sovereign identity (SSI)</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a92e8e4d296" width="1" height="1" alt=""><hr><p><a href="https://blog.cheqd.io/cheqds-product-vision-for-2022-6a92e8e4d296">cheqd’s product vision for 2022</a> was originally published in <a href="https://blog.cheqd.io/">cheqd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The new version of cheqd testnet is out — we’re gearing up for the mainnet launch ]]></title>
            <link>https://blog.cheqd.io/the-new-version-of-cheqd-testnet-is-out-were-gearing-up-for-the-mainnet-launch-1d34109e5b06?source=rss-c5166068a656------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d34109e5b06</guid>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[network]]></category>
            <category><![CDATA[testnet]]></category>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Ankur Banerjee]]></dc:creator>
            <pubDate>Tue, 12 Oct 2021 13:05:20 GMT</pubDate>
            <atom:updated>2021-10-12T14:56:39.275Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>The new version of cheqd testnet is out — we’re gearing up for the mainnet launch 🎉🥳</h3><p><a href="https://www.cheqd.io/"><strong><em>cheqd</em></strong></a><em> has launched v2 of its testnet for a token-incentivised SSI network built on the </em><a href="https://cosmos.network/"><em>Cosmos blockchain framework</em></a><em>. This new testnet follows on from our open-source announcement and incorporates </em><a href="https://blog.cheqd.io/cheqds-tokenomics-for-ssi-explained-f13f680cf00d"><em>tokenomics for mainnet</em></a><em> as well as the </em><a href="https://docs.cheqd.io/governance/"><em>cheqd Governance Framework</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ERVxbuq8SDK8NmMRq_2YQ.png" /></figure><p>Over the past week, we have been testing out <a href="https://github.com/cheqd/cheqd-node/releases">a new version of the <strong>cheqd-node</strong> software</a>. Transparently, we wanted to message and release this last week but held off to investigate why some node operators were reporting errors during the installation process.</p><p>This turns out to have been an issue due to a few outdated links in the documentation, which have all been comprehensively updated and cross-checked.</p><p>The most important thing about the new release is that it’s a <strong>breaking change</strong>: the <a href="https://blog.cheqd.io/announcing-cheqds-testnet-for-a-new-incentivised-decentralised-identity-4f625ea77076"><strong>existing testnet (“v1”)</strong></a><strong> will be deprecated</strong>. In its place, <strong>we’ve set up a new testnet network (“v2”) which is officially the new cheqd testnet going forward.</strong></p><p>Since we <a href="https://blog.cheqd.io/cheqds-testnet-is-public-and-we-ve-open-sourced-our-code-4e73e11f1958">open-sourced our code</a> in August 2021, we’ve had partners from the self-sovereign identity space as well as community members come onboard our initial network. We’d love to explain what’s happening next in our product roadmap and what brought about this breaking change.</p><h3>What are the major changes in cheqd testnet v2?</h3><p>When we <a href="https://blog.cheqd.io/announcing-cheqds-testnet-for-a-new-incentivised-decentralised-identity-4f625ea77076">initially launched cheqd’s testnet v1 in July 2021</a>, we were still in the process of finalising the tokenomics that would be deployed on the network. This meant that our cheqd node software used the default parameters from a Cosmos SDK network along with identity transactions implemented on the Hyperledger Indy transaction model.</p><p>We have since then <a href="https://blog.cheqd.io/cheqds-tokenomics-for-ssi-explained-f13f680cf00d"><strong>published our tokenomics model for the cheqd SSI network</strong></a> and a <a href="https://blog.cheqd.io/entropy-in-decentralised-governance-part-one-b6dc2dab0085">series</a> of <a href="https://blog.cheqd.io/entropy-in-decentralised-governance-part-two-eb4ac7215f85">blog</a> <a href="https://blog.cheqd.io/entropy-in-decentralised-governance-part-three-4d86b158b9b9">posts</a> walking through the <a href="https://docs.cheqd.io/governance/">cheqd Governance Framework</a>.</p><p>Our <a href="https://blog.cheqd.io/cheqds-tokenomics-for-ssi-explained-f13f680cf00d">tokenomics blog post is the best starting point to understand those changes</a> but to summarise on the impact for node operators (on cheqd mainnet):</p><ol><li>We will have an overall supply of <strong>1 billion $CHEQ tokens</strong>. Our original testnet had this as a fixed amount with no inflation. The consequence of this is that node operators would have received rewards <em>only</em> from transaction fees on the network, and there would have been no block rewards consistently for new block creation. Based on conversation and feedback from the community, we have now changed this to incorporate <strong>a level of inflation (1–4%)</strong> using Cosmos’s built-in mechanism, which dynamically sets the inflation rate within a range based on how many tokens are bonded via staking.</li><li>The goal for the <strong>percentage of bonded tokens is currently set to 60% of the overall supply</strong>. This was benchmarked against a number of projects, and we feel this strikes a balance between securing the network and paying for identity transactions.</li><li>We’ve also set parameters for the governance module based on the cheqd governance framework.</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FKYs5QjRbDBs&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DKYs5QjRbDBs&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FKYs5QjRbDBs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c514ad79f9bef291b792f5f92353f588/href">https://medium.com/media/c514ad79f9bef291b792f5f92353f588/href</a></iframe><h3>How do I join cheqd testnet v2?</h3><p>We have updated all of the documentation related to node setup and management, so if you want to set up a node on the v0.2.3 release, <a href="https://github.com/cheqd/cheqd-node">check out the Github repo for cheqd-node</a>.</p><p><strong>If you are an existing node operator:</strong> we recommend <strong>using a new virtual machine/host</strong> (ideally). This will ensure you don’t run into any issues due to old configuration files. If you can’t spin up a new virtual machine, you can uninstall the old version of the node using:</p><pre>apt remove cheqd-node</pre><p>Please also make sure that you’ve removed old app directories and configuration files. More details are available on <a href="https://github.com/cheqd/cheqd-node/blob/main/docs/setup-and-configure/debian/readme.md#uninstalling-the-debian-package">our Debian package overview</a>.</p><h4>Getting started as a node operator on cheqd testnet v2</h4><ol><li><a href="https://github.com/cheqd/cheqd-node/blob/main/docs/setup-and-configure/readme.md">Install the </a><a href="https://github.com/cheqd/cheqd-node/blob/main/docs/setup-and-configure/readme.md">cheqd-node software</a> on a hosting platform of your choice.</li><li>When you have a node successfully installed, please fill out our <a href="http://cheqd.link/join-testnet-form"><strong>node operator onboarding form</strong></a> so that you can acquire CHEQ testnet tokens required for staking on the network.</li><li>Once you have received your tokens, <a href="https://github.com/cheqd/cheqd-node/blob/main/docs/setup-and-configure/configure-new-validator.md">promote your node to a validator</a>.</li><li>If successfully configured, your node would become the latest validator on the cheqd Testnet! Say hi to the other node operators on the <a href="https://cheqd-community.slack.com/archives/C029NSCSA75">#testnet-node-operators</a> channel.</li></ol><p>Any time you have questions or need support, join our <a href="http://cheqd.link/join-cheqd-slack"><strong>cheqd Community Slack</strong></a> and <a href="https://cheqd-community.slack.com/archives/C02AQ9UK4HY">ask for help</a>.</p><h3>What’s new in the cheqd-node release v0.2.3?</h3><p><a href="https://github.com/cheqd/cheqd-node/releases/tag/v0.2.3">cheqd-node v0.2.3</a> is our last major milestone release planned for cheqd-node before we launch the cheqd mainnet. It incorporates the following breaking/major changes:</p><h4>Account names now start with the “<strong>cheqd</strong>” prefix rather than “<strong>cosmos</strong>”</h4><p><strong>Impact</strong>: The new account name format is one of the reasons why this node release version is incompatible with cheqd testnet v1.</p><h4>The lowest denomination of $CHEQ tokens</h4><p>Another major change is that the lowest denomination of a token has been changed to <strong>1 nano $CHEQ (“ncheq”)</strong>, which is 10^-9 CHEQ. The previous testnet had 1 CHEQ as the smallest denomination, which would not have allowed for very precise pricing for transactions. We always wanted to make this change, as we foresee this being a potential issue in the future. This is similar to how Cosmos ATOM uses 10^-6 ATOM as the smallest unit.</p><p><strong>Impact</strong>: All transactions (transfers, balances, etc.) are now calculated in ncheq. Please make sure you double-check your calculations for transactions so that the transaction amount in ncheq works out to the right value in whole CHEQ terms.</p><p>For more details, please see <a href="https://docs.cheqd.io/node/architecture/adr-list/adr-004-token-fractions">ADR 004: Token fractions</a>.</p><h4>Genesis parameters and Cosmos SDK update</h4><p><strong>All genesis parameters have been updated</strong> to reflect what they would be on the mainnet. (More details are outlined in <a href="https://docs.cheqd.io/node/architecture/adr-list/adr-005-genesis-parameters">ADR 005: Genesis parameters</a>.)</p><p>We also upgraded from <a href="https://github.com/cosmos/cosmos-sdk/releases/tag/v0.44.0">Cosmos SDK v0.42 to v0.44 since it’s a security release that contains breaking changes</a> in the underlying SDK. Cosmos v0.43 was discontinued and superseded. We wanted to ensure that this important security update was accounted for before the mainnet launch.</p><h4>Building a cheqd DID method compliant with W3C specifications</h4><p><strong>We’ve removed the NYM transaction type from this release</strong>. We thought long and hard about whether we wanted to keep the same transaction types as Hyperledger Indy, especially since Hyperledger Indy was designed before the W3C specifications in SSI were finalised. Indy, therefore, makes certain assumptions and choices that result in it being incompatible with the <a href="https://w3c.github.io/did-core/">W3C DID Core specifications</a>.</p><p><strong>Impact:</strong> We have work-in-progress to <strong>make the cheqd DID method compliant with W3C specifications</strong>. We believe this is the right choice to make to limit future tech debt.</p><p>Our communication layer is still planned to work with Hyperledger Aries. Integrating a W3C specification compliant DID method would make it easier in the future to extend Aries to support other W3C-compliant DID methods and Verifiable Data Registries, which we see as an exciting leap forward for the SSI community.</p><p>For SDKs/client libraries, we still plan to have at least one implementation of a client library that supports Indycreds and cheqd DID method credentials.</p><h3>What’s next for cheqd’s product roadmap?</h3><p>We hope the summary above explains the changes that we have made and the rationale for them. As always, we welcome feedback on our product releases and keen to take any feedback onboard.</p><p>October / November 2021 is an exciting time for the cheqd team, as we have major milestones planned. Our product and engineering team strongly believes in releasing early and often to ship iterations of the product regularly and provide updates.</p><h4>Launch the cheqd mainnet</h4><p>Based on current projections, we aim to launch v1 of the cheqd mainnet by the end of October 2021 or latest, by November 2021. Our main objective is to implement relatively stable and finalised ledger APIs/functions, giving app developers confidence to build against the network.</p><p>It will have minimum viable functionality for a stable, production-grade network that offers a new range of functionality for SSI application vendors, digital identity companies, enterprises that need to issue/receive digital credentials, and node operators from a DeFi background.</p><p>This would include:</p><ol><li>Finalised tokenomics implemented (this is already present on cheqd testnet v2)</li><li>A W3C compliant DID method</li><li>Final stability changes and bugfixes</li></ol><h4>Open-source our infrastructure tooling repository</h4><p>Many of our node operators run standalone virtual machines, but we have also received interest in more sophisticated setups. Our engineering team has been working on DevOps tooling using Terraform for deploying multi-node, multi-region deployments on <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/AWS_Fargate.html">AWS using Elastic Container Service (ECS) on Fargate</a>.</p><p>We want to open-source and provide this to the community as another available node operator who might want to run more than one node or to have a more robust infrastructure setup. While we currently only work with AWS, we hope to support other cloud platforms in the future and welcome contributions from the open source-community from anyone who wants to contribute automation assets.</p><h4>Public product roadmap website</h4><p>We recognise that our community is excited to find out more about what we do next, discuss and provide feedback on our product roadmap in more detail.</p><p>As a sneak peek, these would include:</p><ol><li>More robust support for the W3C-compliant cheqd DID method in client libraries</li><li>Support for revocation registries and BBS+ signatures</li><li>Holder-pays-issuer, verifier-pays-issuers, and other charging mechanisms</li><li>Block explorer and/or monitoring tools for node operators and general public</li></ol><h3>Join us on testnet and say hi 👋</h3><p>We highly appreciate all the interest from the community in participating in the cheqd testnet and building a vision together for an <strong>authentic data network</strong>. To all of our existing testnet node operators, thank you. ❤️</p><p>If you would like to learn about our partner programme for self-sovereign identity vendors, please reach out to us at <a href="/service/mailto:partners@cheqd.io">partners@cheqd.io</a>.</p><p>Please feel free to ask us any questions on the <a href="https://join.slack.com/t/cheqd-community/shared_invite/zt-toqyo7b7-2g9qDRjx3otd6529dTqeIA"><strong>cheqd Community Slack</strong></a>. We also hugely believe in the value of the community supporting and engaging with each other, so whenever you see someone in need of support, feel free to jump in.</p><p>Onwards and upwards,<br><strong>The cheqd product team 🚀</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d34109e5b06" width="1" height="1" alt=""><hr><p><a href="https://blog.cheqd.io/the-new-version-of-cheqd-testnet-is-out-were-gearing-up-for-the-mainnet-launch-1d34109e5b06">The new version of cheqd testnet is out — we’re gearing up for the mainnet launch 🎉🥳</a> was originally published in <a href="https://blog.cheqd.io/">cheqd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[cheqd’s testnet is public — and we’ve open sourced our code]]></title>
            <link>https://blog.cheqd.io/cheqds-testnet-is-public-and-we-ve-open-sourced-our-code-4e73e11f1958?source=rss-c5166068a656------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e73e11f1958</guid>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[cosmos-network]]></category>
            <category><![CDATA[self-sovereign-identity]]></category>
            <category><![CDATA[digital-identity]]></category>
            <dc:creator><![CDATA[Ankur Banerjee]]></dc:creator>
            <pubDate>Thu, 26 Aug 2021 15:24:53 GMT</pubDate>
            <atom:updated>2021-08-30T11:13:57.651Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3><strong>cheqd’s testnet is public — and we’ve open sourced our code</strong></h3><p><a href="https://www.cheqd.io/"><strong><em>cheqd</em></strong></a><em> has </em><a href="https://github.com/cheqd"><em>open-sourced its code</em></a><em> for a token-incentivised SSI network built on the </em><a href="https://cosmos.network/"><em>Cosmos blockchain framework</em></a><em>. We’re expanding beyond private beta to a public testnet, with plans for publishing further details about tokenomics and governance in future releases.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sVJaJc6kQunfNWsmkMRsHw.png" /></figure><p>We’re excited at <strong>cheqd</strong> to announce that we’re <a href="https://github.com/cheqd">open-sourcing the early version of the code</a> we’ve been building for the past few months for a purpose-built self-sovereign identity (SSI) using the Cosmos blockchain framework with the <strong>$CHEQ token.</strong> As we progress on our product roadmap, this marks another major milestone for the <strong>cheqd</strong> product &amp; engineering team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T-FigzmfPxGVnBdujJPWGw.png" /><figcaption>cheqd private beta testnet partners</figcaption></figure><p>Our persistent <a href="https://blog.cheqd.io/announcing-cheqds-testnet-for-a-new-incentivised-decentralised-identity-4f625ea77076">cheqd testnet has been live in private beta for just about a month</a> with our initial launch partners: <a href="https://www.evernym.com/">Evernym</a>, <a href="https://outlierventures.io/">Outlier Ventures</a>, and <a href="https://www.didx.co.za/">DIDx</a>.</p><h3>About cheqd’s open source repositories</h3><p>With this step, we’re expanding the ability for <strong>anyone</strong> with the capability to run a node to be able to participate in the public beta of the cheqd testnet. Our code is being released on <a href="https://github.com/cheqd">cheqd’s GitHub organisation page</a> under the <a href="https://www.apache.org/licenses/LICENSE-2.0">Apache 2.0 License</a>, which will allow open source contributors to use, modify, remix and deploy our software and join our testnet (at present) and the cheqd mainnet (when launched).</p><p>The repositories that we’re releasing to the public are:</p><ol><li><a href="https://github.com/cheqd/cheqd-node"><strong>cheqd-node</strong></a>: The server/node portion of purpose-built network for decentralised identity. This is where the code for our public-permissionless SSI network analogous to <a href="https://github.com/hyperledger/indy-node">Hyperledger Indy node</a> will live. In one of our previous blog posts, we explained <a href="https://blog.cheqd.io/why-cheqd-has-joined-the-cosmos-4db8845722c5">why we built our stack on Cosmos instead of Hyperledger Indy</a> or other frameworks.</li><li><a href="https://github.com/cheqd/cheqd-sdk"><strong>cheqd-sdk</strong></a>: A Rust client library for ledger-independent self-sovereign identity (SSI) operations on Verifiable Data Registries (VDRs). Integrates with <a href="https://github.com/cheqd/cheqd-node">cheqd-node</a> server-side. This repository is built in collaboration with our partners at Evernym and is currently a mirror of <a href="https://gitlab.com/evernym/verity/vdr-tools">Evernym VDR Tools</a>. This repository is analogous to the <a href="https://github.com/hyperledger/indy-sdk">Hyperledger Indy SDK</a> that current SSI application vendors embed in their products.</li></ol><h3>What has changed since the private beta?</h3><p>Our testnet launch in July 2021 gave us valuable feedback from our early adopters in being able to refine where our engineering teams should focus on. While we initially planned to release a Cosmos-based Decentralized Identifiers (DIDs) specification for August, the feedback we received was to focus on making the installation and upgrade processes easier.</p><p>We’ve therefore worked towards making installation packages and releases (along with documentation) available in the following formats:</p><ol><li><a href="https://github.com/cheqd/cheqd-node/releases"><strong>Debian (.deb) package installer</strong></a>, targeting <a href="http://www.releases.ubuntu.com/20.04/">Ubuntu 20.04 LTS</a> (the Linux distribution most Hyperledger Indy node operators should be familiar with)</li><li><a href="https://github.com/orgs/cheqd/packages?repo_name=cheqd-node"><strong>Docker containers</strong></a>, as a more platform-independent way of deploying the cheqd blockchain node software</li><li><a href="https://github.com/cheqd/cheqd-node/releases"><strong>Linux binary packages</strong></a>, as a baseline for other Linux distributions</li><li>Instructions on how to build any of the above from source.</li></ol><p>We’re also exploring support for other platforms in the future, for example, a <a href="https://snapcraft.io/">Snap package</a> for other Linux distributions.</p><p>One challenge with having a private beta was the logistical challenge of allowing prospective node operators to freely browse and decide to install the code at their own pace, rather than individually trying to coordinate access to the repositories.</p><h3>What functionality is currently available on cheqd testnet?</h3><p>Our existing node operators (and prospective ones) asked us, <em>“Great, I have a node working. What can I do next?!”</em></p><p>We aimed, therefore, to make this milestone one where prospective users could go through an end-to-end journey of setting up a node and being able to read/write DIDs on ledger.</p><p>While it’s early days, the <a href="https://github.com/cheqd/cheqd-node#:~:text=cheqd%20Cosmo%20CLI%20reference%20guide">cheqd Cosmos Command Line Interface (CLI) user guide</a> we’ve started building defines what can be done on our testnet. We started this by asking the following:</p><h4>Basic Cosmos node setup and the “cheq” token</h4><ul><li>Creating, managing, and configuring accounts and keys on a cheqd Cosmos node. These are set up steps that new node operators need to do to get started.</li><li>Our public-permissionless model is based on <a href="https://en.wikipedia.org/wiki/Proof_of_stake">proof-of-stake</a>, so we walk through how to stake and participate in network consensus.</li><li>Basic token functionality for <a href="https://blog.cheqd.io/announcing-cheqds-testnet-for-a-new-incentivised-decentralised-identity-4f625ea77076">holding and transferring our tokens, called “<strong>cheq</strong>”</a>, to other accounts on the network.</li></ul><h4>Basic decentralised identity primitives</h4><ul><li>Writing Decentralized Identifiers (DIDs) entries on a ledger paying for DID writes on the cheqd testnet using testnet tokens. As our CEO, Fraser Edwards, and Javed Khattak (our CFO) described in this blog post <a href="https://blog.cheqd.io/why-self-sovereign-identity-needs-a-token-46e43dada01d">why self-sovereign identity needs a token</a>; we want to <a href="https://blog.cheqd.io/the-business-models-of-identity-bb3336773727">enable new business models for digital identity</a>.</li><li><a href="https://hyperledger-indy.readthedocs.io/projects/node/en/latest/transactions.html#nym">NYM is the term used by Hyperledger Indy</a> for Decentralized Identifiers (DIDs) that are created on ledger. For the sake of explaining with similar concepts as current Hyperledger Indy implementations, on our testnet transactions to add a DID to the ledger are called NYM transactions. Future releases of our software are likely to replace the NYM terminology with DID for better understanding.</li></ul><h3>What’s coming next in cheqd testnet functionality?</h3><p>Our broad goal is to <strong>launch cheqd’s mainnet</strong> with the <strong>$CHEQ token </strong>around <strong>October 2021</strong>. It will have minimum viable functionality for a stable, production-grade network that offers a new range of functionality for SSI application vendors, digital identity companies, enterprises that need to issue/receive digital credentials, and node operators from a DeFi background.</p><p>The two major aims we’ve set ourselves for the next milestone, by the end of September 2021 is to make available:</p><ul><li><strong>Define how tokenomics will work on our network</strong>: We aim to describe how our cheqd Cosmos network will behave and what the initial economic parameters will be. (Stay tuned as we announce a live tokenomics session soon!)</li><li><strong>Our governance framework for a public-permissionless SSI network</strong>: Alex Tweeddale, our Governance &amp; Compliance Lead, <a href="https://blog.cheqd.io/entropy-in-decentralised-governance-part-one-b6dc2dab0085">introduced the concept of “entropy” in the governance model</a> we aim to construct. This will help to get closer to <a href="https://blog.cheqd.io/entropy-in-decentralised-governance-part-two-eb4ac7215f85">decentralised governance that gives the community far greater influence</a> on how the cheqd network will run than current permissioned SSI networks allow.</li><li><strong>Explanations of architectural decisions</strong> that will guide application developers on how to integrate and build against our software.</li></ul><p>We are also exploring mechanisms to showcase our product roadmap and guidance on how community members can influence the aspects above in a simple, easy to understand and accessible fashion.</p><h3>How to get involved in the cheqd testnet</h3><p>If you’re interested in running a node yourself or otherwise getting involved in the code/governance of cheqd, here’s where you can get started:</p><ul><li>“cheq” out <a href="https://github.com/cheqd/cheqd-node#quick-start-for-joining-cheqd-testnet">our quick start guide on setting up a node</a> on cheqd testnet or reach out to us on <a href="/service/mailto:partnerships@cheqd.io">partnerships@cheqd.io</a></li><li>Understand <a href="https://github.com/cheqd/.github/blob/main/CODE_OF_CONDUCT.md">cheqd’s Community Code of Conduct</a> and <a href="https://github.com/cheqd/cheqd-node#building-from-source">build/contribute to our source code</a></li><li>Join the <a href="http://cheqd.link/join-cheqd-slack">cheqd Community Slack</a>, our chat channel for the open-source community, software developers, and node operators. Reach out to us here for discussions, help, and feedback on the project.</li></ul><h3>About cheqd</h3><p>We’re building a secure network that enables individuals to take full control of their personal data. Through our network, anyone can verify identities quickly and securely.</p><p>We help companies monetise self-sovereign identity to stay viable, profitable and more successful than before. Issuers of data benefit from a recurring revenue stream whenever that data is used in the future without needing to process it constantly. Recipients of data can lower their costs since any data they receive is digital, trustable and re-usable, reducing the processing overhead.</p><p>Ultimately, we’re making it easier for individuals and organisations to trust each other.</p><p>For partnership and node operator queries for <strong>cheqd</strong>, please get in touch at <a href="/service/mailto:partners@cheqd.io">partners@cheqd.io</a>.</p><h4>Follow the cheqd community</h4><p><em>We would love to know your thoughts as always either as comments on the article or via any of our other channels below!</em></p><p><em>Make sure to join our rapidly growing </em><a href="https://t.me/cheqd"><em>Telegram community </em></a><em>to stay updated with our most recent news and insights.</em></p><p><em>P.S. We’re also on </em><a href="https://twitter.com/cheqd_io"><em>Twitter</em></a><em> and </em><a href="https://www.linkedin.com/company/cheqd-identity/"><em>LinkedIn</em></a><em>, make sure to cheq in!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e73e11f1958" width="1" height="1" alt=""><hr><p><a href="https://blog.cheqd.io/cheqds-testnet-is-public-and-we-ve-open-sourced-our-code-4e73e11f1958">cheqd’s testnet is public — and we’ve open sourced our code</a> was originally published in <a href="https://blog.cheqd.io/">cheqd</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>