<?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 Rohit Nayak on Medium]]></title>
        <description><![CDATA[Stories by Rohit Nayak on Medium]]></description>
        <link>https://medium.com/@anotherrohit?source=rss-235d0349831a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ZA1VXUGi6pXRw5pX.</url>
            <title>Stories by Rohit Nayak on Medium</title>
            <link>https://medium.com/@anotherrohit?source=rss-235d0349831a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:55:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anotherrohit/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[What is Self Sovereign Identity?]]></title>
            <link>https://medium.com/@anotherrohit/what-is-self-sovereign-identity-55b639c3fb90?source=rss-235d0349831a------2</link>
            <guid isPermaLink="false">https://medium.com/p/55b639c3fb90</guid>
            <category><![CDATA[ssi]]></category>
            <dc:creator><![CDATA[Rohit Nayak]]></dc:creator>
            <pubDate>Fri, 17 Feb 2023 19:46:50 GMT</pubDate>
            <atom:updated>2023-02-17T19:52:29.623Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/113/1*noPsdv7_1gCfb0od4qoz9g.png" /></figure><p><em>This blog has been a research and discovery project and an inspiration from Christopher Allan’s work on Self Sovereign Identity, I have added mere points of view based on some observations in the identity industry. I have made sure I referenced every individual responsible for their research and most importantly referenced Chris’s blog. There are some thoughts which are made in this only as a hypothesis, which has been interesting topics to research on, and not necessarily opinions of any employer.</em></p><p>Identity is a uniquely individualistic idea, which begins from a state of consciousness, and something the world recognizes and relates to. However, in the modern world these ideas are conflated to mere pieces of papers like government issued ids, documents, and id badges issued by trusted organizations, which can directly mean that one’s identity is what an entity defines, validates, and designates to an individual. However, as the world becomes increasingly digital, a new opportunity arises to redefine what identity means and how we can have me as an individual state who I am, because an entity says so, and they have proof that I am who I am, and therefore, you can trust me. This concept is termed as Self Sovereign Identity. As revolutionary as it sounds, today’s world requires a certain level of attestation or proof by third parties who represent your identity, and SSI allows you to do this. With SSI you can safely claim attributes about yourself, along with attributes that are verified and issued to you by a trusted source all encompassing into a single concept of a digital identity, and present to any requesting service to claim you are who you claim to be.</p><p><strong>History of Identity</strong></p><p>Before stating a paradigm shift in the concept of our readers minds, it is important to walk through a journey of the evolution of identity. The models for online identity have advanced through 4 broad stages:</p><ol><li>Centralized Identity</li><li>Federated identity</li><li>User-Centric identity</li><li>Self Sovereign Identity</li></ol><p><strong>Centralized Identity</strong></p><p>In the internet’s early days, centralized authorities were the issuers of identity. Organizations like IANA(1988) determined the validity of IP addresses and ICANN (1998) arbitrated domain names. By 1995,Certificate Authorities (CAs) helped websites to trust and prove to the web world to state who they said they were. This also created hierarchies, using a concept of a root Certificate Authority, who could anoint other organizations to each oversee their own hierarchy, with a lot of power and authority created for them — another way of centralized but subtly less dictated authority, which gave the concept of trusting the chain of certificate authority to accept the identity of an entity.</p><p>Granting control of digital identity to centralized authorities in the online world is equivalent to allowing state authorities to dictate your real identity in the physical world with a proof of attestation, which is giving more power to the centralized identity not the users. The problem further exacerbated as identities exploded with multiple web sites, allowing users to create different accounts and identities, and in turn allowing them to have no control of any of these identities. In fact, with this proliferation we ran into multiple problems of maintaining profiles, usernames, passwords, SMS tokens, Authenticators and other countless ways to manage our identities online, only to be susceptible to cyber threats and honeypots for malicious actors.</p><p>Thanks to some research done by Christopher Allan¹ and countless research papers, which I have quoted as references in this article, there was hard work put in by the computer science community to change this paradigm. The Web of Trust² established trust for a digital identity by allowing peers to act as introducers and validators of public keys² in the PGP model. Anyone could be a validator in the PGP model, which was a decentralized trust management but focused on email addresses and still dependent on centralized hierarchies, which never caught on. Other work in establishing identity without Certification Authority (1996), a paper by Carl Ellison that examined how a digital identity was created, considered both Certificate Authorities and peer-to-peer systems like PGP to define digital identity, and eventually settled on a method to allow online identity by exchanging shared secrets over a secure channel, which allowed users to control their own identity without depending on a managing authority³. He later was also responsible for the SPKI/SDSI project (1999)⁴⁵ with a simpler public infrastructure for identity certificates that could replace the complicated X.509 system. This was the birth of a more revolutionary reconception of identity.</p><p><strong>Federated Identity (administrative control by multiple, federated authorities).</strong></p><p>The next major advancement for digital identity occurred with the introduction of federation. Microsoft’s Passport (1999) allowed users to utilize the same identity on multiple sites and in exchange for making Microsoft the central source of identity. Naturally. The industry took towards looking for an alternative which came in the form of Sun Microsystems organized Liberty Alliance (2001), which resisted the centralized authority by creating a free federation in turn turning the market into a perfectly competitive industry which all identity solutions are selling in the name of a SSO tax. Although this solved the problem of centralization marginally, users could now be redirected to other sites and hence transfer identity information to these few players responsible for creating and storing their profiles on their servers. Again, not really solving the problem quite.</p><p><strong>User-Centric Identity (individual or administrative control across multiple authorities without requiring federation)</strong></p><p>The Internet Identity Workshop working group which was formed as a consortium to advance the idea of decentralized identity tackled the server-centric model of centralized authorities by transforming this to a user-centric identity model. The premise being the user is the center of the identity identification, authentication and authorization process, with consent and hence providing a better user experience⁶⁷. Unfortunately, this led to a need for the user to have more control over his identity and for trust to be decentralized⁸. IIW was responsible for some architectural leadership around authorization protocols like OpenID (2005), OpneID 2.0 (2006), OpenID Connect (2014), and FIDO (2013). All pinning on user consent and interoperability.</p><p>In essence, OpenID allows users to theoretically register his own OpenID which they can use autonomously, so a user can use it from one public site to another. As non capitalistic it sounds, there were major challenges in interoperability in this concept which caused it to never pick up.</p><p>Facebook Connect (2008) appeared a few years after OpenID leveraging lessons from the first time around and of course with a better user experience, which many of us remember from our age⁹. This was a further drift away from decentralizing identities, only to provide a facebook way of login to social websites. Often making enterprise customers even question if there is a place for social login in this business critical industry. Kudos to the vision from the founder of Facebook to imagine a world being taken over by social media, where every user will rely on their social capital gained on the web, through friends, acquaintances and even enemies on social networks. This coupled with security vulnerabilities that the OpenID connect Foundation resolved to address with symmetric keys and the introduction of JSON Web Tokens (JWTs). Today several security vendors provide the best of breed identity Secure token service all leveraging JWTs with cryptographic signatures that if done correctly can provide the security needed, even if it requires a genius programmer to know the difference between JWT.decode and JWT.verify.</p><p><strong>Self Sovereign Identity (individual control across any number of authorities)</strong></p><p>User-centric designs turned centralized identities into interoperable federated identities with centralized control, while also respecting some level of user consent about how to share an identity and with whom. Self-Sovereign Identity was first referenced by developer Devon Loffreto¹¹, where he quoted individuals have an established right to an identity. Following this closely, in March 2012, Patrick Deegan began work on Open Mustard Seed, an open source framework that gives users control over their digital identity and their data in decentralized systems¹². Loffreto has further blogged how the term has evolved¹². As a developer, one way to achieve self sovereign identity is by using a mathematical policy, where cryptography is used to protect a user’s autonomy and control. In the last year, self-sovereign identity has entered in the sphere of international policy¹⁷ with mission driven product companies trying to create identities for refugees and underprivileged societies who do not have any digital footprint, these are interesting concepts only to be limited by the lack of state-issued credentials. The state of self-sovereignty is more. Furthermore, thought leadership around Self-Sovereign identities has been put across by W3C Verifiable claims task force²², publishing the ten rules of SSI including existence, control, access, transparency, persistence, portability, interoperability, consent, minimization and protection.</p><p><strong>Hypothesis for a real world</strong></p><p>I hypothesize a way where products can not only enable users to create identities but also prove their identity by supplementing these with proof that they are who they are, so entities they represent can step in and create an digital format of this identity which resolves uniquely to their relationship with that entity but in the business context of transaction only. Solving for a universal identity proofing with Machine Learning (ML) is surely a way to get that, but how does one place such highly assured ML vetted identity proofing methods to be placed in the Enterprise authentication space where web protocols like OpenID require users consent and an issuer or an identity provider to issue them the identity which any verifier can trust because a Enterprise company said so. I believe this starts at the grass root level where day to day users who need to prove who they are at all times, at various stages of business journeys, may it be waking up and accessing their digital device, or walking up to the place of work to use a employer stated piece of identity to prove they work there, to using a piece of identity issued by a Single Sign on Identity provider to let them login. Imagine how this will work for the thousands of foot soldiers who deliver packages, walk through different campuses representing their institute, and then having to show something that looks like a paper to show they work there in spite of these state of the art authentication platforms existing in every users desktop or mobile phone, just in a building in which they are trying to get in to. Can a ubiquitous way of authentication that ties to these foot soldiers exist which only lasts till the organization they issued this identity wants it to last? We would like to see security vendors solve this problem of moving identity, changing contexts and needs throughout their day, not by allowing them to rely on antiquated ways to verify users by submitting documents at a gate, but in a more sophisticated and industry specific and context specific manner. Self Sovereign Identity was coined to put power back to the people, but only if it works for the people who actually interact with digital systems, enterprises and companies who require assurances which a human can marginally provide. The solutions lie in the institutions that issue these digital identities and a way to make them portable, manageable and trusted in every context of life.</p><p><strong>References</strong></p><p>1 Christopher Allen. 2015. “The Four Kinds of Privacy”. Life With Alacrity blog. /2015/04/the-four-kinds-of-privacy.html↩Jon Callas, Phil Zimmerman. 2015. “The PGP Paradigm”. RebootingWebOfTrust Design Workshop.</p><p>2. Appelcline, Crocker, Farmer, Newton. 2015. “Rebranding the Web of Trust”</p><p>Jon Callas, Phil Zimmerman. 2015. “The PGP Paradigm”. #RebootingWebOfTrust Design Workshop. https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/topics-and-advance-readings/PGP-Paradigm.pdf.↩</p><p>3 Appelcline, Crocker, Farmer, Newton. 2015. “Rebranding the Web of Trust”. #RebootingWebOfTrust Design Workshop. https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/final-documents/rebranding-web-of-trust.pdf↩</p><p>4 Ellison, Carl. 1996. “Establishing Identity without Certification Authorities”. 6th USENIX Security Symposium. http://irl.cs.ucla.edu/~yingdi/pub/papers/Ellison-OldFriend-USENIX-Security-1996.pdf.↩</p><p>5 Ellison, C., et. al. 1999. “RFC 2693: SPKI Certificate Theory”. IETF. <a href="https://tools.ietf.org/html/rfc269%E2%86%A9">https://tools.ietf.org/html/rfc269↩</a></p><p>6 Jordon, Ken, Jan Hauser, and Steven Foster. 2003. “The Augmented Social Network: Building Identity and Trust into the Next-Generation Internet”. Networking: A Sustainable Future. http://asn.planetwork.net/asn-archive/AugmentedSocialNetwork.pdf↩</p><p>7 Jøsang, Audun and Simon Pope. 2005. “User Centric Identity Management”. AusCERT Conference 2005. http://folk.uio.no/josang/papers/JP2005-AusCERT.pdf↩</p><p>8 Verifiable Claims Task Force. 2006. “[Editor Draft] Verifiable Claims Working Group Frequently Asked Questions”. W3C Technology and Society Domain. http://w3c.github.io/webpayments-ig/VCTF/charter/faq.htm↩</p><p>9 Gilbertson, Scott. 2011. “OpenID: The Web’s Most Successful Failure”. Webmonkey. http://www.webmonkey.com/2011/01/openid-the-webs-most-successful-failure↩</p><p>10 Hassine, Wafa Ben and Eva Galperine. “Changes to Facebook’s ‘Real Name’ Policy Still Don’t Fix the Problem”. EFF. https://www.eff.org/deeplinks/2015/12/changes-facebooks-real-names-policy-still-dont-fix-problem↩</p><p>11 Loffreto, Devon. 2012. “What is ‘Sovereign Source Authority’?” The Moxy Tongue. http://www.moxytongue.com/2012/02/what-is-sovereign-source-authority.html↩</p><p>12 Open Mustard Seed. 2013. “Open Mustard Seed (OMS) Framework). ID3. https://idcubed.org/open-platform/platform/↩</p><p>13 Loffreto, Devon. 2016. “Self-Sovereign Identity”. The Moxy Tongue. http://www.moxytongue.com/2016/02/self-sovereign-identity.html↩</p><p>14 Respect Network. 2016. “The Respect Trust Network v2.1”. oixnet.org. http://oixnet.org/wp-content/uploads/2016/02/respect-trust-framework-v2-1.pdf↩</p><p>15 Graydon, Carter. 2014. “Top Bitcoin Companies Propose the Windhover Principles — A New Digital Framework for Digital Identity, Trust and Open Data”. CCN. https://www.cryptocoinsnews.com/top-bitcoin-companies-propose-windhover-principles-new-digital-framework-digital-identity-trust-open-data/↩</p><p>16 Smith, Samuel M. and Khovratovich, Dmitry. 2016. “Identity System Essentials”. Evernym. http://www.evernym.com/assets/doc/Identity-System-Essentials.pdf↩</p><p>17 Dahan, Mariana and John Edge. 2015. “The World Citizen: Transforming Statelessness into Global Citizenship”. The World Bank. http://blogs.worldbank.org/ic4d/category/tags/self-sovereign-identity-systems↩</p><p>18 Identity Commons. 2007. “Claim”. IDCommons Wiki. http://wiki.idcommons.net/Claim↩</p><p>19 Christopher Allen. 2015. “The Four Kinds of Privacy”. Life With Alacrity blog. /2015/04/the-four-kinds-of-privacy.html↩</p><p>20 Cameron, Kim. 2005. “The Laws of Identity”. https://msdn.microsoft.com/en-us/library/ms996456.aspx↩</p><p>21 Respect Network. 2016. “The Respect Trust Network v2.1”. oixnet.org. http://oixnet.org/wp-content/uploads/2016/02/respect-trust-framework-v2-1.pdf↩</p><p>22 Verifiable Claims Task Force. 2006. “[Editor Draft] Verifiable Claims Working Group Frequently Asked Questions”. W3C Technology and Society Domain. http://w3c.github.io/webpayments-ig/VCTF/charter/faq.html↩</p><p>23 “Definition of Credential”. Dictionary.com. http://www.dictionary.com/browse/credential?s=t↩</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55b639c3fb90" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fabvatar badges — A must have for pre-verifying your contractors.]]></title>
            <link>https://medium.com/@anotherrohit/fabvatar-badges-a-must-have-for-pre-verifying-your-contractors-133088e548d5?source=rss-235d0349831a------2</link>
            <guid isPermaLink="false">https://medium.com/p/133088e548d5</guid>
            <dc:creator><![CDATA[Rohit Nayak]]></dc:creator>
            <pubDate>Wed, 18 Jan 2023 00:16:37 GMT</pubDate>
            <atom:updated>2023-01-18T00:24:56.776Z</atom:updated>
            <content:encoded><![CDATA[<h3>Fabvatar badges — A must have for pre-verifying your contractors.</h3><h3>Use ID Cards That Keep Track Of Licenses, Certifications &amp; More.</h3><p><strong>Keeping track of compliance processes, like which workers or contractors have up to date certifications or certifications for performing the job has never been more critical. Failures in the compliance arena can cause huge legal penalties and fines if something bad happens or there’s an audit.</strong></p><p><strong>If someone asked you to do it right now, would you be able to produce compliance documentation for your contractors? How many steps does it take you, how many organizations did you reach out to, just to confirm where the worker has the right certifications? And how many excel spreadsheets do you have to maintain to store this information for short term workers to find what you need?</strong></p><p><strong>What happens if it turns out a contractor’s licenses or certifications are out of date? What if they got injured at your job-site and you’re just now finding this out? If contractor compliance falls by the wayside then the entire job is in jeopardy. How can you further ensure your contractor or field employee has all the approvals required for the job he is carrying at the desired location, considering they are always on the move?</strong></p><p><strong>Instead of going crazy, let Fabvatar Badge ID keep track of this information automatically. Business owners define requirements, add required certification check approvals from credible institutions and create a badge for these contractors. Then,contractors or badge-holders can carry these digital IDs in their phones to display on demand. Fabvatar Badge provides verified credentials signed and attested by a trusted organization that your business relies on and notifies both the badge-holder and business owner when it’s time to get a new certification or attest to a new policy before it expires or goes out of date.</strong></p><p><strong>With Verified Fabvatar credential Badges managing contractor compliance to required licenses, procedures, and certifications, your team can spend more time getting jobs done quicker and less time worrying. Consequently, Instead of maintaining a cumbersome process using Excel spreadsheets to manage compliance certifications and training renewal dates, and allowing potential clients to call and verify with you, Fabvatar Badge keeps track of this information dynamically. With Fabvatar Badge doing certification management automatically, HR managers can spend less time worrying about compliance and more time helping their workers.</strong></p><p><strong>Fabvatar uses secure, encrypted blockchain issued Decentralized Ids or (DIDs) and Public-Private key infrastructure on the blockchain to lookup and ensure uniqueness, confidentiality, integrity of the identity in question is maintained. While all the private data sits on the users device eliminating the need to collect, store and track different certifications for employees, workers, contractors, and more by using the Fabvatar Badge mobile app. Badge-holders can upload the credentials your organization requires when they apply for their badges, and Fabvatar will track these certifications automatically. When a certification like an OSHA or equipment training is about to go out of date, both the badge-holder and business owner will be notified. If the certification expires, the organization can set the worker’s Fabvatar Badge to automatically deactivate until the credential has been updated and re-certified. By storing and tracking different credentials and certifications, digital ID badges can lower risk and make it easier to focus on operations, not compliance.</strong></p><ul><li>Business owners can create Custom Employee or contractor Badge Onboarding Process To Collect Certifications.</li><li>Employees, Workers, Contractors &amp; Volunteers Create A Fabvatar Badge Account And Request Their Badges.</li><li>Contractors Take Selfie Photos &amp; Upload Required Documentation Or Certifications</li><li>Business owners verify Uploaded Documentation &amp; Approve / Issue ID Badges</li><li>Once Approved, Workers Can Show Their Certifications With Their Digital ID Badges</li><li>If A Certification Is About To Expire, The Worker &amp; Administrators Will Be Alerted</li><li>If A Certification Expires, The Worker’s Fabvatar Badge Can Be set To Automatically Deactivate.</li><li>When The Certification Is Updated And Approved, The Worker’s Virtual Badge Will Reactivate.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=133088e548d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learn how you can leverage the power of Verified Credentials to power your Small Business.]]></title>
            <link>https://medium.com/@anotherrohit/learn-how-you-can-leverage-the-power-of-verified-credentials-to-power-your-small-business-9696762241ba?source=rss-235d0349831a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9696762241ba</guid>
            <category><![CDATA[verified-credential]]></category>
            <dc:creator><![CDATA[Rohit Nayak]]></dc:creator>
            <pubDate>Mon, 12 Sep 2022 22:43:58 GMT</pubDate>
            <atom:updated>2022-09-12T22:43:58.076Z</atom:updated>
            <content:encoded><![CDATA[<p>Verified Credentials (VCs) are a standard to digitally represent information about a person or their relationship to an entity in a portable, immutable and transferrable format.</p><p>Today, traditional credentials may it be an assertion, qualification, affiliation or an attribute are used almost in every context. However, these are only limited and difficult and expensive to verify, but also are valid only as per the paper or knowledge based format they are issued with. Alternatively. Verified Credentials are credentials that are digitally signed, immutable, tamper-resistant and verifiable universally.</p><p>Imagine, you are a real estate organization and have about 15 sales representatives performing outbound sales campaigns for you. Each time a sales representative speaks to a potential client, they have to provide a credential to prove their affiliation with your organization. Furthermore, the potential client has to further understand and validate the credential you provide, which in most cases can be a paper based form of credential which every one in the world understands. How does one do this without a paper format, though? Are there any digital standards or specifications that are accepted and understood by everyone, similar to the NMLS ID shown by your agent to prove their association with an organization?</p><p>The answer is yes, and it is named as the Verified Presentation profile.</p><p><strong>Verified Presentation</strong></p><p>Specifications and standards are central to the way we communicate, both in the physical and digital world. Today, standards are often developed as a part of community organizations or standards bodies such as the Internet Engineering Task Force (IETF), World Wide Web Consortium (W3C), and Decentralized Identity Foundation (DIF). These organizations bring together interested parties to develop a common description, understanding, and solution to a domain problem.</p><p>Currently, JSON Web Token(JWT) signing algorithms use ES256K private key or RSA256 signatures, which are essential to be conforming on both the issuing and the verifying party in this example you organization and your potential client. To solve this discrepancy of agreements, the JWT VC Presentation Profile was created.</p><p>The JWT VC Presentation Profile, which is a type of specification profile, requires only two. That’s a 20x reduction in complexity with one constraint as compared to the 40 algorithms supported in JWT signing.</p><p><strong>Verified Presentation Flow</strong></p><p>The flow begins as the Verifier generates a QR Code that contains a request_uri parameter which allows Self-Issued OP (SIOP) Request to be passed by reference. Verifier displays this QR code on their Verifier Website to initiate the exchange.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/1*xBAStRkXhbifTfgRLFXJtA.png" /></figure><p>Verifier Website presents the QR Code to the End User on their Verifier Website. The End User scans the QR Code using their Wallet. The Wallet parses the QR code to obtain the request_uri.</p><p>The Wallet sends a GET request to the obtained request_uri to retrieve the Request Object. The Request Object is a signed JWT that contains a set of request parameters as defined in <a href="https://identity.foundation/jwt-vc-presentation-profile/#term:siopv2-id1">SIOPv2 ID1</a> and <a href="https://identity.foundation/jwt-vc-presentation-profile/#term:openid4vp-id1">OpenID4VP ID1</a>. In particular, Wallet will determine which VCs to submit to the Verifier by processing presentation_definition property in the Request Object.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*1LCkdyWMHMDmpozu7O9qHQ.png" /></figure><p>Upon receiving the Request Object, the Wallet will identify VCs that satisfy the Presentation Definition and encapsulate them in a Verifiable Presentation (VP). The Wallet will complete the SIOP or Authorization Response by sending an ID Token and a VP Token to the Verifier’s redirect_uri.</p><p>Upon receiving the ID Token and VP Token, Verifier performs necessary checks such as DID resolution, signature validation, Linked Domain validation, revocation checks, etc. and sends an acknowledgement of receipt back to the Wallet. The flow of the Wallet presenting VCs to the Verifier is now complete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*zFHQaFfd_IuRZ9jFWsliuw.png" /></figure><p>What might this flow look like for your business? Here is a quick representation. Imagine, as a part of the high-touch sales experience with customers, you have your sales representatives meet potential clients and report daily metrics to your CRM app like salesforce. In this example, your CRM app will act as a verifier, however, a real-life primitive can be a physical individual who wishes to verify that you are indeed an agent representing a business, and hence will be a person with a camera-enabled smartphone. This individual can act as the verifier, who can scan the QR code your agent present on their device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sj57FjvVB2ZNYUHhMzgTBg.png" /></figure><p><strong>Benefits of Verified Credential</strong></p><p>By providing verified credentials for your employees, you have completely modernized your employee authentication process, by maintaining no expensive systems. An account on our decentralized cloud service will enable uniqueness of your employees identity and when tied with the employees government issued document like passport or driving license on our service, you have performed a digital background verification, identification and enabled your employee to carry a portable and transferrable set of credentials beyond a physical ID card or a system or database where you would otherwise store your employees PII data and assign a unique NMLS ID for your employee. Furthermore, you have provided a completely touchless experience for employee verification, authentication and identification with the help of our service.</p><p>Would you like to know more about how our service can enable your business to cut costs and eliminate expensive background check processes? Contact us now at info@fabvatar.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9696762241ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DIDComm a new protocol for Decentralized Identity]]></title>
            <link>https://medium.com/@anotherrohit/didcomm-a-new-protocol-for-decentralized-identity-4fac1abc713a?source=rss-235d0349831a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fac1abc713a</guid>
            <dc:creator><![CDATA[Rohit Nayak]]></dc:creator>
            <pubDate>Wed, 17 Aug 2022 20:53:56 GMT</pubDate>
            <atom:updated>2022-08-17T21:43:10.620Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of the decentralized identity revolution, DIDComm enables an open and crosscommunity standard to provide a secure communication channel between involved parties. It is based on decentralized identifiers and cryptographically guarantees the authenticity of any party represented by their prospective DID.</p><p>At the end of 2019, the Decentralized Identity Foundation (DIF decided to pick up the existing work around DID-based communication and <a href="https://medium.com/decentralized-identity/dif-starts-didcomm-working-group-9c114d9308dc">address the requirements of a broader and more heterogeneous community</a>.</p><p>DIDComm allows and even encourages other protocols to be built on top of it, so there are many different use cases that can be implemented. One common denominator is that there’s no need for a central server for the exchange of messages, thus removing the imbalance of established client-server scenarios that tend to favor institutions and organizations over clients and users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/989/0*Y8YTxSkAyNSLiWGt" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/0*K1n47-399cox-g-T" /></figure><p><strong>Protocols</strong></p><p>In general, protocols can be seen as a description or recipe for interactions that follow a certain pattern, such as ordering a book from an online web shop or paying at the supermarket checkout.</p><p>Properties of protocols comprise composability, meaning that more complex protocols can be built on top of simpler ones, often moving up in terms of abstraction while hiding technical details from those who usehigh-level level protocols. Protocols can also be nested, i.e. run within each other to perform sub-tasks.</p><p>In relation to DIDComm, protocols don’t have an overseer or central instance, but instead rely on mutual consent and shared understanding of how a protocol is meant to be used and all participants (can) act <a href="https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0003-protocols">as peers</a>.</p><p>Often, existing standards are also incorporated into protocols, e.g. <a href="https://datatracker.ietf.org/doc/html/rfc7516">JSE (JSON Web Encryption)</a>, <a href="https://datatracker.ietf.org/doc/html/rfc7515">JWS (JSON Web Signature)</a> or <a href="https://datatracker.ietf.org/doc/html/rfc6838">Media Types</a>.</p><h3>DIDComm Messaging</h3><p>According to the <a href="https://github.com/decentralized-identity/didcomm-messaging">DIDComm Messaging project on GitHub</a>, “DIDComm Messaging is the first specification in a family of related specs; … DIDComm is the common adjective for all of them, that all will share DID mechanisms as the basis of security.”</p><p>The <a href="https://identity.foundation/didcomm-messaging/spec/#message-types">specification</a> also states that “The casual phrase DIDComm Messaging is ambiguous, but usually refers to DIDComm Messaging encrypted messages…”. Infact, DIDComm messages are a powerful approach to enable two or more parties to communicate with each other in a secure fashion, and this is <a href="https://medium.com/decentralized-identity/dif-starts-didcomm-working-group-9c114d9308dc">a key piece for an interoperable decentralized identity stack</a>. It aims to enable anybody (or anything) to use it to <a href="https://github.com/decentralized-identity/didcomm-messaging">exchange machine-readable messages</a>, whether it is between people, institutions and organizations or things (computers, machines, IoT devices etc.).</p><h3>DIDComm Messaging Design</h3><p>Following the specification (<a href="https://identity.foundation/didcomm-messaging/spec/#specificrequirements">https://identity.foundation/didcomm-messaging/spec/#specificrequirements</a>), DIDComm messages should be designed in way that they are:</p><h3>Secure</h3><p>Messages should be secure in a way that they use state-of-the-art cryptography (“best of class”). Signing and optionally also encrypting messages means that they are cryptographically verifiable, making them tamper proof.</p><h3>Private</h3><p>Privacy is an important aspect not only in terms of the messages themselves but also in terms of the participants. Nobody should be able to know or deduce, who communicates with whom and about what.</p><h3>Decentralized</h3><p>Without a central server or instance, participants are seen as equal and <a href="https://identity.foundation/didcomm-messaging/spec/#specific-requirements">base their trust based</a> on the control of DIDs</p><h3>Transport Agnostic</h3><p>How messages get from the sender to the recipient(s) shouldn’t matter in terms of DIDComm — whether it is via a simplex or duplex communication pattern, online or even offline, all of this should be possible.</p><h3>Routable</h3><p>If no direct route is available between any two participants or the recipient’s devices aren’t available at the time of sending (e.g. because they are offline), DIDComm allows for messages to be routed between them in a secure and tamper-proof way.</p><h3>Interoperable</h3><p>Interoperability has several important aspects, for instance when different vendors of decentralized identities or participants in different distributed ledger networks want to communicate with each other.</p><p>It also means that different programming languages can be used, as well as different platforms, operating systems, hardware etc. In short, it aims to be a <a href="https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0005-didcomm/README.md">future-proof lingua franca of all selfsovereign interactions</a>.</p><h3>Extensible</h3><p>Extensibility means that based on asynchronous, simplex messaging as the common denominator, many other protocols and interaction patterns can be built on top of DIDComm.</p><p>Examples include <a href="https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0003-protocols">general guidelines for protocols</a> as well as some specific examples, such as the</p><ul><li><a href="https://github.com/hyperledger/aries-rfcs/tree/main/features/0095-basic-message">Basic message protocol</a> — A stateless and simple protocol with a single message type for sending messages between sender and receiver</li><li><a href="https://github.com/hyperledger/aries-rfcs/blob/main/features/0036-issue-credential/README.md">Issue credential protocol</a> — A protocol for issuing verifiable credentials from an issuer to a prospective holder, including proposals, offers and requests</li><li><a href="https://github.com/hyperledger/aries-rfcs/tree/main/features/0037-present-proof">Present proof features protocol</a> — A protocol to ask for or provide proofs (verifiable claims) for a verifier, based on verifiable credentials</li></ul><h3>Efficient</h3><p><a href="https://identity.foundation/didcomm-messaging/spec/#specific-requirements">No bandwidth, battery, storage space or processing power should be unnecessarily consumed.</a></p><h3>DIDComm Message Anatomy</h3><h3>The anatomy of DIDComm messages has two main layers, one of them being the envelope and the other one the content (plus an optional JWS envelope) as depicted below:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*ht2GBqwTS3XlX9FX" /></figure><h3>Envelope</h3><h3>Envelope</h3><p>On the envelope level, two alternatives can be differentiated, depending on the intended audience and use case:</p><h3>Signed Unencrypted</h3><p>When the authenticity of a message must be proven but the audience is not known to the sender, then a message can be wrapped in an unencrypted but signed envelope. Recipients can then verify based on cryptography whether the message is authentic.</p><h3>Encrypted</h3><p>When the audience is known to the sender, then the message can be wrapped in an encrypted envelope, in turn using one of three options to perform this step:</p><p>1. Anonymous encrypted format — No information about the sender is included</p><p>2. Authenticated encrypted format — Used when a message is encrypted for the recipient and the sender information is included through the use of authenticated encryption. Only the true recipient(s) can decrypt the message and authenticate that its content is truly from the sender</p><p>3. Signed encrypted format — Used when a message is encrypted for the recipient and the sender information is included with a non-repudiable signature. Only the recipient(s) can decrypt the message. Because of the non-repudiability, authentication of the message content can be done by any party who knows the sender</p><h3>Content</h3><p>On the content level, certain conventions regarding the message structure apply, such as the</p><ul><li>Message Type — Identification of the message as well as the protocol (see below)</li><li>Message Id — An ID generated by the sender, allowing unique identification of a message</li><li>Decorators — *Re-usable conventions that are present across multiple messages in order to handle the same functionality in a consistent manner</li></ul><p>For reference, see the <a href="https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0021-didcomm-message-anatomy/README.md">DIDComm Message Anatomy RFC.</a></p><h3>Message Types</h3><p>Even though the term DIDComm Messaging usually refers to encrypted messages, there are three formats that a message can have.</p><ol><li>Plaintext — The plaintext contents are processed when higher protocol levels remove the protective envelopes. It is also a useful message type for debugging purposes</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/258/0*t-BWyHpTVahMSbU7" /></figure><p>2. Signed — A signed <a href="https://tools.ietf.org/id/draft-looker-jwm-01.html">JWM (JSON Web Message)</a> envelope that associates a non-repudiable signature with the plaintext message inside. This message type is expected to be used in a few cases and only when the origin of the plaintext content has to be provable to third parties or when the sender can’t be proven to the recipient by authenticated encryption because the recipient is not known in advance.</p><p>3. Encrypted — An encrypted <a href="https://tools.ietf.org/id/draft-looker-jwm-01.html">JWM (JSON Web Message)</a> that hides all contents from all but the authorized recipients. Furthermore, the sender itself is only disclosed to exactly and only the authorized recipients, too. This format provides integrity guarantees and is the safest format for storing DIDComm messaging data. An encryption envelope is used for each hop on the journey between sender and recipient.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/0*lPTxQ7hmunqhMel_" /></figure><p>For reference, see the <a href="https://github.com/hyperledger/aries-rfcs/blob/main/features/0019-encryption-envelope/README.md">Encryption Envelope RFC</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fac1abc713a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>