<?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 lifeID on Medium]]></title>
        <description><![CDATA[Stories by lifeID on Medium]]></description>
        <link>https://medium.com/@lifeID_io?source=rss-158fa381de94------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bMaYTWFnO13gPpOiKNmIPg.jpeg</url>
            <title>Stories by lifeID on Medium</title>
            <link>https://medium.com/@lifeID_io?source=rss-158fa381de94------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 02:12:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lifeID_io/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[Restoring Trust in a World of Lost Identity]]></title>
            <link>https://medium.com/lifeid/restoring-trust-in-a-world-of-lost-identity-6c9c4ecd2468?source=rss-158fa381de94------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c9c4ecd2468</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[identity]]></category>
            <dc:creator><![CDATA[lifeID]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 16:03:16 GMT</pubDate>
            <atom:updated>2018-10-22T16:03:16.498Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zN-3YfNKOuob0eX_4ut28A.png" /><figcaption><strong>“Lost Identity” by Bartosz Beda — oil on canvas — 2015(c) </strong>Reproduced here by permission of the artist</figcaption></figure><p>[<em>ed. We are honored to have this post contributed by </em><a href="https://www.linkedin.com/in/nick-meyne-90010a2/"><em>Nick Meyne</em></a><em>, Founder at Social Market Technology Network out of Brighton, UK</em>, <em>who is deeply committed to the RChain Cooperative ecosystem and to the future impacts of Self-Sovereign Identity</em>]</p><p>In any platform, especially public, open platforms, the participants or users need to:</p><ol><li><strong><em>trust</em></strong> that the <strong><em>communications</em></strong> between participants are handled securely, reliably, at scale between them;</li><li>know, and <strong><em>trust something about each other</em></strong> in order to message or transact meaningfully;</li><li>manage <strong><em>identity risk</em></strong>.</li></ol><p>Rchain and LifeID are paired together as a foundation for open, decentralized ecosystems that can support future decentralisation at scale, with managed risk. This blog focuses on how they address communication, identity trust and risk.</p><h3><strong>Communication and Naming</strong></h3><p>Let’s start with the <strong><em>communications</em></strong> by looking at Rchain:</p><p>There is a nice, conversational <a href="https://youtu.be/BLQpnQBPvMA">interview</a> in Amsterdam with Tim Bansemer (European Ambassador, RChain and Rinke Hendicksen (Rholang Developer) published this month on YouTube.</p><p>They both summarise how some of the key features of Rchain enable it to scale in a way that other virtual machine blockchain platforms cannot. Part of this is the independence, concurrency and communication between ‘namespaces’. They begin by highlighting that <strong><em>trust </em></strong>in the other party is key in communication. Tim says:</p><blockquote>“ But you need to decide if you trust this other network. If you trust it you can communicate with each other …but this would obviously (depend on) the security and your trust in the other side, or in this case the other ‘<strong><em>namespace</em></strong>’ to be precise.”</blockquote><p>Rinke agrees and goes on to explain namespaces a little more:</p><blockquote>“A name and a namespace are crucial within Rchain because …Rchain is based on the notion of sending and receiving processes (between) names, so communication and computation on this <em>concurrent virtual machine</em> happens by message passing… the name is just there in the database… in the ‘tuple space’ of Rchain …and the name is just listening, (waiting to) receive something. …A namespace is a collection of all these names which are all receiving something and listening… A blockchain is basically a set of all kind of addresses and functions which can send and receive something, but in Rchain …there can be multiple namespaces living ‘in concurrence’ next to each other.”</blockquote><p>Tim adds an analogy:</p><blockquote>(Imagine) we are “sitting here having this interview in a circle, with people listening on a name. (It’s like) we’re listening on a channel: Hey Rinke! (Hey says Rinke, in reply) Rinke reacted …. it was like I was sending to the channel “Rinke” and he replied to me. He doesn’t need to say ‘Tim’ because this is (part of) the context we are sitting in: It’s clear that he means me. in Rchain (and language) he would write back to the channel I was communicating on…… So (in the analogy for) a namespace we could say we are in this room, and this group in this room. If we had loudspeakers on the ceiling, asking for the attention of all people in room xyz then we would all react as a group. …so this is the namespace. it’s a group! And the beauty of this is it represents (follows) …nature …the world we’re living in.” Or… if we compared to the human body … if you have an organ and every cell and molecule in that organ belongs to the namespace of the organ… heart for example.”</blockquote><p>That human body analogy works well: organs get on with their various jobs with only the minimum necessary communication between them. They’re not all waiting on some cerebral consensus process in my head. <a href="https://www.linkedin.com/in/tim-bansemer-51a12699/">Tim Bansemer </a>also calls out the need for <strong>globally unique names</strong>. For example, in the human body analogy, if I accidentally put my hand on a hotplate, an immediate and specific pain response very usefully signals the location of the damage and unconsciously ‘I’ orchestrate my musculo-skeletal system to move my hand away. Very specific ‘whole body’ messaging systems are important: Which hand? Which muscles? Where is the danger? By contrast a non-specific whole body ‘spasm’ would be a much less effective way to avoid danger in a hot kitchen!</p><p>Globally unique <strong><em>unforgeable</em></strong> names are also a key part of security. <a href="https://www.linkedin.com/in/mike-stay-ba8208133/">Mike Stay</a>, CTO of Pyrofex, points out that just copying a name and then creating multiple instances of the same name could be a great way of phishing for money or for personal details using spoof wallets. In the coming release of RChain (7) there is a feature that guarantees this uniqueness, particularly when creating / writing to the blockchain. We’d call that a good old fashioned ‘registry’. Mike tells us that Rchain will implement such a registry, enabling unique lookups so contract code can be made public for communication, but <em>securely</em> and without a nasty performance overhead or bottleneck. This decentralized registry is also the foundation for smart contract version control at the major, minor and patch level. It is native to the Rchain platform, and that makes for another advantage over Ethereum.</p><h3><strong>Trust and Identity</strong></h3><p>This blog post started with another assertion: that the parties in communication also need to know, and <strong><em>trust something about each other</em></strong> in order to message or transact meaningfully. This <em>trust in the other party</em> is where <strong>lifeID</strong> comes in. Chris Boscolo, Founder and CEO of LifeID <a href="https://www.youtube.com/watch?v=uHEEJ9bevV0">says:</a></p><blockquote>“LifeID is building a blockchain-based identity platform where users can coordinate the use of their identity with any other organization in the world. We’re building an identity platform that needs to scale to global levels”</blockquote><p>So with lifeID, and the Rchain registry, Rchain is implementing the globally unique naming and identity infrastructure that Tim and Rinke described as such a compelling feature. LifeID takes this further, being a native, decentralised, Self-Sovereign Identity (SSI) infrastructure based on emerging W3C standards.</p><p>The long story and advantages of SSI are explained more fully in <a href="http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html">Christopher Allen’s excellent paper</a>. The very brief story is that identifiers and attributes should be controlled by the identity holders or subjects — people or personas (like Tim Bansemer, the Rchain Ambassador) things, organisations — not by the centralised, giant ‘relying parties’ of today, who aggregate and correlate data, control the issue of credentials to their subjects and leak data into their ecosystem and beyond. For example, I think the picture at the top of this article — <strong><em>‘Lost Identity’ by Bartosz Beda</em></strong> — powerfully communicates the loss of control and privacy we all suffer in today’s fragmented, broken and abused identity ecosystem. A few years ago we were all told ‘no one cares about their data’ and ‘everyone trusts Facebook, Apple, Google and so on. How things have changed. And how quickly things can change.</p><p>LifeID explains more about the challenges of centralised digital identity in the introduction to their <a href="https://lifeid.io/whitepaper.pdf">white paper</a>. LifeID supports ‘pairwise’ issue of Decentralised Identifiers — DIDs. In today’s world the companies you deal with (Facebook, Apple, Google, Visa, Mastercard…) or intermediaries ‘identity providers’ (IDP) appointed by them, issue and control your verifiable credentials. By contrast, DIDs are controlled by you and there are typically ‘pairs’ of them for each peer-to-peer relationship that you have. <strong>You provide only the information necessary in order to transact with your peer (and usually vice-versa) and there’s no one sitting in the middle, aggregating, correlating, or even selling the data which has passed through their proprietary platform.</strong> A LifeID identity layer on RChain provides a scalable decentralised and trusted identity infrastructure, including lookup, “DID-resolution”, to support the wider partner and application ecosystem, globally.</p><p>LifeID’s initial focus is on organisations wishing to issue digital credentials for their membership (whether customers, employees, partners or associates..). These cannot be forged because they are signed by that organisation’s private key. Revocation is handled by a blockchain-based public revocation list. Members use an app to authenticate by scanning 2D barcodes. LifeID seeks to make it easier for organisational adopters by:</p><ol><li>Using DID protocols built on familiar modern auth and OpenID Connect standards</li><li>Providing a client SDK and an integration portal with Oauth and OpenID Connect api’s, and code frameworks to accelerate corporate integration</li><li>Providing administrator control / governance to help a local identity ecosystem to ‘bootstrap’, scale up and maintain its common membership and authentication and authorisation infrastructure.</li></ol><p>Outside of Rchain, lifeID is working on emerging SSI standards in the <a href="http://identity.foundation/">Decentralized Identity Foundation</a>. It is committed to interoperability with other blockchains / crypto platforms in a future distributed Identity 3.0 ecosystem. They work with other DID solution providers such as Evernym / Sovrin Foundation and UPort to extend the scope of the identity standards into specific use cases and attribute sets for key industry sectors such as supply chain, health, transport and so on.</p><h3><strong>Identity Risk</strong></h3><p>I believe there are great opportunities for new businesses (and for old businesses to re-invent themselves) in this new, open, decentralised and essentially ‘upturned’ world of naming and identity. It does NOT mean ‘putting identity on the blockchain’, nor does it equate ‘digital identity’ with ‘real-world identity’ or ‘self’ or even ‘legal identity’ in the hope of ‘solving’ the ‘identity problem’. All that is false hope.<strong> </strong>But It DOES mean, for example,<strong> </strong>that<strong> open standards for decentralised identity could give us newer, more efficient and fairer ways to manage identity <em>risk</em> in the new ecosystem.</strong></p><p><a href="https://medium.com/humanizing-the-singularity/a-blockchain-solution-for-identity-51fbcae94caa">Vinay Gupta pointed this out nicely</a> when he said ‘The identity system is going to be an insurance system’. In today’s centralised financial systems, the growing cost of cardholder identity fraud is paid for by the cardholders and merchants. Visa and Mastercard don’t <em>really</em> care — as they get paid enough in fees to cover it, including any dispute resolution and regulatory defence, there is little incentive to fix it. In a decentralised world, customers and merchants could instead be ‘micro-insuring’ according to the risk of their peer-to-peer transaction.</p><h3><strong>Conclusion</strong></h3><p>RChain is part of a third generation of blockchain platforms and lifeID is part of a second generation of distributed identity solutions. Built and organised as a co-operative, Rchain as a platform, with LifeID in its ecosystem as the identity layer, they show promise as a future foundation for open decentralised applications at scale. Both are rapidly evolving and innovating, and are far from stable, but t<strong>ogether they have the potential to provide a trusted decentralised platform to support global peer to peer transaction rates and self-sovereign identity with global consumer reach</strong>.</p><p>Despite problems and abuses, today’s centralised, mostly hierarchical world of organisation, communication and finance will probably remain the dominant and most efficient ‘socio-techno-economic’ pattern that humans follow. <strong>However, there are markets, human populations and environmental ecosystems with problems such as broken trust, massive scale or risk that could perhaps be solved better by applying decentralised, peer to peer patterns. Centralised and decentralised systems will coexist, perhaps uncomfortably, and even compete.</strong></p><p>The trick for Rchain and lifeID to manage is the ‘bootstrapping’ of a decentralised user community and application ecosystem that makes it sensible to adopt and grow with ‘synergies’ or common benefit for all. There should be a business design and roadmap, from today’s dominant centralised landscape to make that happen. But how to do that is another story, and the subject of another blog!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c9c4ecd2468" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifeid/restoring-trust-in-a-world-of-lost-identity-6c9c4ecd2468">Restoring Trust in a World of Lost Identity</a> was originally published in <a href="https://medium.com/lifeid">lifeID</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ARCBLOCK AND LIFEID ANNOUNCE PARTNERSHIP TO BRING DIGITAL IDENTITY TOOLS TO BLOCKCHAIN 3.0]]></title>
            <link>https://medium.com/lifeid/arcblock-and-lifeid-announce-partnership-to-bring-digital-identity-tools-to-blockchain-3-0-5296c60a0940?source=rss-158fa381de94------2</link>
            <guid isPermaLink="false">https://medium.com/p/5296c60a0940</guid>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[lifeID]]></dc:creator>
            <pubDate>Wed, 17 Oct 2018 16:25:49 GMT</pubDate>
            <atom:updated>2018-10-17T16:25:49.723Z</atom:updated>
            <content:encoded><![CDATA[<h3>ARCBLOCK AND LIFEID ANNOUNCE PARTNERSHIP TO BRING DIGITAL IDENTITY TOOLS TO BLOCKCHAIN 3.0 DEVELOPER ECOSYSTEM</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gt-aiF1sYpcBlnl9esbkOw.png" /></figure><h3>ArcBlock Announces Partnership with LifeID</h3><p>Bellevue, WA — (Press Release) — ArcBlock, creator of the world’s first Developer-ready Blockchain 3.0 ecosystem, and LifeID, creator of the leading open-source, tokenized protocol for sovereign identity, have announced a new technology partnership to bring LifeID’s blockchain-based digital identity protocol and developer tools to ArcBlock’s blockchain 3.0 developer ecosystem.</p><p>LifeID is creating an open, public identity protocol for next-generation web and blockchain ecosystems to give users an easy, convenient and secure way to control their identity. With lifeID, users have more options on how they want to manage their personal identity data online and offline using blockchain-based authentication.</p><p>Through this new partnership, ArcBlock continues to redefine what it means to build a decentralized application (DApp) by giving developers an entirely new way to make DApps and blockchain services that remove many of today’s common problems. With nothing more than a browser and unified architecture, developers can write their code once and use it across different blockchains automatically. Developers no longer need to worry about spinning up nodes, poor performance or vendor lock-in, but instead can focus on doing what they do best — building, managing and deploying DApps efficiently.</p><p>“Starting today, ArcBlock is giving developers a powerful digital identity protocol that enables users to control their own identity easily,” said Tyr Chen, VP of Engineering for ArcBlock. “Today, companies and developers recognize that digital data is a powerful asset, and are working to keep control of that data in a manner that lets the user have control. With LifeID, self-sovereign identity is now a reality.”</p><p>“lifeID and Arcblock are natural blockchain infrastructure partners,” said Chris Boscolo, lifeID CEO and Founder. “Arcblock’s vision of a powerful blockchain developer ecosystem is perfectly aligned with the lifeID mission of revolutionizing personal digital identity. We’re both building out the necessary foundations to achieve our shared vision of blockchain ecosystems serving developers and their users. Part of this vision means having blockchain-based identity for any Web 3.0 application. lifeID’s partnership with Arcblock will accelerate our goal of ‘digital identity with dignity’ for the world.”</p><p>For anyone interested in learning more, you can visit LifeID <a href="https://www.lifeid.io/">https://www.lifeid.io</a>, or contact ArcBlock visiting <a href="https://www.arcblock.io/">https://www.arcblock.io</a> or Telegram community at t.me/arcblock for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5296c60a0940" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifeid/arcblock-and-lifeid-announce-partnership-to-bring-digital-identity-tools-to-blockchain-3-0-5296c60a0940">ARCBLOCK AND LIFEID ANNOUNCE PARTNERSHIP TO BRING DIGITAL IDENTITY TOOLS TO BLOCKCHAIN 3.0</a> was originally published in <a href="https://medium.com/lifeid">lifeID</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[lifeID Insider: RChain Spotlight plus Rholang Smart Contracts]]></title>
            <link>https://medium.com/@lifeID_io/lifeid-insider-rchain-spotlight-plus-rholang-smart-contracts-bff6f2d22eaf?source=rss-158fa381de94------2</link>
            <guid isPermaLink="false">https://medium.com/p/bff6f2d22eaf</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[passwords]]></category>
            <dc:creator><![CDATA[lifeID]]></dc:creator>
            <pubDate>Thu, 04 Oct 2018 17:34:28 GMT</pubDate>
            <atom:updated>2018-10-04T21:56:32.492Z</atom:updated>
            <content:encoded><![CDATA[<p>10/04/2018</p><h3>Hello lifeIDealists!</h3><p><strong>This is the second in our weekly roll-out rhythm for our open source code releases.</strong> Last week, the first release was the lifeID Foundation’s Open Source DID Repository. You can head over to <a href="https://gitlab.com/lifeid/lifeid-did">Gitlab</a> to check out that new <strong>lifeID DID repository</strong>.</p><p>This week we’re publishing our DID Registry smart contracts that will be integrated into our API Bridge. You can check out a description below, provided by lifeID’s resident functional programming expert, Seth Bailey.</p><h3>lifeID’s RChain Partner Spotlight</h3><p><strong>Control Your Data and Eliminate Passwords</strong></p><p>This is a <a href="https://www.rchain.coop/blog//lifeid-control-your-data-and-eliminate-passwords">great post from RChain</a> on lifeID’s vision and value.</p><p>lifeID’s revolutionary Personal Digital Identity protocol is being built on the RChain blockchain. RChain is an innovative 3rd generation blockchain built by the RChain Cooperative. If you don’t know about RChain yet, we encourage everyone to learn more and get involved. You can <a href="http://www.rchain.coop/">watch a short video</a> on their site to get started.</p><h3>lifeID DID Registry Smart Contracts</h3><p>You can find the draft of our DID registry smart contracts here: <a href="http://gitlab.com/lifeid/did-registry">https://gitlab.com/lifeid/did-registry</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/483/0*3xmpDmflIFrr06dW.jpg" /></figure><p>If they look a little strange, that’s because <em>they are!</em> Our DID registry development will mostly take place in rholang, the smart contract language of RChain. It is very safe, and designed with concurrency as a priority, but there’s no denying it can be pretty hard to follow the first time you see it because it works very differently than most programming languages. Rholang is still under active development which means this registry will go through many iterations. Right now, it is mostly <strong>create</strong>, <strong>update</strong> and <strong>delete</strong> channels with an authentication layer, and it will certainly change and grow. We wanted to open the development to the public as early possible because the registry is at the core of what we do.</p><p>If you have any questions, please post them in our <a href="http://gitlab.com/lifeid/did-registry">Gitlab Repo</a>! 🙏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bff6f2d22eaf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello lifeID OSS Community!]]></title>
            <link>https://medium.com/lifeid/hello-lifeid-oss-community-81c50e1464d4?source=rss-158fa381de94------2</link>
            <guid isPermaLink="false">https://medium.com/p/81c50e1464d4</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[lifeID]]></dc:creator>
            <pubDate>Wed, 26 Sep 2018 17:30:59 GMT</pubDate>
            <atom:updated>2018-09-26T17:30:59.585Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*Fsa6hyXT3dGVeARU.png" /></figure><p><strong>Last week we started our weekly roll-out rhythm for our open source code releases.</strong> The first release is the lifeID Foundation’s Open Source DID Repository. Head over to <a href="https://gitlab.com/lifeid/lifeid-did">Gitlab</a> to check out the new <strong>lifeID DID repository</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/0*koEbOmGJwbdG_g6P.jpg" /></figure><p><strong>Heads up</strong> that next week we’ll be publishing our OSS Community plan. We’d love your feedback on our approach and how you’d we can provide the best infrastructure to make engagement easy for you. We’re all in this together to build decentralized Digital Identity.</p><h3>Open Source lifeID DID repository</h3><p><strong>What are DIDs?</strong> DIDs are decentralized identifiers that make the concept of Self-Sovereign Identity work in a decentralized architecture. DIDs are an important innovation. They give us the ability to establish unique digital identifiers that are persistent, secure, and globally resolvable, yet they don’t rely on centralized organizations or middlemen to create and maintain them. That is done automagically using lifeID’s new user onboarding process for each service or relationship.</p><p>This lifeid-did library gives users all the tools they need to create, encode and decode lifeID decentralized identifiers (“DIDs”). On the lifeID platform, a DID is an identifier shared between two or more parties that establishes a cryptographic relationship and communication channel through which you can digitally interact with someone else.</p><p>A user will create a different and unique DID relationship for each digital identity relationship they establish, whether that’s for a website, corporation or person. For more information on DIDs generally, see the <a href="https://w3c-ccg.github.io/did-spec/">W3C DID specification</a>. For more information on the lifeID DID specification check out our own implementation details (in draft form) here: <a href="https://lifeid.github.io/did-method-spec/">https://lifeid.github.io/did-method-spec/</a></p><p>lifeID DIDs are the cornerstone of the lifeID Identity Protocol ecosystem. lifeID DIDs allow us all to disclose exactly what information you choose, no more and no less. They also allow us to maintain the security of knowing that we can recover our identifiers if we lose our phone, computer or backup storage.</p><p>We will release more info on how to integrate DIDs into your own software stack as we continue to open-source our platform in the coming weeks.</p><p>If you have any questions, please post them in our <a href="http://gitlab.com/lifeid/lifeid-did">Gitlab Repo</a> or post in our Discord OSS channel <a href="https://discord.gg/6Gfq4zf!">https://discord.gg/6Gfq4zf!</a> 🙏</p><p>Thank you for joining the lifeID Movement! 🙌</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81c50e1464d4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifeid/hello-lifeid-oss-community-81c50e1464d4">Hello lifeID OSS Community!</a> was originally published in <a href="https://medium.com/lifeid">lifeID</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[lifeID Insider: First lifeID Foundation Code Release!]]></title>
            <link>https://medium.com/lifeid/lifeid-insider-first-lifeid-foundation-code-release-b32726cfcc4d?source=rss-158fa381de94------2</link>
            <guid isPermaLink="false">https://medium.com/p/b32726cfcc4d</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[identity-management]]></category>
            <category><![CDATA[digital-identity]]></category>
            <dc:creator><![CDATA[lifeID]]></dc:creator>
            <pubDate>Thu, 20 Sep 2018 15:39:06 GMT</pubDate>
            <atom:updated>2018-09-20T15:41:58.474Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*cZMVxgZiLskH-O9I.jpg" /></figure><p><strong>Today we’re beginning our weekly roll-out rhythm for our open source code releases.</strong> The first release is the lifeID Foundation’s Open Source DID Repository. Head over to <a href="https://gitlab.com/lifeid/lifeid-did">Gitlab</a> to check out the new <strong>lifeID DID repository</strong>.</p><p><strong>What are DIDs?</strong> DIDs are decentralized identifiers that make the concept of Self-Sovereign Identity work in a decentralized architecture. DIDs are an important innovation. They give us the ability to establish unique digital identifiers that are persistent, secure, and globally resolvable, yet they don’t rely on centralized organizations or middlemen to create and maintain them. That is done automagically using lifeID’s new user onboarding process for each service or relationship.</p><h3>Open Source lifeID DID repository</h3><p>This lifeid-did library gives users all the tools they need to create, encode and decode lifeID decentralized identifiers (“DIDs”). On the lifeID platform, a DID is an identifier shared between two or more parties that establishes a cryptographic relationship and communication channel through which you can digitally interact with someone else.</p><p>A user will create a different and unique DID relationship for each digital identity relationship they establish, whether that’s for a website, corporation or person. For more information on DIDs generally, see the <a href="https://w3c-ccg.github.io/did-spec/">W3C DID specification</a>. For more information on the lifeID DID specification check out our own implementation details (in draft form) here: <a href="https://lifeid.github.io/did-method-spec/">https://lifeid.github.io/did-method-spec/</a></p><p>lifeID DIDs are the cornerstone of the lifeID Identity Protocol ecosystem. lifeID DIDs allow us all to disclose exactly what information you choose, no more and no less. They also allow us to maintain the security of knowing that we can recover our identifiers if we lose our phone, computer or backup storage.</p><p>We will release more info on how to integrate DIDs into your own software stack as we continue to open-source our platform in the coming weeks.</p><p>If you have any questions, please post them in our <a href="http://gitlab.com/lifeid/lifeid-did">Gitlab Repo</a>! 🙏</p><p><strong>The lifeID Foundation Qualified Investor Token Sale is Live!</strong></p><p>If you’d like to participate, please register here</p><p><a href="https://lifeid.io/IDtoken"><strong>Join the Movement</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b32726cfcc4d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifeid/lifeid-insider-first-lifeid-foundation-code-release-b32726cfcc4d">lifeID Insider: First lifeID Foundation Code Release!</a> was originally published in <a href="https://medium.com/lifeid">lifeID</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[lifeID Foundation Qualified Investor Token Sale is Live!]]></title>
            <link>https://medium.com/lifeid/lifeid-foundation-qualified-investor-token-sale-is-live-f42970e4b6ee?source=rss-158fa381de94------2</link>
            <guid isPermaLink="false">https://medium.com/p/f42970e4b6ee</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[lifeID]]></dc:creator>
            <pubDate>Wed, 19 Sep 2018 15:50:49 GMT</pubDate>
            <atom:updated>2018-09-19T15:51:36.471Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’d like to participate, please register here: <a href="http://www.lifeid.io/IDtoken"><strong><em>Join the Movement</em></strong></a></p><p>We’ve heard from thousands of people here in the US and around the world who want to participate in supporting our project, and we are deeply grateful. Thank you for all your questions, suggestions, and most of all, your patience as we were working through this new process in our growing industry.</p><p>Our goal is to include as much of our community as possible. So before the launch of the network, we’ll be running two limited, fundraisers for the lifeID Foundation: one for US-based investors and one for International investors. These will function as two legally separate raises that fall under different requirements and guidelines.</p><p>Each of these are sales for future tokens for qualified investors. At network launch, your tokens will convert to lifeID Protocol “ID Tokens.” After these two fundraising events, no further rounds are expected before network launch.</p><p>To make this happen as smoothly and safely as possible, US community members who would like to participate in the pre-sale will be invited to go through an Accredited Investor check. International, non-US investors, will be invited to go through a KYC check.</p><p>Thank you and please let us know if you have any questions at <a href="/service/mailto:ID@lifeID.io">ID@lifeID.io</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f42970e4b6ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifeid/lifeid-foundation-qualified-investor-token-sale-is-live-f42970e4b6ee">lifeID Foundation Qualified Investor Token Sale is Live!</a> was originally published in <a href="https://medium.com/lifeid">lifeID</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LifeID DID Method Version 0.1 Now Available in the W3C DID Method Registry]]></title>
            <link>https://medium.com/@lifeID_io/lifeid-did-method-version-0-1-now-available-in-the-w3c-did-method-registry-f1334bc1e48c?source=rss-158fa381de94------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1334bc1e48c</guid>
            <category><![CDATA[self-sovereign-identity]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[identity]]></category>
            <dc:creator><![CDATA[lifeID]]></dc:creator>
            <pubDate>Thu, 13 Sep 2018 17:13:09 GMT</pubDate>
            <atom:updated>2018-09-13T17:13:09.331Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Delightful Announcement: LifeID DID Method Version 0.1 Now Available</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D3o8iaeo0ueLE3oj_XeVbQ.png" /></figure><p>This is months in the making, and we are beyond happy about this. Our team has submitted to the World Wide Web Consortium (W3C) Credentials Community Group-maintained <a href="https://w3c-ccg.github.io/did-method-registry/">Decentralized Identifier Registry</a> our very first version of the <a href="https://lifeid.github.io/did-method-spec/">lifeID DID Method specification</a>! What does this mean? Two things.</p><p>First, recall that the building blocks of self-sovereign identities are decentralized identifiers (DIDs). So <strong>by publishing our lifeID spec, we’re formally describing lifeID’s particular approach to creating self-sovereign identities and how it conforms with the global standard</strong>, the “<a href="https://w3c-ccg.github.io/did-spec/">DID Specification</a>”. It means we’re telling the development world and the open standards community how the lifeID protocol will work architecturally, and what the smart contracts of our protocol will do.</p><p>Second, this means that <strong>lifeID’s DID Method, our approach to creating self-sovereign identifiers, is now listed in the official W3C registry table of the handful of such methods under development in the world</strong>, right next to BTCR, ERC725, Sovrin, Veres One, uPort, Ontology, and others. Per the table, ours, “<em>did:life:</em>” currently is one of only ten such methods being developed on the planet:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oS4iwrc6noa_Qkdf5uH6eg.png" /></figure><p>With the publication of this draft, we join the global self-sovereign identity community in promulgating this foundational identity infrastructure. As our CEO Chris Boscolo commented today, “One key to the adoption of a new identity paradigm are standards that help drive adoption. Kudos to the many folks at the W3C for pushing this [DID Specification]”. We’re excited to help promote the vision of self-sovereign identity and a new form of identity management on the open web.</p><p>You can now find our DID method in the registry table at <a href="https://w3c-ccg.github.io/did-method-registry/"><strong>DID Method Registry: A registry for Decentralized Identifier Methods</strong></a><strong> </strong>and read our lifeID DID Method v0.1 in full at <a href="https://lifeid.github.io/did-method-spec/"><strong>LifeID DID Method Version 0.1: A Decentralized Identifier Method for the LifeID Protocol</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1334bc1e48c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[lifeID Foundation Purpose & Fundraising]]></title>
            <link>https://medium.com/lifeid/lifeid-foundation-purpose-fundraising-81eaf6b9e801?source=rss-158fa381de94------2</link>
            <guid isPermaLink="false">https://medium.com/p/81eaf6b9e801</guid>
            <category><![CDATA[digital-identity]]></category>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[token]]></category>
            <dc:creator><![CDATA[lifeID]]></dc:creator>
            <pubDate>Tue, 04 Sep 2018 17:50:23 GMT</pubDate>
            <atom:updated>2018-09-19T03:24:52.322Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jnwYjiJVzCAAs_r8leE8qg.jpeg" /></figure><h4><strong>lifeID Mission for Digital Identity</strong></h4><p>How we manage our identity online and in the physical world is broken. The current approach to user identity requires creating, storing, and maintaining an average of 130+ passwords. This constant juggling effort goes a long way towards explaining why managing and securing our personal and financial data is so frustrating and why we’re all so vulnerable.</p><p>Companies are feeling the flip side of this user nightmare. Centralized data stores — especially personal identity data — are honeypots for hackers and social engineers. Liability for these kinds of data is becoming a top management priority. We’ve watched market caps plunge for companies that haven’t properly secured their users’ data.</p><p>lifeID is proposing a more effective approach: We’re building an open, permissionless — and highly-secure — blockchain-based identity service called the lifeID Protocol. The protocol will be deployed and managed by the self-sustaining, self-funding lifeID Foundation, as a public infrastructure identity-as-a-service layer for the blockchain and web 2.0 ecosystems, supporting a wide variety of identity-specific transactions. The lifeID Identity Protocol will be a more simple, secure and straightforward solution to our international “identity crisis” — a life-long, self-sovereign digital identity called “lifeID™”.</p><p>lifeID will provide users with the same single sign-on (SSO) convenience that Facebook or Google logins offer, but free of the risks and privacy violations <a href="https://medium.com/@lifeID_io/despite-ceo-assurances-facebook-data-mining-will-continue-6162b15ecbc">we’ve come to associate with social media</a> corporations.</p><p>Armed with a self-sovereign digital identity, each user will be empowered to securely and easily manage his or her online and real-world transactions wherever authenticating identification is a requirement. Best of all, users will be able to use their identity to transact free of the third-party oversight by intrusive social media companies, financial institutions, corporations and government agencies that pervade the current structure.</p><h4>The lifeID Foundation Purpose</h4><p>The lifeID Foundation was created to develop and market the lifeID Protocol &amp; Platform, a decentralized, blockchain-based open identity provider. When the network launches, it will create a decentralized network for self-sovereign identity creation and management. The lifeID Foundation token, the <strong>ID Token,</strong> will be used to store and exchange value on the platform for services and for governance. ID Tokens’ primary purpose will be the exclusive method of payment for services on the platform. At network launch, The lifeID Foundation <a href="http://www.lifeid.io/whitepaper.pdf">whitepaper</a> will define the ID Token allocation, transaction fees, and initial governance mechanisms.</p><p>The foundation itself is a non-profit organization with well-defined objectives that are laid out in the whitepaper. In essence, the objectives serve the goal of launching the lifeID Platform for self-sovereign identity and promoting a growing, high-value network.</p><p>Funds raised by the lifeID Foundation will be used to ensure a growing and thriving ecosystem of developers, protocol users, and lifeID identity holders. This includes finding the best talent and focusing on R&amp;D while promoting the platform to ensure the long-term success and persistence of the identity service.</p><p>To drive adoption at network launch, lifeID will ensure that tokens are widely distributed throughout the ecosystem to jump-start the minimum viable ecosystem. Priority will be given to platform developers, engaged community members, ecosystem partners, and software developers who use the platform to serve lifeID’s users. At launch, ID Token holders will be able to start experimenting with the lifeID Platform and building applications.</p><h4>The Problem with ICOs</h4><p>Blockchain has been a geeky playground for wild innovative projects, new kinds of businesses and a brave new world of fundraising. The wild valuations and lack of funding caps have tarnished perceptions of ICOs. Too many have been pump-and-dump, quick-buck schemes. Others have promoted unrealistic projects that somehow raised tens of millions of dollars without a genuine hope of delivering on a thinly thought-out whitepaper.</p><p>As a result, the SEC has served subpoenas to many of these projects. Although most of them were acting in good faith, many ran afoul of an archaic regulatory environment designed to protect retail investors. Even worse, some projects were actually designed specifically to exploit the new ICO model by raising funds, then redirecting those funds to individuals with nefarious intentions.</p><p><strong>Our challenge in this environment is that any misstep during the fundraising process, no matter how well-intentioned, can have crushing effects on the success of any project — meaning that the success of the vision itself is at stake.</strong></p><p>If the fundraising process kills your project’s chance to fulfill the mission, then you’ve failed before you’ve truly begun. At the lifeID Foundation, we will take every precaution we can to prevent that from happening.</p><p><strong>We are true believers. We’re committed to creating an open-source, permissionless, self-sovereign identity solution for our ecosystem. </strong>Our goal for providing this open, public identity platform is to ensure that everyone can own and manage their identities with convenience, privacy and security.</p><p>With this in mind, and after deep investigation, the lifeID Foundation has zeroed in on a prudent fundraising approach. We’ve heard from thousands of people around the world who want to participate in supporting our project and we are deeply grateful. So thank you for all your questions, suggestions, and most of all, your patience, as we work through this evolving process in an industry chock full of ambiguity.</p><h4>lifeID Foundation Qualified Investor Token Sale</h4><p>As a result of these considerations, we believe the best path to achieve our mission does not include an ICO. Before the launch of the network and the distribution of ID Tokens, we will be running two, limited fundraising events for the lifeID Foundation. These will both be for qualified investors who would like to participate in a ‘SAFT-like’ purchase for future tokens. At network launch, future tokens will be delivered as lifeID Protocol “ID Tokens”.</p><p>Our goal is to include as many members of our community as possible, within regulatory guardrails. So these two fundraising efforts, one for US citizens and one for non-US citizens, will function as two legally separate fundraising events that fall under different requirements and guidelines. After these two fundraising events, no further rounds are expected before network launch.</p><p>To make this happen as smoothly and safely as possible, US community members who would like to participate will be invited to go through an Accredited Investor check. International, non-US investors, will be invited to go through a KYC check.</p><p><strong>The fundraising events will begin September 6th, 2018. If you are interested in participating, you can register </strong><a href="https://lifeid.io/IDtoken"><strong>HERE</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81eaf6b9e801" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifeid/lifeid-foundation-purpose-fundraising-81eaf6b9e801">lifeID Foundation Purpose &amp; Fundraising</a> was originally published in <a href="https://medium.com/lifeid">lifeID</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We’ve joined W3C!]]></title>
            <link>https://medium.com/lifeid/weve-joined-w3c-111025f2c004?source=rss-158fa381de94------2</link>
            <guid isPermaLink="false">https://medium.com/p/111025f2c004</guid>
            <category><![CDATA[digital-id]]></category>
            <category><![CDATA[web-standards]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[lifeID]]></dc:creator>
            <pubDate>Wed, 22 Aug 2018 20:22:53 GMT</pubDate>
            <atom:updated>2018-08-22T20:22:53.575Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VaOgX74tEWsph0ssEf9oLQ.jpeg" /></figure><p>We are delighted to announce we have joined as the latest member organization of the <a href="http://w3c.org/">World Wide Web Consortium</a> (W3C), a standards body for the open web. Our Chief Blockchain Evangelist for the lifeID platform, <a href="https://www.linkedin.com/in/alexoblockchain">Alex Ortiz</a>, will serve as our W3C Advisory Committee Representative.</p><p>Through participation in <a href="http://w3c.org/">W3C</a> and its <a href="https://www.w3.org/2017/vc/WG/">Verifiable Claims Working Group</a>, we’ll learn from our industry peers and contribute our own ideas about decentralized self-sovereign identity with a global community of professionals from <a href="https://www.w3.org/Consortium/Member/List">472 member organizations</a>. W3C has contributed important foundational work to the blockchain identity industry, including specifications and technical reports for <a href="https://w3c-ccg.github.io/did-spec/">Decentralized Identifiers</a> (DIDs), <a href="https://www.w3.org/TR/verifiable-claims-data-model/">verifiable claims</a> and <a href="https://www.w3.org/community/credentials/">credentials</a>, and <a href="https://www.w3.org/TR/verifiable-claims-use-cases/">verifiable claims/credentials use cases</a>. We look forward to learning from this body of work and informing the direction of open, interoperable, and decentralized identity systems, including the lifeID platform, in the years to come.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=111025f2c004" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifeid/weve-joined-w3c-111025f2c004">We’ve joined W3C!</a> was originally published in <a href="https://medium.com/lifeid">lifeID</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[lifeID in Depth: Self-Sovereign Identity and How it Works]]></title>
            <link>https://medium.com/lifeid/lifeid-in-depth-self-sovereign-identity-and-how-it-works-582a09d97899?source=rss-158fa381de94------2</link>
            <guid isPermaLink="false">https://medium.com/p/582a09d97899</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[digital-identity]]></category>
            <dc:creator><![CDATA[lifeID]]></dc:creator>
            <pubDate>Wed, 22 Aug 2018 20:21:07 GMT</pubDate>
            <atom:updated>2018-10-08T20:48:06.079Z</atom:updated>
            <content:encoded><![CDATA[<p>We’re getting ready to launch the lifeID Protocol<strong> </strong>Network in Q1,<strong> </strong>so<strong> </strong>we want make sure everyone groks all the aspects of how lifeID is developing and launching the lifeID Identity Protocol. Over the next several weeks, we’ll be covering what you need to know about the architecture, the protocol tokenomics, community governance, our marketing philosophy in a “zero-knowledge” user data world, as well as everything else that touches you, our partners, token holders and community.</p><p>This article covers what “Self-Sovereignty Identity” is and how it works using a blockchain identity protocol.</p><h3>Self-sovereign Identity and How it Works</h3><p>A self-sovereign digital identity is an identity that’s created and managed by you, the user. It has all of the credentials you need to interact in the digital and physical world, without relying on a centralized organization or authority.</p><p>Self-sovereign identities use public key cryptography, so to understand how they work requires a basic understanding of how this cryptography is used.</p><p>Public key cryptography is a process in which cryptographic keys are generated in pairs, a public key and a private key. The public key can be viewed by anyone, while the private key is kept secret by the user. Users can prove ownership of the public key by using, but not showing, the private key itself. <strong>This proof of ownership of the public key is the mechanism owners use to prove that a self-sovereign identity is theirs.</strong></p><p>To create a self-sovereign digital identity, an app creates a unique digital identifier along with a cryptographic public/private key pair. This “identifier” is just a large, unique random number. Using a global public registry — in this case a blockchain — the user associates the public half of the key pair with the unique digital identifier.</p><p>The private key is also an extremely large number that’s ridiculously hard to memorize or type into keyboard. Instead, it gets stored in a <a href="https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys/storing_keys_in_the_secure_enclave">secure enclave</a> like on an iPhone or Android<strong>. If the user loses access to the private key associated with their digital identifier, they create a new key pair and update the global public registry.</strong> <strong>This key management is an essential feature of self-sovereign identity. </strong>(We’ll cover how key recovery works in a future note, but the short version is that it uses smart contracts combined with standard “friends or family” recovery methods chosen by the user during initial setup.)</p><p><strong>Unique identifiers represent each peer-to-peer relationship established by the user with a third party, like a friend, a bank, their university, a website, etc. These identifiers are then used to ensure each party is who they say they are for these peer-to-peer interactions.</strong> As an example, when a user creates an account on a new website, a new key pair is created. To authenticate with the website, the user proves ownership of this identifier using the private key associated with the identifier (all this happens in the app — users don’t have to manage this themselves). When the website wants to authenticate a user, it looks up the user’s identifier on the blockchain, determines the associated public key, and confirms that the user has the private key. <strong>It’s worth noting that updating the keys associated with the unique digital identifier does not require that the user contact the website where the identifier was used. Instead, updates are managed in the background by a lifeID-power app.</strong></p><p>Making all of this work requires a secure global registry where users can update the digital identifiers that they control — where the data, once written, can’t be changed or removed except by the user with the private key. <strong>Until the advent of blockchain technology, these requirements were impossible to meet.</strong></p><p><strong>How do you create an open public central registry that isn’t itself centrally controlled? This is where the magic of the blockchain comes in!</strong>It’s the source of truth for key management, mapping a user’s unique digital identities to their corresponding public keys. Because it uses a blockchain-based consensus mechanism to maintain the accurate and up-to-date state of the registry, it requires no central authority to control or operate it.<strong> In fact, an open, self-sovereign digital identity is one of the best use cases for a permissionless, decentralized blockchain.</strong></p><p>To fully realize the promises of a self-sovereign identity, the blockchain that functions as the central registry must be built with these three important pillars that we’ll cover in next the next edition of our newsletter.</p><p>1. Driven by economic incentive</p><p>2. Open and Permissionless</p><p>3. Self Governance</p><p>Please let us know if you have questions about this newsletter topic or anything else via email, info@lifeID.io, or twitter, lifeID_io</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=582a09d97899" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifeid/lifeid-in-depth-self-sovereign-identity-and-how-it-works-582a09d97899">lifeID in Depth: Self-Sovereign Identity and How it Works</a> was originally published in <a href="https://medium.com/lifeid">lifeID</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>