<?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 Michael Sena on Medium]]></title>
        <description><![CDATA[Stories by Michael Sena on Medium]]></description>
        <link>https://medium.com/@msena?source=rss-fc3b0ec804e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6BLUPDNSlkEPvQsJeCMuFA@2x.jpeg</url>
            <title>Stories by Michael Sena on Medium</title>
            <link>https://medium.com/@msena?source=rss-fc3b0ec804e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 14:59:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@msena/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[IDX and SkyDB joins forces for a future of Web3 hackathon]]></title>
            <link>https://medium.com/ceramic/idx-and-skydb-joins-forces-for-a-future-of-web3-hackathon-83eff179a9a1?source=rss-fc3b0ec804e------2</link>
            <guid isPermaLink="false">https://medium.com/p/83eff179a9a1</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[ecosystem]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[skydb]]></category>
            <category><![CDATA[ceramics]]></category>
            <dc:creator><![CDATA[Michael Sena]]></dc:creator>
            <pubDate>Mon, 02 Nov 2020 19:05:54 GMT</pubDate>
            <atom:updated>2020-11-02T19:06:22.527Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QkWu8R2cfu_-7gdmrRSEyQ.png" /></figure><h3>IDX and SkyDB join forces for a future of Web3 hackathon</h3><h4>The hackathon lasts through Nov. 23</h4><p>In recent months, the Web3 ecosystem has seen an explosion of of new tools and platforms that allow developers to build mature, sophisticated dweb applications with functionality that was previously unimaginable.</p><p>To celebrate this evolution in Web3, <a href="https://medium.com/3box/idx-a-devkit-for-open-identity-48edc88e8e85"><strong>IDX</strong></a> is teaming up with <a href="https://blog.sia.tech/skydb-a-mutable-database-for-the-decentralized-web-7170beeaa985"><strong>SkyDB</strong></a> to kick off a hackathon which gives you the opportunity to experiment with and build applications that combine these two new technologies. Our teams are offering a combined $12,000 in rewards paid out in Siacoin (SC), and to make things even sweeter there’s a consolation prize paid out to every eligible submission.</p><p><strong>The hackathon kicks off today November 2nd on </strong><a href="https://gitcoin.co/hackathon/skydb/onboard"><strong>Gitcoin</strong></a><strong>, and lasts for three weeks until November 23. Here’s how to get started:</strong></p><ol><li><a href="https://gitcoin.co/hackathon/skydb/onboard">Register for the hackathon</a></li><li><a href="https://chat.idx.xyz/">Hop into the IDX Discord</a> and the <a href="https://discord.gg/sia">Sia Discord</a> for help or to share what you’re working on. We’re more than happy to help discuss your IDX integration with SkyDB.</li></ol><h3>Build apps on a next-gen Web3 stack</h3><p><a href="https://blog.sia.tech/skydb-a-mutable-database-for-the-decentralized-web-7170beeaa985"><strong>SkyDB</strong></a> is a decentralized database system built on <a href="https://siasky.net/">Sia</a> and <a href="https://medium.com/3box/idx-a-devkit-for-open-identity-48edc88e8e85"><strong>IDX</strong></a> is a decentralized identity system built on <a href="https://ceramic.network/">Ceramic</a>. By combining these two technologies, developers can easily build full-stack, data-rich applications that give users direct control and full ownership over their information — all without running servers or siloing information to a particular key pair, application, or database technology.</p><h4>SkyDB: A mutable DB for dweb apps</h4><p>The SkyDB database allows developers to build any feature that requires a decentralized, mutable key-value store. Being able to store user and/or application data in a mutable but decentralized way opens up a world of new possibilities for dweb applications. You can use it to store user-generated content, files, media, application state, or any other type of dynamic information without worrying about managing one-off skylinks for each individual content update. For a quick-start intro to SkyDB, check out this blog post which makes a simple Skynet app that uses SkyDB.</p><p><a href="https://blog.sia.tech/skydb-example-a-note-to-self-app-ccd4e7ba31ba">SkyDB Example: A Note-to-Self App</a></p><h4>IDX: An open identity system for dweb apps</h4><p>The IDX identity framework allows you to tap into a universal decentralized identity layer that makes user and data management for your dweb app much more open and powerful. IDX provides a universal cross-platform identity (DID) for users that can be used everywhere across the Web3 ecosystem, a way to store/access public metadata such as profiles and social graphs, a way to associate your app’s data storage systems (i.e. SkyDB) to the user’s identity, a way to discover and import available third-party data sources for the user (even ones outside of the SkyDB ecosystem such as Filecoin files, TextileDBs, OrbitDBs, and much more!), and a way to publish schemas for your data so that others might easily make use of your application data within another application or context.</p><p>By design, IDX is completely agnostic as to which wallet users authenticate with and which backend configuration you choose to build with —<em> including any blockchain and data storage system</em> — so it easily integrates into the rest of your stack and allows you to build truly cross-platform interoperable applications. You can save data wherever you choose, and import data from other applications that may even be outside of the SkyDB ecosystem!</p><p><a href="https://medium.com/3box/idx-a-devkit-for-open-identity-48edc88e8e85">IDX: A Devkit for Open Identity</a></p><p>// <em>Good luck to all the hackers! Don’t forget to register for the hackathon now — </em><a href="https://gitcoin.co/hackathon/skydb/onboard"><strong><em>https://gitcoin.co/hackathon/skydb/onboard</em></strong></a><em>. Also, </em><strong><em>j</em></strong><a href="https://chat.idx.xyz/"><strong><em>oin the IDX Discord</em></strong></a><em> and </em><a href="https://discord.gg/sia"><strong><em>Sia Discord</em></strong></a><em> for help or questions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83eff179a9a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ceramic/idx-and-skydb-joins-forces-for-a-future-of-web3-hackathon-83eff179a9a1">IDX and SkyDB joins forces for a future of Web3 hackathon</a> was originally published in <a href="https://medium.com/ceramic">Ceramic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IDX: A Devkit for Open Identity]]></title>
            <link>https://medium.com/3box/idx-a-devkit-for-open-identity-48edc88e8e85?source=rss-fc3b0ec804e------2</link>
            <guid isPermaLink="false">https://medium.com/p/48edc88e8e85</guid>
            <category><![CDATA[idx]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[ceramics]]></category>
            <category><![CDATA[did]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Michael Sena]]></dc:creator>
            <pubDate>Fri, 23 Oct 2020 13:29:56 GMT</pubDate>
            <atom:updated>2020-10-28T00:27:17.548Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*na2QrrjwKCpeMMUTYA81mg.png" /></figure><h4>The future of Web3 identity has arrived</h4><p><a href="https://idx.xyz/"><strong>IDX</strong></a> is a brand new SDK for building with decentralized identity and user-centric data from the 3Box Labs team. <em>IDX is in alpha but if you’d like to start experimenting,</em><strong><em> </em></strong><a href="https://chat.idx.xyz/"><strong><em>join our discord</em></strong></a><em> and jump into the </em><a href="https://idx.xyz/docs"><strong><em>docs</em></strong></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wkxWqeHkbA2LAVamrH-ubA.png" /></figure><h3>A new era for Web3 development</h3><p>The Web3 vision for an internet that is open and interoperable, where users control their information requires a decentralized, cross-platform identity system. To this end, IDX is an open source JavaScript/TypeScript library that exposes high-level developer APIs to various meta-protocols and standards for decentralized identity. Not only is IDX powerful and flexible enough to meet all of your user and data management needs, but it wraps everything in an easy-to-use package that makes decentralized identity accessible to all Web3 developers.</p><p>Designed to be cross-platform and highly configurable, IDX is compatible with all blockchains, wallets, and a wide variety of user and application data storage options including <a href="https://ceramic.network/">Ceramic</a>, <a href="https://textile.io/">Textile</a>, <a href="https://orbitdb.org/">OrbitDB</a>, <a href="https://filecoin.io/">Filecoin</a>, <a href="https://ipfs.io/">IPFS</a>, <a href="https://sia.tech/">Sia</a>, and <a href="https://identity.foundation/secure-data-store/">Secure Data Stores</a> — so you can seamlessly integrate decentralized identity with the rest of your Web3 tech stack. With IDX, developers can now build much more sophisticated and powerful Web3 applications that rival and even exceed what’s currently possible on Web2.</p><h3>Why decentralized identity?</h3><p>If you’ve ever asked yourself any of these questions, then you should definitely consider adding a decentralized identity system to your development stack.</p><ul><li>How can I create a <strong>universal identifier</strong> to associate data resources from a variety of platforms to a single user?</li><li>How can I improve my user experience with <strong>decentralized social profiles</strong>?</li><li>How can users create a <strong>unified Web3 identity that links many different accounts</strong> within and across various blockchain platforms?</li><li>How can users <strong>establish trust and reputation</strong> by connecting their Web3 identity to existing Web2 social accounts (i.e. Twitter), various anti-sybil systems (i.e. <a href="https://brightid.org/">BrightID</a>), domain names (i.e. DNS, <a href="https://ens.domains/">ENS</a>, <a href="https://handshake.org/">Handshake</a>), and identity verification services (i.e. KYC)?</li><li>How can users create a universal and portable <strong>social graph</strong> of followers, friends, and contacts?</li><li>How can I <strong>store user and application data in various centralized and decentralized data storage technologies</strong> in a way that isn’t siloed to my application, gives users ultimate control and portability over their data, and works with all of their existing wallets/accounts?</li><li>How do I <strong>discover and import data</strong> that a user has created on another application, platform, or network so that I can use it inside my app?</li></ul><h3>IDX: An open identity framework for Web3</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*erbL1qHL2mPTMF31f0K33A.png" /></figure><p>Decentralized identity and user-centric data management are complex, broad-ranging capabilities that touch almost every other aspect of your app architecture. IDX removes the all of the guesswork from implementing these in a scalable and future-proof way.</p><h4>Build with unified digital identities</h4><p>Using IDX, all applications can access a shared, globally-available identity layer that contains unified users identities. Built 100% on permissionless protocols, IDX enables users and their most important information to seamlessly flow and interoperate across platforms, while giving users the ownership and control they demand. In a way, the identity capabilities offered by IDX sort of function as a decentralized Keybase but with much greater flexibility and decentralization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IAhm-w54MKOPVCj55HV0uA.png" /><figcaption>A unified digital footprint!</figcaption></figure><p>The core of each identity consists of a <a href="https://www.w3.org/TR/did-core/">decentralized identifier (DID)</a> which acts as a globally-unique ID and an <a href="https://github.com/ceramicnetwork/CIP/blob/cip/idx/CIPs/CIP-11/CIP-11.md">identity index</a> which keeps track of an identity’s information. IDX allows developers to deploy identities as well as create, read, update, and delete a variety of metadata and information related to the identity, including but not limited to:</p><ul><li>Multiple user profiles for different contexts or applications</li><li>Portable social graphs, from followers to contacts and family</li><li>Links to multiple blockchain accounts from different protocols (Ethereum, Bitcoin, Polkadot, NEAR, Flow, etc)</li><li>Links to existing social accounts (Twitter, Github, Discord, Matrix, etc)</li><li>Links to domain names (DNS, ENS, Unstoppable, Handshake, etc)</li></ul><p>All DIDs, identity indexes, and metadata are securely stored on Ceramic’s permissionless document management network. Because all information is publicly available (but optionally encrypted) and linked via the identity index, any bit of information can be cross-resolved by querying based on any other information. For example you could lookup a user’s profile based on their DID, their Ethereum account, or their Twitter handle; or you could lookup a user’s Filecoin account based on their Polkadot account. We are working with <a href="https://thegraph.com/">The Graph</a> on indexing these identity structures which will open up many new opportunities in this realm.</p><h4>Integrate with data storage solutions</h4><p>Unified identities are the gateway to a world of additional functionality for your application. If you also need a way of storing and managing user data, you have three main options.</p><ul><li>Use the IDX library to <em>directly</em> store documents on the Ceramic Network and add references to those documents in the user’s index. For this option, no additional software is needed; it works out of the box with IDX.</li><li>Store data in alternative data storage systems such as Filecoin, IPFS, Sia, Arweave, Textile, OrbitDB, Secure Data Stores, or Ethereum contracts and use IDX to add references to this data in your user’s index. For this option, you would need to separately install these technologies in your app alongside IDX.</li><li>Use a combination of the different data storage solutions above for your application, each with their own strengths and weaknesses, while mapping everything in your user’s IDX.</li></ul><p>Whichever data storage configuration you choose, IDX allows all data to be controlled by the user, discoverable by others, and portable across platforms. This is true regardless of where the data resides (servers or decentralized networks) or which application first created the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5IFFJ3sG-BARmU9-7dZhA.png" /><figcaption>The identity index contains mappings to various data sources</figcaption></figure><h4>Share data across applications and silos</h4><p>As described above, the key aspect of IDX that de-silos information, promotes interoperability, and enables user control is the identity index. It provides a standard interface which allows any application or developer to set and query all available data that belongs to a user so that they might make use of it within their application. The identity index serves as the information root for each user and makes everything discoverable.</p><p>To further promote interoperability, the identity index allows developers to:</p><ul><li>Publish schemas, names, and descriptions for data points they are adding to the index, so others can more easily consume this information</li><li>Publish endpoints for where this information can be found, whether a DocID on Ceramic, a CID on IPFS/Filecoin, a contract on Ethereum, or an endpoint for a hosted service</li><li>Request permission to access encrypted data points in the index</li></ul><h3>Developing with IDX</h3><p>The following section outlines how to get started building with IDX. For more supporting materials, <a href="https://idx.xyz/docs"><strong>read the docs</strong></a>.</p><h4>Installation</h4><p>First, we’ll need to install the main IDX library and associated dependencies:</p><pre>npm install @ceramicnetwork/ceramic-http-client @ceramicstudio/idx @ceramicstudio/idx-constants</pre><h4>Query an identity</h4><p>Then we can use these libraries to connect IDX to a Ceramic network and interact with the documents associated to a given DID. This example shows how to simply query the basic profile for a given user.</p><pre>import Ceramic from &#39;@ceramicnetwork/ceramic-http-client&#39;<br>import { IDX } from &#39;@ceramicstudio/idx&#39;<br>import { definitions } from &#39;@ceramicstudio/idx-constants&#39;</pre><pre>// Use Ceramic devnet<br>const ceramic = new Ceramic(&#39;&lt;https://ceramic.3boxlabs.com&gt;&#39;)</pre><pre>// Use IDX-provided definitions aliases<br>const idx = new IDX({ ceramic, definitions })</pre><pre>// Get the basic profile of a known DID supporting IDX<br>async function getProfile(did) {<br>  return await idx.get(&#39;basicProfile&#39;, did)<br>}</pre><h4>Save data</h4><p>More advanced examples involving authentication and setting content can be found in the <a href="https://idx.xyz/docs/guide-authentication"><strong>IDX documentation</strong></a>.</p><p><em>Remember, IDX is still in alpha. If you have any questions, comments, or feedback on what we’ve built or how to use it, please </em><a href="https://chat.idx.xyz/"><strong><em>reach out on Discord</em></strong></a><em>.</em></p><h3>About</h3><p>IDX is an open source library that is built and maintained with 💜 by the 3Box Labs team, creators of <a href="https://github.com/3box/3box-js">3Box.js</a>, a leading decentralized identity and data storage solution for Ethereum that has been used by 30,000+ users and 1,000+ projects. IDX is a smarter, mature evolution of 3Box.js. All DIDs and profiles created using 3Box.js will be automatically migrated to IDX once the library goes into production. We are working on various solutions to migrate user data that has been saved in spaces and threads to other IDX compatible data storage systems including Ceramic, Textile, and OrbitDB. If you have questions about this migration process or timeline, please reach out.</p><h3>Resources</h3><p><a href="https://idx.xyz/"><strong>Website</strong></a><strong><br></strong><a href="https://idx.xyz/docs"><strong>Docs</strong></a><strong><br></strong><a href="https://chat.idx.xyz/"><strong>Discord</strong></a><strong><br></strong><a href="https://github.com/ceramicstudio/js-idx"><strong>Github</strong></a><strong><br></strong><a href="https://twitter.com/identityindex"><strong>Twitter</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48edc88e8e85" width="1" height="1" alt=""><hr><p><a href="https://medium.com/3box/idx-a-devkit-for-open-identity-48edc88e8e85">IDX: A Devkit for Open Identity</a> was originally published in <a href="https://medium.com/3box">3Box Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Identity Index?]]></title>
            <link>https://medium.com/@msena/what-is-identity-index-d3594b59633e?source=rss-fc3b0ec804e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3594b59633e</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[ceramics]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[standards]]></category>
            <category><![CDATA[identity-management]]></category>
            <dc:creator><![CDATA[Michael Sena]]></dc:creator>
            <pubDate>Tue, 28 Jul 2020 14:02:57 GMT</pubDate>
            <atom:updated>2020-07-28T14:02:57.301Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*felRDfYfnoeWw6ahZPSegA.jpeg" /></figure><h4>IDX is an evolution in decentralized identity.</h4><p><a href="https://github.com/ceramicnetwork/CIP/issues/3"><em>Identity Index (IDX)</em></a><em> is an effort to propose a standard for creating a unified, identity-centric index of resources. IDX is the missing component needed to deliver the vision of a truly user-centric web. If you would like to participate and help evolve the standard, join the conversation at the link above.</em></p><h3>Background</h3><p>Over the last 4+ years of working in Web3, I’ve been involved in various decentralized identity projects and initiatives including <a href="http://github.com/ceramicnetwork">Ceramic</a>, <a href="http://3box.io/">3Box</a>, <a href="http://uport.me/">uPort</a>, and the <a href="http://identity.foundation/">Decentralized Identity Foundation</a>. Every product I’ve built has always relied on <a href="https://w3c.github.io/did-core/">DIDs</a>, given users control of their data, and sought to enable a re-architecture of the web around users instead of platforms.</p><p>However, one thing has become immensely clear. <em>Decentralized identity has a glaring problem.</em></p><h3>The missing piece</h3><p><a href="https://w3c.github.io/did-core/">DIDs</a> are the W3C standard for globally-unique decentralized identifiers that commonly identify an entity across the web. A DID is the minimum requirement for establishing an interoperable, platform-agnostic digital identity. However, a digital identity is much more than a decentralized identifier.</p><p>An identity is the complete set of resources that give context and capability to a DID including all of its keys, accounts, profiles, social graphs, data, settings, services, and more. Oftentimes, these resources are scattered across the web on many different centralized platforms (application servers) and decentralized networks such as 3Box, Ceramic, Textile, Ethereum, IPFS, Arweave, and others.</p><p>Decentralized identity depends on the ability for users to bring their identifier and resources to an application, as opposed to the current “Web2” paradigm of applications and platforms controlling identities and data. However to date, this has not been possible.</p><p>Currently there is no standardized and decentralized way of associating resources to a DID. This limits an application’s ability to permissionlessly query, discover, and resolve a DID’s many resources. In turn, this limits the value of decentralized identities. We believe this is one of the reasons “Web3” has not realized its full potential.</p><h3>What is Identity Index?</h3><p><a href="https://github.com/ceramicnetwork/CIP/issues/3">Identity Index (IDX) (CIP-11)</a> is a standard for constructing a unified, identity-centric index of resources. IDX is decentralized, cross-platform, and DID-agnostic <em>so it can be used by any DID, to map to any resources, on any platforms.</em></p><p><a href="https://github.com/ceramicnetwork/CIP/issues/3">Identity Index (IDX) · Issue #3 · ceramicnetwork/CIP</a></p><p>By standardizing how resources are associated to a DID, IDX solves discovery, routing, and resolution. This enables any app to lookup a DID and seamlessly interact with its resources regardless of where they exist or which application first created the data. As a result, IDX can unlock true identity-centric interoperability across the web.</p><h3>How does it work?</h3><p>IDX achieves this by specifying a top-level resource directory, called the Root Index (CIP-12), which links to various subdirectories including a:</p><ul><li>Profiles Index (CIP-13): contains links to a DID’s profiles (i.e. basic, work)</li><li>Keychains Index (CIP-15): contains links to a DID’s keychains (i.e. auth)</li><li>Accounts Index (CIP-14): contains links to a DID’s accounts (i.e. crypto, social, domains)</li><li>Connections Index (CIP-18): contains links to a DID’s social connections (i.e. follows)</li><li>Collections Index (CIP-16): contains links to a DID’s data collections (i.e. app data)</li><li>Services Index (CIP-17): contains links to a DID’s services (i.e. notifications or backup)</li><li>Settings Index (CIP-24): contains links to a DID’s settings documents (i.e. internationalization)</li><li>and more…</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*ofnHIfX-cclOVMbnnen1dg.jpeg" /></figure><h3>Motivation &amp; Goals</h3><p>The motivation for specifying the IDX standard is as follows:</p><ul><li>Elevate DIDs into complete identities with the full set of resources and capabilities needed to be broadly useful</li><li>Provide a DID-centric framework for indexing resources that is flexible, extensible, decentralized, cross-platform, and DID-agnostic</li><li>Simplify resource discovery and routing, wherever resources may exist (centralized servers, decentralized networks, etc)</li><li>Provide a standard interface for developers to use when interacting with any DID</li><li>Enable DIDs to easily integrate with other technologies, networks, platforms, and wallets</li><li>Make it easy to build with decentralized identities</li></ul><h3>Join us</h3><p>IDX currently exists as a draft of a specification that will continue to evolve over the coming days, weeks, and months with your feedback. We’d love to have you join us on this journey. Here are some resources to get started.</p><ul><li>Contribute on Github: <a href="https://github.com/ceramicnetwork/CIP/issues/3">Identity Index (CIP-11)</a></li><li>Join the <a href="https://github.com/ceramicnetwork/CEA#join-the-cea">Identity Working Group</a></li><li>Follow on Twitter: <a href="http://twitter.com/identityindex">@identityindex</a></li></ul><p><em>Special thanks to those who have already contributed in various ways.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3594b59633e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ceramic Improvement Proposals]]></title>
            <link>https://medium.com/ceramic/ceramic-improvement-proposals-40154fa65845?source=rss-fc3b0ec804e------2</link>
            <guid isPermaLink="false">https://medium.com/p/40154fa65845</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[ceramic-network]]></category>
            <dc:creator><![CDATA[Michael Sena]]></dc:creator>
            <pubDate>Wed, 15 Jul 2020 16:49:33 GMT</pubDate>
            <atom:updated>2020-07-15T16:49:33.734Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Owck3frZLEkc8WKqwINDGg.png" /></figure><h4>CIPs give you the power to shape the Ceramic network</h4><p><a href="http://github.com/ceramicnetwork"><em>Ceramic</em></a><em> is a permissionless protocol and decentralized network for smart documents that is currently in pre-alpha testnet.</em></p><p>Decentralization, community, and open source are core to the vision of Ceramic. Although the network is still in its infancy, we’re already taking steps to decentralize control over where the platform is headed and giving it to you— the community.</p><h3>Introducing, Ceramic Improvement Proposals</h3><p>We’re excited to introduce the <a href="http://github.com/ceramicnetwork/cip"><strong>Ceramic Improvement Proposal (CIP)</strong></a><strong> </strong>framework, along with a set of supporting processes, as a way for the community to have control in shaping the future of the network.</p><p>If you’re familiar with popular open source languages (Python) or decentralized networks (Bitcoin, Ethereum), then you likely already understand what CIPs are all about.</p><p>For those that aren’t, CIPs allow anyone to propose improvements to the Ceramic network across a range of dimensions — from core protocol specifications to doctypes, schemas, use case standards, and meta process improvements. All of this takes place in the open on Github issues and pull requests in the <a href="http://github.com/ceramicnetwork/cip"><strong>Ceramic CIP repo</strong></a>.</p><p><a href="http://github.com/ceramicnetwork/cip">GitHub - ceramicnetwork/CIP: The Ceramic Improvement Proposal repository</a></p><p>From start to finish, the entire CIP process is 100% community-driven and open source. Anyone is free to create a new CIP, input on the CIPs of others, advocate for their standard, or whatever else you would like to do. All we ask is that you follow the process outlined in <a href="https://github.com/ceramicnetwork/CIP/blob/master/CIPs/CIP-1/CIP-1.md"><strong>CIP-1</strong></a>.</p><h3>Motivation</h3><p>Here are some of the reasons why Ceramic needs a CIP process:</p><ul><li>To define an explicit governance process for Ceramic network upgrades</li><li>To make it easy for community members to contribute to the development of the protocol and its standards</li><li>To provide a way for developers to discover existing implementation standards accepted by the community when building their product</li><li>To provide a historical record of how and why things changed over time</li><li>To provide a vehicle for community discussion around important topics</li><li>To remove any individual or group of individuals as gatekeepers to the Ceramic network</li></ul><h3>Get Involved</h3><p>The entire CIP process is outlined in <a href="https://github.com/ceramicnetwork/CIP/blob/master/CIPs/CIP-1/CIP-1.md">CIP-1</a>. To create a new CIP, <a href="https://github.com/ceramicnetwork/CIP/issues/new?assignees=&amp;labels=&amp;template=new-cip.md&amp;title=">open an issue</a>.</p><p>Additionally, the CIP framework has a few supporting processes:</p><ul><li><strong>Community Calls</strong>: Tri-weekly video calls where the Ceramic community convenes to discuss things that are important and relevant, including CIPs. Add the community call calendar <a href="https://calendar.google.com/calendar/b/3?cid=Y2VyYW1pYy5uZXR3b3JrX3JsNzFrcXZtNzE4ZGY4aWk2cDZzanNmbDdjQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20"><strong>here</strong></a>.</li><li><strong>Core Devs Calls</strong>: Tri-weekly video calls where the Ceramic developer community convenes to discuss the core protocol and network, including CIPs that could potentially be included in a future network upgrade. Add the core devs call calendar <a href="https://calendar.google.com/calendar/b/3?cid=Y2VyYW1pYy5uZXR3b3JrX3JsNzFrcXZtNzE4ZGY4aWk2cDZzanNmbDdjQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20"><strong>here</strong></a>.</li><li><strong>Working Groups</strong>: Community-organized working groups where contributors and interested individuals meet to tackle specific challenges, such as collaborating on one or more CIPs that solve a specific issue. Working groups offer more dedicated space to collaborate beyond Github issue comments. Working groups are organized as part of the Ceramic Ecosystem Alliance. To join or start a working group, <a href="https://github.com/ceramicnetwork/cea#join-the-cea"><strong>join the CEA</strong></a>.</li></ul><p>See you in the <a href="http://github.com/ceramicnetwork/cip">CIP repo</a> and on the <a href="https://discord.gg/5CZzG7V">Ceramic Discord</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40154fa65845" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ceramic/ceramic-improvement-proposals-40154fa65845">Ceramic Improvement Proposals</a> was originally published in <a href="https://medium.com/ceramic">Ceramic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hack with 3Box at HackFS ]]></title>
            <link>https://medium.com/3box/hack-with-3box-at-hackfs-9bff5f298ff?source=rss-fc3b0ec804e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bff5f298ff</guid>
            <category><![CDATA[ipfs]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[3box]]></category>
            <dc:creator><![CDATA[Michael Sena]]></dc:creator>
            <pubDate>Thu, 09 Jul 2020 13:51:46 GMT</pubDate>
            <atom:updated>2020-07-09T13:51:46.976Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_lAvSima2F-VbFQuMvEL7Q.png" /></figure><h4>We’re giving away more than 3,000 DAI in prizes!</h4><p><em>We’re excited to announce that </em><a href="http://3box.io/"><em>3Box</em></a><em> is a proud sponsor of the </em><a href="http://hackfs.com/"><em>HackFS</em></a><em> hackathon along with other amazing sponsors like Protocol Labs, the Ethereum Foundation, Consensys, Textile, and others. 3Box is offering three bounties worth a total of more than 3,000 DAI in prizes! Read more below.</em></p><h4>What is HackFS?</h4><p>HackFS is a month-long hackathon run by <a href="https://ethglobal.co/">ETHGlobal</a> and <a href="http://protocol.ai/">Protocol Labs</a> dedicated to realizing the vision of Web3 by encouraging hackers to build projects that combine blockchains (such as Ethereum), linked data (IPFS), and p2p storage (such as OrbitDB). 3Box uses all three of these technologies and so is a great fit for anyone looking to hack on a new project.</p><h4>Details</h4><p>Sign up: <a href="http://hackfs.com/">hackfs.com</a><br>Dates: July 6 — Aug 6, 2020</p><h3>3Box Bounties</h3><p>As a sponsor of the hackathon, we get to offer prizes to developers for building with 3Box’s technology.</p><p><strong>About 3Box:</strong> <a href="http://3box.io/">3Box</a> is the leading platform for decentralized identity, profiles, databases, and messaging that helps Web3 developers build amazing applications.</p><h4>1. Best Overall Use of 3Box</h4><p>Builders choice! Create something truly awesome using 3Box and surprise us with your creativity. For this bounty you can create a new project that uses 3Box, or integrate 3Box into an existing project.</p><p>3Box offers a <a href="https://www.notion.so/threebox/HackFS-3Box-Bounties-e2c1f618095d4c92b25ef8afe646988b#751dee5b6c7d46919c81d361142f1289">JavaScript SDK</a> that delivers everything you need to get going in a single, easy-to-use library. 3Box also offers <a href="https://www.notion.so/threebox/HackFS-3Box-Bounties-e2c1f618095d4c92b25ef8afe646988b#751dee5b6c7d46919c81d361142f1289">plugins</a> that make it easy to add various 3Box-powered functionalities, such as profile hovers, comments, or trollboxes, into to any React app.</p><p><strong>Prize: </strong>1,000 DAI</p><p><a href="https://www.notion.so/threebox/HackFS-3Box-Ceramic-Bounties-e2c1f618095d4c92b25ef8afe646988b#d2d541b563af4d9bb04d330f3f1202e2">Learn more</a></p><h4>2. Interoperable #Defi Chat Platform</h4><p>Create a home for discussions about DeFi protocols and take the DeFi ecosystem to the next level! This bounty is to create a completely decentralized platform for discussing DeFi protocols that can be used across every DeFi interface. Contribute a massive value-add to the thriving DeFi ecosystem.</p><p>The goals of this bounty are to:</p><ol><li>Create a standalone DeFi chat application (name idea: DeFi Talk!) using the <a href="https://docs.3box.io/build/web-apps/messaging/ghost-threads">3Box Ghost Threads API</a></li><li>Integrate chatrooms into 2+ existing DeFi interfaces (i.e. Zerion, Instadapp, DeFi Market Cap, DEXs, etc) using the <a href="https://docs.3box.io/build/plugins/chatbox">3Box Chatbox plugin</a></li></ol><p>3Box offers a <a href="https://www.notion.so/threebox/HackFS-3Box-Bounties-e2c1f618095d4c92b25ef8afe646988b#380562285564485b8d15447509d75a2f">Ghost Threads API</a> that allows developers to create highly-scalable p2p, decentralized chatrooms that are decoupled from any single interface. 3Box also has a Chatbox Plugin which is a simple way to drop Ghost Threads chatrooms into any react app.</p><p><strong>Prize: </strong>1,500 DAI</p><p><a href="https://www.notion.so/threebox/HackFS-3Box-Ceramic-Bounties-e2c1f618095d4c92b25ef8afe646988b#763b5316702549aa8759ce28fe2a17ab">Learn more</a></p><h4>3. Ethereum Leaderboard (Yield Farming, Dapp Usage, and more!)</h4><p>Gamify the DeFi and dapp ecosystem! Create a leaderboard of Ethereum users based on usage of certain apps and protocols.</p><p>3Box offers a <a href="https://docs.3box.io/build/web-apps/profiles">Profiles API </a>that allows developers to create populate their application with rich social user profiles. This API is great for creating delightful and engaging leaderboards. There are already more than 22,000 profiles created!</p><p><strong>Prize: </strong>1,000 DAI</p><p><a href="https://www.notion.so/threebox/HackFS-3Box-Ceramic-Bounties-e2c1f618095d4c92b25ef8afe646988b#12b075b49c874969bbca702a18cb2141">Learn more</a></p><h4>4. Create a new doctype for Ceramic Network</h4><p>Contribute to early development of the <a href="http://ceramic.network/">Ceramic Network</a> by expanding what’s possible! This bounty is for creating a new doctype that can run on the protocol. Doctypes are the primitives that define content requirements and state transition rules for documents published on the network. You can read the general doctype specification <a href="https://github.com/ceramicnetwork/CIP/issues/37">here</a>.</p><p>You can create any doctype you’d like but if you need help getting started, a Verifiable Claims doctype that complies with the <a href="https://www.w3.org/TR/vc-data-model/">W3C Verifiable Claims</a> standard would be awesome! Some examples of existing doctypes include: <a href="https://github.com/ceramicnetwork/specs/blob/master/doctypes/3id.md">3ID</a>, <a href="https://github.com/ceramicnetwork/specs/blob/master/doctypes/account-link.md">Account Link</a>, and <a href="https://github.com/ceramicnetwork/specs/blob/master/doctypes/tile.md">Tile</a>.</p><p><strong>About Ceramic: </strong>Ceramic is a cross-platform information graph that allows DIDs to publish unstoppable content in the form of mutable documents. Each document on the network essentially forms its own doc-chain (of updates) and has it’s own verifiable state. Ceramic network uses DIDs to sign messages and author content, doctypes to define document rules, IPFS (IPLD) to store content, and blockchains (or Filecoin) to anchor updates. Each document gets a permalink in the form of ceramic://bafy.... <em>Ceramic is currenly in early alpha testnet. We will have a fully-functional testnet live in a month or so.</em></p><p><strong>Prize: </strong>500 DAI<br><strong>Questions &amp; Support:</strong> Join <a href="https://discord.gg/bt5yPMa">Ceramic Discord</a><br><strong>Docs:</strong> <a href="https://www.notion.so/threebox/HackFS-2022b67e249540a5a7fc5009701ee09f#c7ef133fb7e34583a9fe64566c330ade">Doctype specification guidelines</a>, <a href="https://github.com/ceramicnetwork/specs">Ceramic Specs</a>, <a href="https://github.com/ceramicnetwork/js-ceramic">js-ceramic</a></p><p><a href="https://www.notion.so/threebox/HackFS-3Box-Ceramic-Bounties-e2c1f618095d4c92b25ef8afe646988b#9fce9a2a7fea4de9b1db237a9737a068">Learn more</a></p><h3>Happy hacking and good luck to all! 🚀</h3><p>We’re always available for questions or support in the <a href="https://discord.gg/669BQHv">3Box Discord</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bff5f298ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/3box/hack-with-3box-at-hackfs-9bff5f298ff">Hack with 3Box at HackFS 🚀</a> was originally published in <a href="https://medium.com/3box">3Box Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing, 3ID Connect ✨]]></title>
            <link>https://medium.com/3box/introducing-3id-connect-531af4f84d3f?source=rss-fc3b0ec804e------2</link>
            <guid isPermaLink="false">https://medium.com/p/531af4f84d3f</guid>
            <category><![CDATA[3box]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[authentication]]></category>
            <dc:creator><![CDATA[Michael Sena]]></dc:creator>
            <pubDate>Tue, 21 Apr 2020 13:58:00 GMT</pubDate>
            <atom:updated>2020-06-16T14:00:45.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O4gXYrzh5r5X_IHsOPok5A.png" /></figure><h4>A whole new way to onboard 3Box users</h4><p>We’re excited to unveil a whole new interface for onboarding <a href="http://3box.io/">3Box</a> users to your application. <a href="https://github.com/3box/3id-connect"><strong>3ID Connect</strong></a> is the most complete, secure way for apps to authenticate 3Box accounts (identities, profiles, and data stores) controlled by users.</p><p>3ID Connect is an account &amp; key management application run in an iFrame, which is privately controlled by users and can be accessed by wallets and applications during onboarding. The new 3ID Connect flow is very similar to the Oauth consent flows that users have become accustomed to on web2, such as signing into apps with Facebook, Google, Twitter, or Github. However, 3ID Connect provides your application with much more powerful, user-centric identity and data storage capabilities.</p><p>Before 3ID Connect, users didn’t have the most clarity over the permissions they were giving when signing into apps that used 3Box, they needed to endure the inconvenience of signing individual messages for each data consent (sometimes up to 10!), and they were limited to only controlling their 3Box account with a single ethereum key pair.</p><p>This was due to 3Box’s reliance on the personal_sign method in the EthereumProvider API for authentication — including generating identities, signing messages, and storing identity/database keys in localStorage. If you’ve used 3Box or web3 apps before, you’ll recognize this flow; it’s the common wallet signature request.</p><p>Instead, 3ID Connect uses the <a href="http://ceramic.network/">Ceramic Network</a>’s dedicated 3IDProvider (via <a href="https://github.com/3box/identity-wallet-js">IdentityWallet SDK</a>) to deliver a more feature-complete, secure, friendly, and cross-chain experience for 3Box accounts. There are many reasons to love 3ID Connect, but here are some highlights:</p><ul><li>Secure key material 🔐</li><li>Data consent clarity ✅</li><li>Fewer wallet signatures 🔑</li><li>Persistent 3Box sessions 🔁</li><li>Standalone 3ID provider 🆔</li><li>Multi-address support 🔗</li><li>Multi-network support 🕸</li><li>Contract wallet support 🛡</li><li>Ceramic Network compatibility 🔸</li></ul><h3>Get started with 3ID Connect</h3><p>To improve the onboarding flow in your application and get started with 3ID Connect today, you simply need to install the latest version of 3Box.js@1.20.0 or greater.</p><p>Over two releases we will fully migrate to 3ID Connect. The first release of 3Box.js simply imports legacy keys and starts to use a subset of features of 3ID Connect. The second release will fully migrate to the 3ID Connect account model and any apps not using 3ID Connect at this time may lose references to some of their user’s data. Additional details and the planned timeline is as follows.</p><p>⚠️ <em>To avoid any interruption of service or breaking changes in the roll out, we recommend updating your application to use the latest version of </em><em>3Box.js with 3ID Connect enabled as soon as possible. Apps using older versions of </em><em>3Box.js after August 5, 2020 may lose references to some of their user’s data or compatibility across applications.</em> ⚠️</p><h3>1. 3ID Connect Migration [June 16, 2020]</h3><p>3Box.js ^1.20.0: Simply update <em>3Box.js</em> to version 1.20.0 or greater and you will be now using be using 3ID connect. While you don&#39;t need to change any code to support this change, it may be a good time to review any older code and update it to the now suggested flow to reduce load time and user interactions required. Primarily use create and auth instead of openBox, call Box.create as early as possible, and auth to authenticate a user to all spaces needed in one call.</p><pre>// On page load create<br>const box = await Box.create()<br>// Later authenticate user<br>const spaces = [&#39;myDapp&#39;]<br>await box.auth(spaces, { address: &#39;0x12345abcde&#39;, provider: ethProvider })</pre><p>⚠️ <em>An earlier version of this article stated that you had to pass a 3ID Connect Provider Box.get3idConnectProvider() to use 3ID-Connect. This is no longer true and this function will throw an error now. If you made this update in the past, please return to passing an ethereum provider, this will be wrapped in a 3ID Connect Provider in the background, and will allow control over which providers are used to be returned to the app developer. We decided to make this change after much feedback from the first 3ID Connect users. This change and refactor also pushed the upgrade timeline. Originally May 26, 2020 was stated as the breaking date, this has been pushed to August 5, 2020. </em>⚠️</p><h3>3. 3ID Connect [August 5, 2020]</h3><p>No codes changes or upgrades needed. At this point you need to be using 3Box.js@1.20.0 or greater. On August 5, we will release a 3ID Connect update that will fully migrate users to the new account model. After a user migrates, their account will not be fully compatible with apps using an older version of 3Box.js and references to any new data created in these apps may be lost.</p><h3>Improved Security</h3><h4><strong>Secure key material 🔐</strong></h4><p>3ID Connect stores a user’s 3ID identity and database keys in an iFrame application hosted on the 3Box domain (connect.3box.io) instead of in browser localStorage.</p><p>Apps that integrate with 3Box request to perform signing and encryption operations with these keys, but they never leave the iFrame. This model is <em>risk minimizing</em> since apps no longer have unrestricted access to keys at any time.</p><h3>Simplicity &amp; User Experience</h3><h4><strong>Data consent clarity ✅</strong></h4><p>3ID Connect gives users ultimate clarity over the data permissions that applications are requesting so that users have more control. These permissions are described to users in the 3ID Connect modal.</p><h4><strong>Fewer wallet signatures 🔑</strong></h4><p>3ID Connect uses an HD trie to derive database keys for 3Box spaces from the user’s 3ID, so users only need to sign one message to consent to all permissions requested by an application instead of signing one message for each individual permission.</p><h4><strong>Persistent 3Box sessions 🔁</strong></h4><p>3ID Connect allows users to persist 3Box sessions across application browser tabs, eliminating the need for users to sign into each individual tab.</p><h3>Flexibility &amp; Extensibility ⚡️</h3><h4><strong>Standalone 3ID provider 🆔</strong></h4><p>3ID Connect can act as a standalone identity (DID) and data management wallet provider for pure dweb apps that don’t need blockchain.</p><h4><strong>Multi-address support 🔗</strong></h4><p>In time, 3ID Connect will support the ability for users to link multiple cryptographic addresses to their 3ID. This allows users to control their 3ID (and 3Box account) from multiple wallet accounts.</p><h4><strong>Multi-network support 🕸</strong></h4><p>3ID Connect makes it possible to add support for blockchain networks beyond just Ethereum in the 3ID Identity Provider. This allows a 3ID identity to use its profile, 3Box, and other data across many different platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Mu6fC-Tsai-gax4ocR30A.png" /><figcaption>Support any blockchain!</figcaption></figure><h4><strong>Contract wallet support 🛡</strong></h4><p>3ID Connect makes it easy for contract wallet providers on Ethereum and other blockchains to add support for their wallet in the 3ID identity provider. This allows users to control their 3Box data from any key associated with their contract.</p><h4><strong>Ceramic Network Compatibility 🔸</strong></h4><p>3ID is a web3-native DID method provided by the <a href="http://ceramic.network/">Ceramic Network</a>. 3IDs live on IPFS and give users full control, flexibility, and interoperability of their identity, profile, data, and resources across the entire web3 ecosystem — including across all wallets and blockchains and regardless of which key they use or which network they’re on.</p><h3>Future Improvements</h3><h4><strong>Decentralized Hosting</strong></h4><p>In the future, we will further improve security of user keys by hosting the 3ID Connect iFrame on a distributed storage network such as ENS+IPFS/Filecoin or Arweave.</p><h4>How to add new blockchains (Blog post)</h4><p>Soon we will publish a follow-up blog post on this topic, but if you’re interested in adding support for additional blockchains, drop in the <a href="https://discord.gg/Tg4FAJS">3Box Discord</a> and ask us how!</p><h4>How to add new contract wallets (Blog post)</h4><p>Soon we will publish a follow-up blog post on this topic, but if you’re interested in adding support for your contract wallet, drop in the <a href="https://discord.gg/Tg4FAJS">3Box Discord</a> and ask us how!</p><h4>And more…</h4><p>Hop in the <a href="https://discord.gg/669BQHv">3Box Discord</a> to ask us more about what’s coming next! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=531af4f84d3f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/3box/introducing-3id-connect-531af4f84d3f">Introducing, 3ID Connect ✨</a> was originally published in <a href="https://medium.com/3box">3Box Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to the Ceramic Protocol]]></title>
            <link>https://medium.com/ceramic/introduction-to-the-ceramic-protocol-8d56951ae3f?source=rss-fc3b0ec804e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d56951ae3f</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[protocol]]></category>
            <category><![CDATA[ipfs]]></category>
            <category><![CDATA[ceramics]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Michael Sena]]></dc:creator>
            <pubDate>Tue, 24 Mar 2020 13:12:54 GMT</pubDate>
            <atom:updated>2020-03-24T13:12:54.461Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qwKHGzf8EurXx4Ow6JIlEA.png" /></figure><h4>The protocol for a connected, interoperable web</h4><h3>Connecting a web without silos</h3><p>This post introduces <a href="http://ceramic.network/">Ceramic</a>, a new permissionless protocol for creating and accessing unstoppable documents that serve as the foundation for a connected, interoperable web without silos. Ceramic is ideal for storing information that requires guaranteed trust, cross-platform interoperability, and multi-party consumption.</p><p>Because participants can create and resolve documents for any type of information without any centralized service, Ceramic <em>unlocks information interoperability between all platforms and services across the web.</em></p><p>Although Ceramic can be used to store any kind of signed information, it is well-suited as a universal routing layer for storing decentralized identifiers (DIDs) and their associated metadata, data schemas, policies for usage of web services, access control permissions, and other documents that collectively enable boundless interoperability between an ecosystem of connected wallets, applications, databases, and services. Here’s what’s possible on Ceramic:</p><ul><li>Portable self-sovereign identity</li><li>Shared data schemas and definitions</li><li>Interoperable user and application data storage</li><li>Open web services, without new accounts or logins</li></ul><p><em>For more information, jump directly to the use cases or examples sections below.</em></p><p>Ceramic’s global ecosystem of interoperable resources allows developers to build composable applications with unprecedented modularity, trust, and scale. As a result, Ceramic is the trusted foundation upon which a more connected, transparent, and user-centric internet is built.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZuX3I8xnHhD2XBGthSAvQQ.png" /></figure><h3>Learn More about Ceramic</h3><p>Continue reading the full Ceramic Overview below, or explore these additional resources:</p><ul><li><a href="https://github.com/ceramicnetwork/specs">Ceramic Technical Specification</a></li><li><a href="https://github.com/ceramicnetwork/js-ceramic">Ceramic JavaScript Client</a></li></ul><h3>Join the Conversation</h3><ul><li><a href="https://discord.gg/6VRZpGP">Join the Discord</a></li><li><a href="https://twitter.com/ceramicnetwork">Follow on Twitter</a></li><li><a href="https://danny765911.typeform.com/to/l7DlvJ">Attend our community call on April 2</a></li><li><a href="https://danny765911.typeform.com/to/yDYZQP">Attend a technical webinar on April 9</a></li></ul><h3>Ceramic Overview</h3><ol><li>Background</li><li>Ceramic Documents</li><li>Ceramic Use Cases</li><li>Ceramic Ecosystem</li><li>Ceramic Ecosystem Alliance</li><li>Ceramic Timeline</li><li>Ceramic Technical Specification</li></ol><h3>1. Background</h3><p>Despite the benefits of cloud services, SaaS tools, and API businesses, building a fully featured product or service is still extremely complex, fragile, and limited. Even simple apps require deploying and maintaining a backend, securing and managing user identities and data, and tying together a tangle of APIs and services. Choices made early often lock developers in to long term relationships with technology providers, which vendors exploit. Making a product’s value-add interoperate with other products and services is often difficult and unpredictable. All of this is because infrastructure, information, and access control are needlessly replicated and siloed for each individual application.</p><p>To combat these problems of duplication, fragmentation, and insecurity, the internet needs a flexible public infrastructure where participants can store verifiable information that is universally discoverable and accessible across all applications. By keeping identifiers, their associated data, and services in the public domain instead of on siloed application servers, they can be accessed by all participants across the web. In this model, participants directly define and control their resources, share (or not) these resources with others, and bring their identities and metadata across experiences.</p><p>In addition to giving users more agency and control, this model dramatically simplifies the experience for developers as well. Instead of spending effort on managing data and tying together various services, developers can focus on the value-add in their product. Each application can simply query an identity for the information and access they need. Data can be easily shared across products without compromising privacy. Experiences can be composed in real-time to a users preferences. Bilateral service signups and agreements can be done away with, replaced instead by frictionless payment channels for services.</p><p>All of this frees products and services from needing to perform non-critical functions, reconciling services and data, worrying about user trust and liability, or scrambling to attract and retain users through many points of friction. Instead, developers can simply build a product that plugs into an already existing ecosystem of users, data, and services that work seamlessly together. Over time, this will result in more targeted micro-services and micro-applications being developed, instead of the behemoths we see today.</p><h4>Requirements</h4><p>The composable web needs a permissionless, identity-centric interoperability protocol to provide applications with all the information they need to easily discover, route to, gain access to, and interact with a user’s resources regardless of which wallet users bring, which applications created the data, or where the resources are located. This protocol must:</p><ol><li>Permissionlessly register an interoperable identity (DID);</li><li>Privately control this identity with multiple private keys;</li><li>Publicly associate public keys and accounts to this identity;</li><li>Publicly or privately associate resources to this identity;</li><li>Set permissions for resources;</li><li>Perform access control to resources;</li><li>Interoperably sign and/or encrypt information; and</li><li>Revoke private keys, public keys, and permissions for resources.</li></ol><p>In addition to these base requirements, a protocol aiming to unlock interoperability should also allow applications and services to:</p><ol><li>Publish metadata and definitions;</li><li>Publish data schemas; and</li><li>Publish policies and service agreements.</li></ol><p>Finally, a solution aiming to make it simpler to build powerful applications must be easy for developers to use. It must fit with existing mental and development models, add no additional burdens, and scale well with new use cases and complexity.</p><h3>2. Ceramic Documents</h3><p>Ceramic provides a <em>universal graph of verifiable documents</em>. Ceramic documents are signed, append-only, tamper-proof objects stored in <a href="https://github.com/ipfs/ipfs">IPFS</a>, encoded using <a href="https://github.com/ipld/ipld">IPLD</a>, and anchored in one or more blockchains. Due to its hybrid design relying on IPFS/IPLD and various blockchains, Ceramic’s document graph is interoperable, scalable, permissionless, and low cost (variable depending on blockchain anchor service).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cDzva42P7lJ9erzNicfPJA.png" /></figure><p>Ceramic documents are a flexible primitive that can be modeled to represent many things, however each document must conform to a specific <em>doctype</em> supported by the protocol. Doctypes specify rules that govern what is a valid update to the document such as signatures and state transitions. This allows Ceramic nodes to verify the state of a given document in a decentralized way.</p><p>Ceramic currently supports three standard <a href="https://github.com/ceramicnetwork/specs#document-types">doctypes</a>: <em>3IDs</em>, <em>account-links</em>, and <em>tiles</em>. Below, find some of the common ways that these doctypes are used. If your use case doesn’t fit into one of these doctypes, you can add new doctypes to the protocol by submitting an issue on the <a href="http://github.com/ceramicnetwork/specs/issues">Ceramic specs</a> repository.</p><p><em>Learn more about </em><a href="https://github.com/ceramicnetwork/specs/blob/master/README.md#protocol-overview"><em>Ceramic documents</em></a><em>.</em></p><h4>Decentralized Identifiers (DIDs)</h4><p>DIDs are globally unique identities used to sign documents on the Ceramic network and also interact with arbitrary off-chain services and data. More specifically, they are abstract, key-agnostic interfaces used to uniquely identify entities, interoperably sign and encrypt information, authorize authentication/access control to services, and store mappings to additional resources. Ceramic makes no assumptions about what kind of entity a DID represents, so they can be users, organizations, applications, services, devices, etc. DIDs can be controlled by one or many private keys, providing flexibility and interoperability across wallets and platforms.</p><p><strong>3ID Identity<br></strong>The first and most widely used DID method on Ceramic is 3ID. More than 15,000 3IDs are already being used in production. Other DID methods that conform to the <a href="https://www.w3.org/TR/did-core/">W3C DID spec</a> may be added to the network as additional doctypes.</p><p><em>Learn more about </em><a href="https://github.com/ceramicnetwork/specs/blob/master/doctypes/3id.md"><em>3IDs</em></a><em> or see an </em><a href="https://github.com/ceramicnetwork/specs/blob/master/doctypes/3id.md#example"><em>example</em></a><em>.</em></p><h4>Account Links</h4><p>Account links are the second doctype supported by Ceramic. Account links are verifiable public mappings that allow a DID to prove that it owns a different public cryptographic identity that is also capable of signing, such as a public key, smart contract, or other DID.</p><p><em>Learn more about </em><a href="https://github.com/ceramicnetwork/specs/blob/master/doctypes/account-link.md"><em>account links</em></a><em>.</em></p><h4>Tiles</h4><p>Tiles, the third doctype supported by Ceramic, are the most general form of a document and can be used to represent almost any kind of information. Tiles are a way to make verifiable statements by one or more DIDs. Tiles may act as standalone objects or they can reference other tiles. This allows for composability between various tiles, creating a relational graph of verifiable, mutable information. See below for a few examples of how tiles will be used on Ceramic.</p><p><em>Learn more about </em><a href="https://github.com/ceramicnetwork/specs/blob/master/doctypes/tile.md"><em>tiles</em></a><em>.</em></p><p><strong>Schemas<br></strong>The first use case for tiles is creating verifiable, globally-available data schemas. Schema tiles allow a user to define a canonical schema that can be used by anyone anywhere in the world, encouraging multiple parties to converge around standard schemas. This makes schema tiles valuable in their own right. Schema tiles are also used to provide structure to information contained in other tiles. Because of this, schema tiles are the core building block for other tiles, such as those below. Schemas tiles can be thought of as templates for other tiles.</p><p><strong>Metadata<br></strong>Tiles are used to express additional metadata or context about Ceramic DIDs. At a minimum, DIDs need a DID Manager tile so they can be controlled by one or more private keys. Other metadata needs will vary depending on the type of entity that a DID represents and the use case.</p><ul><li>DID Manager: Contains information required to allow one or many private keys to control a DID</li><li>Public Profile: Provide context about a DID, such as profile metadata (name, image, logo, etc)</li><li>Identity Link: Allow others to verify that a non-cryptographic identifier is owned by a DID, such as social links (twitter, github, etc) or DNS links</li><li>Resource Link: Allow others to verify that a resource is owned by the DID, such as a data link (data sources, data bases, verifiable claims, registries) or a service link (services, APIs)</li></ul><p><strong>Policies<br></strong>Tiles are used to define more explicit, specific terms around the design of a particular service or the access control requirements and permissions needed to access it. For example, policies can define the data model for an application, terms and requirements of a service, or the permissions set by a user to access their data.</p><ul><li>Collection Policy: Used to define an app’s data model (database types plus references to schema tiles)</li><li>Service Policy: ToS and requirements for using a resource, may include service endpoint and payment info</li><li>Privacy Policy: User-managed access control permissions to their resources</li></ul><p><strong>Agreements<br></strong>Tiles are used to form explicit agreements between DIDs. An example of this would be a Service Agreement, which is a multi-party agreement between a provider and purchaser of a service (i.e. data hosting).</p><p><strong>Claims<br></strong>Tiles are used to create statements about other DIDs; to achieve this they can create a Verifiable Claim tile. Verifiable claims are a flexible standard for creating signed statements or data. If the verifiable claim is accepted by the recipient, is included in the recipient’s metadata above.</p><h3>3. Ceramic Use Cases</h3><p>Most production systems and applications that use Ceramic will combine these simple primitives (DIDs, account links, and tiles) to enjoy the simplicity, interoperability, and scale that is only possible when identities, resources, and services are unbundled from wallet or application silos. Here are a few powerful use cases that are built on Ceramic:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5zZWPGc-UZwCJoR8UcYW7A.png" /></figure><h4>Portable, Self-Sovereign Identity</h4><p>Self-sovereign identity (SSI) describes a system where participants can permissionlessly create and control their digital identity using one or more private keys. Technically, SSI could be enabled by any decentralized asymmetric cryptography system where public keys (identities) are controlled by private keys (passwords) such as bitcoin or ethereum. However, this type of system would be limited to the network on which these identities are registered, as well as the single private key account. These two constraints function as silos that prevent this identity from being used interoperably in additional contexts.</p><p>For identities to be truly flexible and portable across platforms and keys, which makes them more useful in practice, we need an additional identity abstraction that lives at a layer above blockchain accounts. This is the value of DIDs. On Ceramic, DIDs function as the global public identity and they can be controlled by any number of private keys from any blockchain or cryptographic system. DIDs provide a single interface that owners can use to identify themselves, interoperably sign messages, encrypt data, and authorize/access control to off-chain services that is agnostic to which blockchain a user is on. DIDs are the antidote to private key and network lock-in.</p><p>SSI is often meant to include much more than direct control of an identifier. Most times, this identifier needs more context so others can interact with it, such as profile details. Ceramic tiles allow DID owners to permissionlessly add public metadata and additional information or resources to their SSI, making for a flexible and dynamic SSI solution.</p><h4>Interoperable Data Ecosystems</h4><p>For powerful interoperable experiences, data portability across applications is required. This requires a few core functionalities. First, we need to have a universal way for users to identify themselves across platforms, so that we can know which data is theirs. This is handled by SSI/DIDs (see above). Second, we need to know where this data lives in order to request it. Third, we need to be able to access this data, with users’ permission. Last, we need to know the schema of the data so we can consume it in our application without manual processing.</p><p>Ceramic makes this simple for all parties. By storing mappings to data resources in a user’s DID, Ceramic provides a way for applications (and other data consumers) to efficiently discover where information lives, whether on a specific server or a public network. Also by allowing Ceramic DIDs to define access control policies for their data resources via tiles, Ceramic provides an identity-centric way for users to provide consumers access to their information regardless of where it lives. Instead of access control happening on the server, it happens directly on the user. Finally, Ceramic allows applications to define schemas for any data being saved so that data consumers can know a priori the shape of the data that will be returned, even if it is encrypted.</p><p>Together these capabilities allow users to frictionlessly control and share their data across various application and server silos, while also allowing developers to make use of a richer, higher quality dataset than ever — without storing any of it.</p><h4>Open Web Services</h4><p>The last piece of the interoperability puzzle is providing more open access to web services. All service providers on Ceramic (i.e. data hosting, indexing, anchoring, payments, or other arbitrary web/API services) can service requests from <em>all</em> other identities, with no need for bilateral, one-off accounts. Service providers can remove the requirement of creating an account and using an API key to access their service. Rather than through an API key living on an application’s backend, services can be accessed whenever a user, application, or other service meets certain pre-defined conditions. This allows service providers to remove all friction from accessing their services and to grow their customer base on a per-use (or other predefined) basis.</p><p>For example, a service provider that is hosting user data that needs to be accessed by many different parties can now serve all of them without each of them needing an account with the service. Using Ceramic, the data hosting service can define their service and create a service policy that includes the requirements a consumer must meet in order to access their service. When a user (or application) chooses to use this service to host their data in a database that is access controlled by a DID, the user (or app) then adds this resource to their DID. When other consumers want to request this information they need to request access permissions from the user, and once approved, then fulfill the requirements of the hosting service (such as payments or other) before the data will be returned.</p><p>Although Ceramic provides the information required for services to accept per-use payments from all parties, the Ceramic protocol itself does not handle payments. Because these transactions will likely be small micropayments, Ceramic is extremely complementary to emerging permissionless cryptographic micropayment networks such as <a href="https://github.com/ConnextProject">Connext Network</a> on EVM blockchains and <a href="https://github.com/lightningnetwork/lnd">Lightning Network</a> on Bitcoin. In the most permissionless version of these systems, service providers and end users would run payment nodes and transact. In more practical versions, these responsibilities can be delegated to a third-payment payment processor. This model would also allow applications to pay for services on behalf of their users. We think this make the most sense in the near term.</p><p><em>Although this example depicts a data hosting service, Ceramic service policies can be used for almost any type of service.</em></p><h4>Example: 3Box</h4><p>To make everything more concrete, let’s dive into how <a href="http://github.com/3box/3box">3Box</a> relies on Ceramic to enable an interoperable, user-controlled data management system. 3Box is a framework that allows developers to store user and application data on a network of open data hosting services access controlled by users instead of on siloed application servers. Users are always in control of their data and can choose to permission it out to other applications, making it shareable across platforms and applications. To achieve this 3Box relies on <a href="https://github.com/ceramicnetwork/ceramic/blob/master/OVERVIEW.md#portable-self-sovereign-identity">self-sovereign identity</a>, <a href="https://github.com/ceramicnetwork/ceramic/blob/master/OVERVIEW.md#interoperable-data-ecosystems">interoperable data</a>, and <a href="https://github.com/ceramicnetwork/ceramic/blob/master/OVERVIEW.md#open-web-services">open web services</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WKYOhT2AuMRDagIToToAMA.png" /></figure><p>For self-sovereign identity and to enable user-managed access control, 3Box uses Ceramic’s 3ID DID method which allows users to control their identity, information, and services using all of their existing private wallet keys. To enable interoperable data and shared access web services, 3Box relies on the following set of tiles which are created by the various participants that play a role in the system including applications, services, and users:</p><ul><li><a href="https://github.com/ceramicnetwork/ceramic/blob/master">Schema(s)</a>: Describes a data schema used in a particular database. Allows <em>developers</em> to define their data schemas, or use existing ones.</li><li><a href="https://github.com/ceramicnetwork/ceramic/blob/master">Collection Policy</a>: Describes a collection of databases linked to Schema tiles. Allows <em>applications</em> to define their databases and the data models they use so others can easily consume the data.</li><li><a href="https://github.com/ceramicnetwork/ceramic/blob/master">Service Policy</a>: Describes simple functions that take an input and produce an output. In this case, it’s used for hosting of databases in the Collection Policy. Allows <em>service providers</em> to define their service or API and the requirements to access it.</li><li><a href="https://github.com/ceramicnetwork/ceramic/blob/master">Privacy Policy</a>: Describes user-managed access control rights to databases in the Collection Policy. Allows <em>users</em> to set permissions and control their privacy while sharing data across apps.</li></ul><p>This collection of functionalities allows App A to store data for User B on a hosting service in databases that are access controlled by User B’s 3ID. User B can now go to App C and give them permission to access their data from App A. To receive the data from the hosting service, App C must meet the requirements defined by the hosting service’s service policy which may include payment information.</p><h3>4. Ceramic Ecosystem</h3><p>By now you understand that Ceramic enables the emergence of a diverse, interoperable ecosystem of user-controlled wallets, data stores, and infrastructure services that allow developers to build lightweight, composable, collaborative applications. Here’s how you can participate.</p><h4>Wallets and Authentication Systems</h4><p><strong>Integrate Platform-Agnostic, Self-Sovereign Identity</strong>: Give your wallet’s users the ability manage their data and other off-chain services using a DID instead of a particular private key. DIDs are an abstraction from individual key pair and contract accounts that eliminate private key lock-in. DIDs are used for interoperable data signing, encryption, and service authorization with all the wallet keys your users already have.</p><h4>Databases</h4><p><strong>Integrate a Unified, User-Managed Access Control System</strong>: Make your database’s access control system compatible with Ceramic DIDs so users can manage their information stored across all databases with a single identity and allow different applications to access their information. Ceramic will first support IPFS-based peer-to-peer databases <a href="https://github.com/orbitdb/orbit-db">OrbitDB</a> and <a href="https://github.com/textileio">Textile</a>.</p><h4>Services</h4><p><strong>Offer Open, Shared Access Services</strong>: Offer Ceramic-compatible services and list your infrastructure on the Ceramic network to allow others to discover and interact with your service even if they’re not your direct customers.</p><h4>Applications</h4><p><strong>Build Composable, User-Centric Applications</strong>: Build your app using Ceramic’s ecosystem of connected, interoperable services. Store your user and application data in Ceramic-enabled databases with infrastructure providers that support Ceramic service agreements. Also use Ceramic to discover available data sources to populate your application.</p><h3>5. Ceramic Ecosystem Alliance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Zpi8scDWBcnC_f4S8S2qA.png" /></figure><p>The Ceramic Ecosystem Alliance is a collaborative group of organizations, communities, and individuals actively contributing to the research and development of the Ceramic protocol, integrating Ceramic standards into their products, or building services on the Ceramic network. Become a member and <a href="https://danny765911.typeform.com/to/AAFtVN"><strong>sign up here</strong></a>.</p><h3>6. Timeline</h3><p>Ceramic’s core contributors are working hard to ship v1 of the network. We already have some working code in <a href="https://github.com/ceramicnetwork/js-ceramic">js-ceramic</a>, and ideally will launch into production sometime this summer.</p><p>Hop in our <a href="https://discord.gg/6VRZpGP"><strong>Discord</strong></a> to ask more questions.</p><h3>Further Reading</h3><h4><a href="https://github.com/ceramicnetwork/specs">Continue to Ceramic Technical Specification &gt;</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d56951ae3f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ceramic/introduction-to-the-ceramic-protocol-8d56951ae3f">Introduction to the Ceramic Protocol</a> was originally published in <a href="https://medium.com/ceramic">Ceramic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Confidential Threads API]]></title>
            <link>https://medium.com/3box/confidential-threads-api-17df60b34431?source=rss-fc3b0ec804e------2</link>
            <guid isPermaLink="false">https://medium.com/p/17df60b34431</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[3box]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[messaging]]></category>
            <dc:creator><![CDATA[Michael Sena]]></dc:creator>
            <pubDate>Fri, 14 Feb 2020 14:53:47 GMT</pubDate>
            <atom:updated>2020-02-14T14:53:47.242Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XHao8D_H8WRQ7TXgrpoQMg.png" /></figure><h4>Private messaging for DMs, group chat, and private lists</h4><p>Since we launched the first version of 3Box threads <a href="https://medium.com/3box/3box-decentralized-comments-api-7e495d2ddd24">almost a year ago</a>, developers have been asking for increased privacy for their users’ messages. Today we’re excited to finally lift the curtain on our brand new <a href="https://docs.3box.io/build/web-apps/messaging/persistent-threads#first-decide-on-a-persistent-thread-type">Confidential Threads API</a>. Confidential threads enable private, encrypted, peer-to-peer messaging between one or many participants.</p><p>Unlike 3Box open threads, which are publicly readable by everyone, confidential threads are only readable by a designated subset of users. Use confidential threads anytime you don’t want outsiders to be able to read the contents of your stream.</p><p>Confidential threads are perfect for adding direct messages, group chats, or private lists to your application.</p><p><em>Continue reading to more about use cases and how to add confidential threads to your application.</em></p><h4>👉 <a href="https://docs.3box.io/build/web-apps/messaging/persistent-threads">Read the Docs</a> 👈</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PM-iyOxPB0oFQkn7NEdUlQ.png" /></figure><h3>Types of Confidential Threads</h3><p>3Box supports two primary types of threads. <a href="https://docs.3box.io/build/web-apps/messaging/persistent-threads">Persistent threads</a> persist messages in an OrbitDB feed store where they remain unless removed by the original author or a moderator, while <a href="https://docs.3box.io/build/web-apps/messaging/ghost-threads">Ghost threads</a> are more ephemeral and only exist in the memory of online peers, and do not use OrbitDB. If all peers go offline, then the message history of a ghost thread is lost.</p><p><a href="https://docs.3box.io/build/web-apps/messaging/choose#types-of-persistent-threads">Confidential threads</a> are a type of persistent thread with two varieties: <a href="https://docs.3box.io/build/web-apps/messaging/choose#persistent-members-confidential">Members Confidential</a> and <a href="https://docs.3box.io/build/web-apps/messaging/choose#persistent-personal-confidential">Personal Confidential</a>.</p><p>The first terms Members and Personal describe the write permissions on the thread, while the second term Confidential indicates that read access is restricted to those who can write. Read access control restrictions are implemented using asymmetric encryption with the user’s 3ID.</p><p>Below, see the two confidential thread options in relation to other persistent thread types offered by 3Box:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OQXB1w0AEn-X610AGHCkuQ.png" /><figcaption>Persistent thread types supported by 3Box</figcaption></figure><p><em>As you can see, 3Box also offers non-confidential thread types. Explore the docs for </em><a href="https://docs.3box.io/build/web-apps/messaging/choose#persistent-open"><em>Open</em></a><em>, </em><a href="https://docs.3box.io/build/web-apps/messaging/choose#persistent-members-open"><em>Members Open</em></a><em>, or </em><a href="https://docs.3box.io/build/web-apps/messaging/choose#persistent-personal-open"><em>Personal Open</em></a><em> threads to learn more.</em></p><h3>Use Cases for Confidential Threads</h3><h4>Private Messaging and Data Sharing</h4><p>Since members confidential threads restrict write and read access to the same subset of users, they are great for <strong>direct messages</strong> between two users, <strong>group chats</strong> between 3+ users, and <strong>private shared data feeds/streams</strong> between 2+ users.</p><h4>Private Personal Lists</h4><p>Since personal confidential threads restrict write and read access to a single user, they are great for creating private <strong>personal lists</strong> or <strong>content streams</strong> that can be read and modified by <strong>only the author</strong>. Example use cases include private <strong>shopping carts</strong>, <strong>to-do lists</strong>, <strong>contact lists</strong>, <strong>playlists</strong>, <strong>photo albums</strong>, and more.</p><h3>Build with Confidential Threads</h3><p>Below we will walk through how to create and use confidential threads with the 3Box APIs made available via <a href="https://docs.3box.io/build/web-apps/install">3Box.js</a>. Full documentation is available <a href="https://docs.3box.io/build/web-apps/messaging"><strong>here</strong></a>.</p><ol><li>Install 3Box SDK</li><li>Configure your threads</li><li>Create a new confidential thread</li><li>Join an existing thread</li><li>View posts</li><li>Add posts</li></ol><h4>1. Install 3Box SDK</h4><p>Add 3Box to your project using npm:</p><pre>npm i 3box</pre><h4>2. Configure your threads</h4><p>Before getting started, you should consider a few configuration options for your persistent threads, which will make later steps more simple.</p><p>You only need to perform this step if you are creating a <strong>new</strong> persistent thread. If you want to join an existing thread, then proceed to Step 4 (join an existing thread).</p><p><strong>First, choose a name for your space. <br></strong>Persistent threads are stored in OrbitDB feed stores, and references to these threads are stored in your application’s space. These spaces are created and exist inside the 3Box of each user that joins the thread, not in one single global space. You should choose a name for the space that you will use to store your app’s thread references.</p><p>In most cases, the name of the space should be the name of your application.<strong> </strong>We recommend simply using the name of your application for this threads space, unless you want your application’s threads kept in a different space for some reason. This space is an OrbitDB key-value store, so you can also keep other information and data related to your application inside it.</p><p>For example, if your application is called SuperRare we would recommend calling your space SuperRare.</p><p>‌<strong>Then, choose a naming convention for your individual threads.<br></strong>For thread name, we recommend creating some standard convention that allows your application to easily create and manage many threads. While you can decide what this convention is, you may consider using the page URL, a topic, or something else unique.</p><h4>3. Create a new confidential thread</h4><p>Now that you have decided on the configuration options for your persistent threads, the next step in actually adding them to your application is allowing users to create new confidential threads.</p><p>**Note: To perform interactive operations on threads, such as creating a thread, joining a thread, posting messages, removing messages, adding moderators, and adding members, you must first authenticate the space wherein the thread is stored.</p><p><strong>Create a Members Confidential or Personal Confidential Thread</strong></p><p>To create a members confidential or personal confidential thread, use the createConfidentialThread method.</p><pre>const thread = await space.createConfidentialThread(&#39;myConfThread&#39;)</pre><p>For a members confidential thread, you will likely want to add other members around the time of creation so they can read from and write messages to the thread. Use the addMember method to allow moderators to add members to this thread. Note this is performed on the thread object.</p><pre>await thread.addMember(&lt;ethereum-address or 3id&gt;)</pre><p>For a personal confidential thread, you will not add additional members to the thread.</p><h4>4. Join an existing thread</h4><p>Persistent threads are identified within the 3Box network in two ways: by a unique<strong> thread address</strong>, or by a unique set of <strong>configuration options</strong>. While either can be used to join an existing thread, we recommend joining by the thread address.</p><p><strong>Join Thread by Address</strong></p><p>To join an existing thread, the easiest way is by its address using the joinThreadByAddress() method.</p><pre>const thread = await space.joinThreadByAddress(&#39;/orbitdb/zdpuAp5QpBKR4BBVTvqe3KXVcNgo4z8Rkp9C5eK38iuEZj3jq/3box.thread.testSpace.testThread&#39;)</pre><p>For members confidential and personal confidential threads, joining the thread will not allow you to read messages or post new messages unless you have first been added by a moderator.</p><p><strong>Discover Thread Address</strong></p><p>Users can discover the thread address in many ways depending on the app’s implementation of thread discovery, however users within the thread can use the code below to get the thread address and send it to new users in whatever way they choose.</p><p>An address of a thread can be found as follows once joined.</p><pre>const threadAddress = thread.address</pre><h4>5. View posts</h4><p>There are three options to getting the messages in a thread, but only one works for confidential threads since the user needs to first authenticate to decrypt and read the message they have permission to.</p><p><strong>First authenticate the user, then call </strong><strong>thread.getPosts()</strong></p><p>This option for getting messages in a thread is appropriate when:</p><ul><li>you may not know the address or configurations of the thread</li><li>you have already authenticated a user using the openBox and openSpace methods</li><li>the user has already joined the thread</li><li>you want to dynamically display updates to the thread</li></ul><p>To get all posts in a thread, use thread.getPosts()</p><pre>const posts = await thread.getPosts()</pre><pre>console.log(posts)</pre><pre><em>// you can also specify a number of posts you want</em></pre><pre>const posts = await thread.getPosts(20)</pre><pre>console.log(posts)</pre><p><strong>Listen for new updates</strong></p><p>After you have gotten posts in a thread, you will likely want to listen for updates to the thread so you can update your application’s UI. To listen for updates to a thread, such as new posts, use thread.onUpdate(). This will allow you to immediately display new messages posted to the thread in your application.</p><pre>thread.onUpdate(myCallbackFunction)</pre><h4>6. Add posts</h4><p>To post in a thread, a user must first either create or join the thread using the steps above. After they have joined a thread, they can add a message to the thread using the thread.post() method. The author of the message will be the user&#39;s 3ID (3Box DID). Everyone who has permission to read the thread will have access to the message.</p><pre>await thread.post(&#39;hello world&#39;)</pre><h3>Want to add confidential threads to your project?</h3><p>We’re always online and available to chat in <a href="https://chat.3box.io/"><strong>Discord</strong></a> if you have any questions about building with confidential threads or anything else. You can also read the full docs <a href="https://docs.3box.io/build/web-apps/messaging/persistent-threads"><strong>here</strong></a>.</p><p>#BuildBetter 3️⃣</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17df60b34431" width="1" height="1" alt=""><hr><p><a href="https://medium.com/3box/confidential-threads-api-17df60b34431">Confidential Threads API</a> was originally published in <a href="https://medium.com/3box">3Box Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3Box messaging plugins get more social!]]></title>
            <link>https://medium.com/3box/3box-messaging-plugins-get-more-social-354e2afe88cb?source=rss-fc3b0ec804e------2</link>
            <guid isPermaLink="false">https://medium.com/p/354e2afe88cb</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[3box]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Michael Sena]]></dc:creator>
            <pubDate>Thu, 06 Feb 2020 15:57:48 GMT</pubDate>
            <atom:updated>2020-02-06T15:57:48.423Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vKsD4qj3kBQCS1SgF3ab_w.png" /></figure><h4>Message Likes, Reactions, Replies, and Votes</h4><p>When we released the first versions of 3Box <a href="https://docs.3box.io/build/plugins/comments">Comments</a> and <a href="https://docs.3box.io/build/plugins/chatbox">Chatbox</a> plugins last year, we had the goal of making every web3 app just a little more social with minimal developer effort — by easily sprinkling in UI components that allow users to interact with applications and each other in exciting ways.</p><p>Many developers added these easy-to-use UI plugins to their applications; and the Comments plugin even won a UX award at Devcon 5!</p><p><strong>Today we’re excited to release new versions of </strong><a href="https://docs.3box.io/build/plugins/comments"><strong>Comments</strong></a><strong> and </strong><a href="https://docs.3box.io/build/plugins/chatbox"><strong>Chatbox</strong></a><strong>, complete with even more social features: likes, reactions, replies, and votes! </strong>These features make 3Box’s commenting and chat plugins even more social, closing the feature parity gap between web3 technology and legacy web2 solutions such as Disqus. Let’s create better dapps today! #BuildBetter</p><h3>3Box Comments</h3><p>We’ve added comment replies, emoji reactions, votes, and a deleted comment UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4_zkn3Rzcs-zvUy0ZAJe-w.gif" /></figure><h4>Get started with Comments</h4><ul><li><a href="https://docs.3box.io/build/plugins/comments"><strong>Read the Docs</strong></a> 📚</li><li><a href="https://3box.github.io/3box-comments-react/examples/dist/"><strong>Try the Demo</strong></a> 🏄‍♂️</li></ul><h3>3Box Chatbox</h3><p>We’ve added message likes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gwgV7t6LKsy4SZgAXc3vxA.gif" /></figure><h4>Get started with Chatbox</h4><ul><li><a href="https://docs.3box.io/build/plugins/chatbox"><strong>Read the Docs</strong></a> 📚</li><li><a href="https://3box.github.io/3box-chatbox-react/examples/dist/"><strong>Try the Demo</strong></a> ❤️</li></ul><h3>Questions? Reach out on Discord!</h3><p>We’re always online and available to chat in <a href="https://chat.3box.io/"><strong>Discord</strong></a> if you have any questions about our messaging plugins or anything else.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=354e2afe88cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/3box/3box-messaging-plugins-get-more-social-354e2afe88cb">3Box messaging plugins get more social!</a> was originally published in <a href="https://medium.com/3box">3Box Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3Box Hub now supports ENS]]></title>
            <link>https://medium.com/3box/3box-hub-now-supports-ens-af4a8efbd36e?source=rss-fc3b0ec804e------2</link>
            <guid isPermaLink="false">https://medium.com/p/af4a8efbd36e</guid>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[3box]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[integration]]></category>
            <dc:creator><![CDATA[Michael Sena]]></dc:creator>
            <pubDate>Tue, 07 Jan 2020 13:49:51 GMT</pubDate>
            <atom:updated>2020-01-07T13:49:51.236Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KIfpBnGjXjs7u_7_VeJ7Vw.png" /></figure><h4>View ENS names inside Hub using ENS SDK and The Graph</h4><p>We’re excited to announce we’ve improved the <a href="https://3box.io/login">3Box Hub</a> UI with an ENS integration. Now you can view ENS names right alongside 3Box profiles inside the Hub app. Not only does the combination of Profiles and ENS deliver improved usability, but also adds more trust to the 3Box ecosystem.</p><p>At this time, we only display users’ existing ENS names and do not support creating 3Box ENS names: such as <em>yourname.3box.eth</em>. However, we will enable this functionality in the future.</p><h4>Try it today</h4><ul><li><a href="https://3box.io/login">Log in to 3Box Hub</a></li></ul><h3>Where is ENS in the app?</h3><p><strong>Profile Search:</strong> Search users by their ENS name or their Ethereum address</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SYE0njMnzjNjJmJDfbMSyA.png" /></figure><p><strong>Profile Details:</strong> View ENS names alongside 3Box profile details</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IjeYo7PtE8kdBT0QqjoUbQ.png" /></figure><p><strong>Profile Wall and Activity Feed: </strong>ENS names on your wall and activity feed</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A-LmnpqA0lMtHMyX3EXnRQ.png" /></figure><h3>How it Works</h3><h4>Display Canonical ENS Names</h4><p>After purchasing an ENS name at one of the ENS domain registration sites, users can choose to set their name as their <em>canonical</em> name (ie: yourname.eth returns a 0x… ETH address) by setting up a reverse resolution record. Since Ethereum addresses can only have one ENS name reverse resolved at any given time, we chose to display this name wherever we show names inside Hub. The reality is that some users own many ENS names for themselves or their businesses, and we only wanted to only show the one that they chose to self identify with. If a user never set a canonical name, then we show the first name that is returned when we look up the ENS registry contracts.</p><h4>Technology Required</h4><p>To make this possible, we use two third-party technologies: <a href="https://thegraph.com/"><strong>The Graph</strong></a> and <a href="https://www.npmjs.com/package/ethereum-ens"><strong>ethereum-ens</strong></a>.</p><p>ethereum-ens is a JavaScript library maintained by the core ENS team that allows front-end applications to check reverse resolution records required for getting a user’s canonical name. Since reverse resolution records need to be verified with a subsequent forward resolution, we also use this library for that. If the same result is achieved with both queries, then we display that canonical name for an Ethereum address in Hub.</p><p>The Graph is a simple GraphQL query interface for the Ethereum blockchain, which we use to gather all ENS names owned by an address. We use this list of names to populate the user’s UI in the instance that they, or other users, have not set a canonical name.</p><h3>What’s next?</h3><p>We’re eventually going to give 3Box users the ability to create a 3Box ENS name, such as yourname.3box.eth, but this will come in a later release.</p><h3>Questions? Reach out on Discord!</h3><p>We’re always online and available to chat in <a href="https://chat.3box.io/"><strong>Discord</strong></a> if you have any questions about this integration or our software.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af4a8efbd36e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/3box/3box-hub-now-supports-ens-af4a8efbd36e">3Box Hub now supports ENS</a> was originally published in <a href="https://medium.com/3box">3Box Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>