Home of the Ceramic Protocol
Home Page: http://ceramic.network
.github
Organization level configuration and defaults
See https://help.github.com/en/articles/creating-a-default-community-health-file-for-your-organization
750 DAI
A consistent challenge in distributed, interoperable storage environments is maintaining compatibility when underlying data schemas are updated to a new version; this could cause different data instances that rely on the same schema to be using different versions of the schema – causing headaches for application developers. Cambria is an exciting approach to converting JSON data between related schemas using lenses. See more in this video.
Ceramic is a decentralized network for deploying version-controlled data, and an ideal place to house these lenses so they are globally available and easy to link. Additionally, Ceramic could also benefit from having support for Cambria or a similar solution as a way to enable even easier and more powerful interoperability between various Ceramic streams and schema.
This bounty is for the best proof-of-concept implementation of Cambria (or a similar system) on Ceramic schemas and data models.
Submissions will be evaluated based on the implementation cleanliness, usability, and readiness.
October 27th
This description misses the required specificity: "cross-platform decentralized identity graph complete with DIDs, identity metadata such as profiles" as it stands, I cannot serve as the foundation for the development of a viable implementation. - In particular: what functionally (and legally) relevant actions are being supported (IRL). It is not: "identity", and certainly not "decentralized identity" .. the closest equivalence IRL would be a person suffering from DID - fittingly that acronym is most commonly used for Dissociative Identity Disorder. - Consequently 'identity' and 'identification' are conflated several times in the documentation, including - but not limited to - the "identity wallet" and "3-ID Connect" which is described as "account management service".
js-ceramic IPFS updatesjs-ceramic-ipfs repo which will enable dag-jose by default500 DAI
Ceramic's Identity Link Services enable the linking of social accounts to a decentralized identity (DID) and its associated blockchain accounts. Currently, services are built for Twtiter, Github, Discord and Discourse.
This bounty is to add a working verification flow for Telegram. It likely will use a bot, similar to the discord implementation (see this repo)
Don't forget to update the API documentation with your verification system once it's implemented.
Share your planned work before completing the implementation
Code quality and reliability must be high, and must be well documented
Must be submitted to the identity services repo in Ceramic Studio
First submission that meets requirements and is ready for deployment.
Valid through April 5
First prize: 1,500 DAI for best hack using IDX
Runner up: 750 DAI
This is an open prize for using IDX to manage decentralized identity information or data. This can include integrating IDX into an existing project, building a new product that uses IDX, building tooling that supports or complements IDX, or any other creative implementation that makes use of IDX as decentralized identity infrastructure. IDX is currently in alpha.
Submissions will be evaluated on:
IDX is a new cross-ecosystem decentralized identity and user data management protocol that provides for a single, unified digital identity system that works with all Web3 platforms, blockchains, and storage technologies. IDX is built on Ceramic, a peer-to-peer dataweb for publishing, linking, and querying verifiable information on the open web. IDX is currently in alpha so may be unstable.
IDX provides a flexible identity infrastructure for developers to use when building decentralized applications. It can be used to store profiles and metadata, link multiple blockchain and social accounts to a single identity, read and write user verifications, and manage data on IPFS, OrbitDB, Textile, SkyDB or any other platform. This decentralized, unified, and cross-platform identity infrastructure helps Web3 projects build faster and more simply. It is also the key to realizing the vision of giving users ultimate control and portability of their information across applications and networks by breaking down information silos and putting users at the center of the web.
With IDX, every user gets a cross-platform decentralized identifier (DID) and an identity index document to which developers can attach various pieces of data relevant to their experience. Since IDX identities are public and permissionless, any developer can openly discover, query, and import data from an identity into their application, creating a rich ecosystem of information around each user.
IDX Website: https://idx.xyz
IDX Docs: https://idx.xyz/docs
IDX and Ceramic Tutorials: https://blog.ceramic.network/tag/tutorials/
Ceramic website: https://www.ceramic.network
Dev Chat: chat.idx.xyz
This issue is a work in progress. Please feel free to add recommendations or thoughts in the comments. As the explorer specification becomes more solidified, this document is subject to change.
It would be awesome for someone in the community to create an explorer so developers/prosumers can easily discover documents on the Ceramic network via an interface.
Pending (Signed record)Processing/Anchoring (Submitted to a blockchain) [maybe this isn't needed?]Confirmed (Anchor record added)React
The explorer would be most performant and feature-complete if it was built on an index, but for the MVP we could likely directly query the network.
cc @oed @kamescg @msterle @pedrouid @simonovic86
IDX is a new cross-ecosystem decentralized identity and user data management protocol that provides a way for users enjoy the benefits of having a single, unified digital identity that works with all Web3 platforms, blockchains, and storage technologies – including SkyDB.
IDX provides a universal identity layer for developers to use when building decentralized applications. This helps to realize the Web3 vision of giving users ultimate control and portability of their information across applications and networks by breaking down information silos and putting users at the center of the web. IDX can be used to build a unified, cross-platform Web3 identity and make user data stored in SkyDB, or anywhere else on Web3 (think Ceramic, Filecoin, OrbitDB, TextileDB), interoperable across domains and platforms. Using IDX, your app can even store data in SkyDB and discover/pull-in user data stored in any of the systems mentioned above.
With IDX, every user gets a cross-platform decentralized identifier (DID) and an identity index to which developers can attach various pieces of data – from linked blockchain accounts and user profiles, to social graphs, SkyDB instances, and much more. Additionally, since IDX identities are public and permissionless, any developer can openly discover, query, and import data from an identity into their application. This is especially useful for shared, cross-domain data cases like public profiles or social graphs.
For this bounty, we’re looking for someone to build a project that makes use of IDX as an identity protocol alongside SkyDB. To achieve this, during onboarding you can use the IDX SDK to import or create identities, add your user’s SkyDB instance for your application to their identity index, and query their index for their data stored throughout the Web3 ecosystem – on any other Web3 platform. Feel free to use IDX for additional in-app features such as user profiles, social graphs, or anything else you can imagine. IDX allows you to store this identity metadata natively in documents on the Ceramic network, where it can be consumed everywhere across the Web3 ecosystem – within Sia applications and beyond.
We have many ideas for how to connect a SkyDB instance to IDX, so please reach out to our team in the IDX Discord if you have questions.
IDX Website: https://idx.xyz
IDX Docs: https://idx.xyz/docs
Dev Chat: IDX Discord
IDX Announcement: https://medium.com/3box/idx-a-devkit-for-open-identity-48edc88e8e85
js-ipfs dependenciesipfs typesImplement retry mechanism for possible ETH TX failures.
Using the @StableLib packages
The Ceramic community has put up $15K so far for a product that mirrors twitter posts onto Ceramic. There's a lot to be worked out here, but a very high potential project for anyone looking to build something ambitious!
Context here: https://twitter.com/StefanDGeorge/status/1347861734716035074
Describe the bug
Error: Unable to connect on ceramic popup
To Reproduce
Steps to reproduce the behavior:
import { ThreeIdConnect, EthereumAuthProvider } from '@3id/connect'
const threeIdConnect = new ThreeIdConnect()
let authProvider = new EthereumAuthProvider(window.ethereum, address)
yield threeIdConnect.connect(authProvider)
const didProvider = yield threeIdConnect.getDidProvider()
const CERAMIC_URL = "https://ceramic-clay.3boxlabs.com";
const ceramic = new Ceramic(CERAMIC_URL)
yield ceramic.setDIDProvider(didProvider)
Screenshots
Pic 1 - These APIs are getting called only, after which i get the error in Pic 2
Pic 2
Pic 3 and Pic 4 - Getting error on this API only for now but still other APIs are getting called which further gives the error on popup.
Ceramic versions
"@3id/connect": "^0.1.3",
"@ceramicnetwork/http-client": "^0.9.3",
"@ceramicstudio/idx": "^0.7.0",
Machine, OS, browser information (please complete the following information):
Linux,testing on Chrome and Brave only for right now.
js-ipfs instance with APIs enableddag-jose codec by default.2,000 DAI
Open prize for building with Glaze or Self.ID.
Read this article for more information about the tools and how to build applications with them.
October 27th
Update JSON Schemas from the doc.
...such as setting the content to an empty string or null
3id-blockchain-utils)Hi folks! I'm really enjoying to get to discover Ceramic! Watched through https://www.youtube.com/watch?v=AplPOcWdVik
Can you confirm when is the next Call for the technical discussion? I would love to join and share notes! Do you have a Community Calendar with all your calls?
We spent some time developing a lot of similar ideas in the past with a large bet on CRDT, Cryptographic ACLs and Verifiable Claims. In case you are curious, you can check (everything is open and MIT licensed):
//cc @pgte @satazor @joaosantos15 @jimpick @dirkmc who I'm sure will enjoy learning about Ceramic and discussing ideas as well
Keep up the great work! 🌟🌟🌟🌟🌟🌟
PS: I'm curious on the name, is it Ceramic because you are building the Porcelain on top of all the other protocols or because you use Tiles as a concept?
Create a CIP PR based on the issue
Will need to be a Core ceramic feature / property of DocState. Doctypes can then choose if they support schemas. Also add how schemas are validated.
When there's no schema embedded in the proof.
As simple as possible for a PoC Using the jose library for creating JWS objects and store them in ipld.
Check for secp256k1 and ed25519 support (should work already).
750 DAI
Self.ID is a drop-in bundle for building web applications with decentralized data that includes Ceramic, Glaze (DID DataStore and DataModels), and 3ID Connect (blockchain-based authentication). Self.ID aims to make it as easy as possible for developers to get started building decentralized data applications on Ceramic.
DID DataStore is a cross-chain identity protocol that allows applications to store and retrieve information in a user's decentralized identity based on customizable data models - such as profile, social graph, blog posts, linked blockchain accounts, application data, or whatever you can imagine. Multiple applications can reuse the same data models to share access to the user's data – achieving true data interoperability. DID DataStore makes use of decentralized identifiers (DIDs) as persistent, globally-unique user identifiers with verifiably-linked blockchain accounts (from any or multiple chains), but does not natively have a human readable naming system.
Unstoppable Domains provides human-readable naming systems that can resolve records used to store basic metadata, but not as complete identities.
Together, Self.ID combined with Unstoppable Domains provides a complete identity solution, enabling applications to use human-readable names to refer to a blockchain account, resolve the account's associated DID, and request access to desired information stored in DID DataStore.
The challenge: Create a guide so that any developer can use Self.ID with the Unstoppable naming service.
October 27th
The merkle tree should be generated once every 1h (for now). For the PoC we can anchor on the rinkeby ethereum testnet.
Many of the "learn more" links on the OVERVIEW page are broken, such as the links that say "Learn more about 3IDs or see an example.", "Learn more about account links.", etc. We should update them to point to the proper parts of our current documentation
500 DAI
Build a project that makes use of IDX as an identity protocol alongside Textile's ThreadsDB. To achieve this, during onboarding you can use the IDX SDK to import or create identities, create a Textile ThreadsDB definition for your application's data, add this to users' identity index, and query their index for their data stored by your app or others.
Feel free to use IDX for additional in-app features such as user profiles, social graphs, or anything else you can imagine. IDX allows you to store this identity metadata natively in documents on the Ceramic network, where it can be consumed everywhere across the Web3 ecosystem.
For this prize, we will be evaluating submissions based on:
Use of IDX and Textile ThreadsDBs
Should require authentication via IDX to post to thread. Anyone can read
Implementation completeness
Creativity of the integration
Demo or other supporting material that makes the implementation useful for others
IDX is a new cross-ecosystem decentralized identity and user data management protocol that provides for a single, unified digital identity system that works with all Web3 platforms, blockchains, and storage technologies. IDX is built on Ceramic, a peer-to-peer dataweb for publishing, linking, and querying verifiable information on the open web. IDX is currently in alpha so may be unstable.
IDX provides a flexible identity infrastructure for developers to use when building decentralized applications. It can be used to store profiles and metadata, link multiple blockchain and social accounts to a single identity, read and write user verifications, and manage data on IPFS, OrbitDB, Textile, SkyDB or any other platform. This decentralized, unified, and cross-platform identity infrastructure helps Web3 projects build faster and more simply. It is also the key to realizing the vision of giving users ultimate control and portability of their information across applications and networks by breaking down information silos and putting users at the center of the web.
With IDX, every user gets a cross-platform decentralized identifier (DID) and an identity index document to which developers can attach various pieces of data relevant to their experience. Since IDX identities are public and permissionless, any developer can openly discover, query, and import data from an identity into their application, creating a rich ecosystem of information around each user.
IDX Website: https://idx.xyz
IDX Docs: https://idx.xyz/docs
IDX and Ceramic Tutorials: https://blog.ceramic.network/tag/tutorials/
Ceramic website: https://www.ceramic.network
Dev Chat: chat.idx.xyz
Describe the bug
Since today only, i am getting error on api https://ceramic-clay.3boxlabs.com/api/v0/pins/k2t6wyfsu4pg1fj3y2j0zs1q9123cqxskk09n8bbs2b080t3wh73xh5xcikrla and https://ceramic-clay.3boxlabs.com/api/v0/documents/k3y52l7qbv1frxi800msx6cub6qxt6m0qgwe0jssvs1c0lhoww5kh4xh5h1jn8hds
To Reproduce
Steps to reproduce the behavior:
Using package '@3id/connect'
Connecting with 3id with the following code
import { ThreeIdConnect, EthereumAuthProvider } from '@3id/connect'
const threeIdConnect = new ThreeIdConnect()
let authProvider = new EthereumAuthProvider(window.ethereum, address)
yield threeIdConnect.connect(authProvider)
const didProvider = yield threeIdConnect.getDidProvider()
const CERAMIC_URL = "https://ceramic-clay.3boxlabs.com";
const ceramic = new Ceramic(CERAMIC_URL)
yield ceramic.setDIDProvider(didProvider)
Getting error on code statement - yield ceramic.setDIDProvider(didProvider).
Expected behavior
Gets connected to ceramic
Screenshots
Ceramic versions
"@3id/connect": "^0.1.3",
"@ceramicnetwork/http-client": "^0.9.3",
"@ceramicstudio/idx": "^0.7.0",
Machine, OS, browser information (please complete the following information):
Linux,testing on Chrome and Brave only for right now.
Additional context
Error coming since today only,was working fine till yesterday with the same written code.
500 DAI per blockchain added. Most complete implementation for each chain will be awarded the prize.
IDX supports a cross-ecosystem, cross-chain identity model by letting users link any number of blockchain accounts and key pairs to their DID. You can find clear instructions for how to add new blockchains in this article, along with the additional context needed.
Currently, Ethereum and Filecoin keys are supported. This bounty is to add support for additional blockchains. This makes the promise of a portable cross-chain identity more complete, and increases the number of apps and services that can use an interoperable identity infrastructure and data ecosystem.
The Ceramic core team is also available for questions at chat.ceramic.network. We encourage you to notify us of your plans to ensure you are adding support for a blockchain others are not already working on.
For this prize, we will be evaluating submissions based on:
IDX is a new cross-ecosystem decentralized identity and user data management protocol that provides for a single, unified digital identity system that works with all Web3 platforms, blockchains, and storage technologies. IDX is built on Ceramic, a peer-to-peer dataweb for publishing, linking, and querying verifiable information on the open web.
IDX provides a flexible identity infrastructure for developers to use when building decentralized applications. It can be used to store profiles and metadata, link multiple blockchain and social accounts to a single identity, read and write user verifications, and manage data on IPFS, OrbitDB, Textile, SkyDB or any other platform. This decentralized, unified, and cross-platform identity infrastructure helps Web3 projects build faster and more simply. It is also the key to realizing the vision of giving users ultimate control and portability of their information across applications and networks by breaking down information silos and putting users at the center of the web.
With IDX, every user gets a cross-platform decentralized identifier (DID) and an identity index document to which developers can attach various pieces of data relevant to their experience. Since IDX identities are public and permissionless, any developer can openly discover, query, and import data from an identity into their application, creating a rich ecosystem of information around each user.
IDX Website: https://idx.xyz
IDX Docs: https://idx.xyz/docs
IDX and Ceramic Tutorials: https://blog.ceramic.network/tag/tutorials/
Ceramic website: https://www.ceramic.network
Dev Chat: chat.idx.xyz
DIDs own documents that may only be created or edited by them but the open network allows for the query visibility of all created documents on the network is it possible to see proof of a document in query but restrict the visibility of the document content with only the DID providing permissions for this viewing ? this question is relevant in terms of determining if personal private data can be used on an enterprise blockchain running this network protocol as to increase transparency but also ensure security
This issue aims to specify an application that allows users to manage their 3ID account. It is a work in progress. Please feel free to input in the comments below, and we will update this spec over time. If you're interested in designing or building the UI, please reach out.
As a 3ID user, I want a simple way to manage my 3ID account, including my:
As a user, this application should allow me to:
Functionality:
Design:
Hosting:
--
For an overview of the 3ID account model, see this PR: ceramicnetwork/specs#21
3id invalidation from key rotation with failed anchor
Two plausible paths:
Include commitId of keychain commit that was updated in the key rotation done to the 3ID tile
Sign the keychain update with the new keys before they have been anchored
Probably not any of these:
3. Bundling everything into 3ID tile (undesirable for network performance reasons)
4. Atomic anchor (undesirable for system complexity reasons)
In the '3ID Identity' section of the overview, the '3IDs' and 'example' links land on a 404 page.
750 DAI
This bounty is to create an application or system for issuing identity-related credentials to a decentralized identity using DID DataStore or the Self.ID bundle. Your service can optionally use a third-party identity data provider, such as KYC (Onfido, BrightID, Berbix, Passbase) or reputation (proof-of-humanity, anti-sybil). Many of these providers have APIs that can be used to complete the identity verification/KYC check. Your application or service would need to generate a signed verifiable credential.
The format of the credential (and inspiration for the flow) can be taken from Ceramic's IdentityLink Service, which issue similar credentials for verified social accounts.
Tip: It's easier to create updatable/revokable credentials if each credential is stored in a separate data stream controlled by your application. Users would then need to add a reference to this credential stream inside their DID DataStore.
A good submission should consider how to handle the data submitted to complete the verification as well as the metadata contained in the verification itself.
October 27th
500-1000 DAI depending on submission quality and readiness
Build a proof of concept implementation for conviction voting off-chain using Ceramic. See this article for inspiration.
A valid submission will show an end to end implementation of conviction voting using IDX and Ceramic Network.
A demo video must show a multi-user experience.
It does not need to be production ready, but it should show a full experience and have a route to real usage
We encourage hackers to share their plans in chat.ceramic.network before going too far
Valid through mid-April
1500 DAI
This bounty is to integrate IDX (currently in alpha) into Gitcoin as articulated in this issue
Submissions will be evaluated on:
IDX is a new cross-ecosystem decentralized identity and user data management protocol that provides for a single, unified digital identity system that works with all Web3 platforms, blockchains, and storage technologies. IDX is built on Ceramic, a peer-to-peer dataweb for publishing, linking, and querying verifiable information on the open web. IDX is currently in alpha so may be unstable.
IDX provides a flexible identity infrastructure for developers to use when building decentralized applications. It can be used to store profiles and metadata, link multiple blockchain and social accounts to a single identity, read and write user verifications, and manage data on IPFS, OrbitDB, Textile, SkyDB or any other platform. This decentralized, unified, and cross-platform identity infrastructure helps Web3 projects build faster and more simply. It is also the key to realizing the vision of giving users ultimate control and portability of their information across applications and networks by breaking down information silos and putting users at the center of the web.
With IDX, every user gets a cross-platform decentralized identifier (DID) and an identity index document to which developers can attach various pieces of data relevant to their experience. Since IDX identities are public and permissionless, any developer can openly discover, query, and import data from an identity into their application, creating a rich ecosystem of information around each user.
IDX Website: https://idx.xyz
IDX Docs: https://idx.xyz/docs
IDX and Ceramic Tutorials: https://blog.ceramic.network/tag/tutorials/
Ceramic website: https://www.ceramic.network
Dev Chat: chat.idx.xyz
1000 DAI (500 each from 3Box Labs and the Ethereum Foundation)
Eth.Build currently uses 3Box to backup user sessions. This bounty is to work with Austin Griffith to replicate the backup functionality using IDX (currently in Alpha) for identity and authentication and a storage solution like Ceramic, OrbitDB, Textile ThreadsDB or SkyDB.
For this prize, we will be evaluating submissions based on:
IDX is a new cross-ecosystem decentralized identity and user data management protocol that provides for a single, unified digital identity system that works with all Web3 platforms, blockchains, and storage technologies. IDX is built on Ceramic, a peer-to-peer dataweb for publishing, linking, and querying verifiable information on the open web. IDX is currently in alpha so may be unstable.
IDX provides a flexible identity infrastructure for developers to use when building decentralized applications. It can be used to store profiles and metadata, link multiple blockchain and social accounts to a single identity, read and write user verifications, and manage data on IPFS, OrbitDB, Textile, SkyDB or any other platform. This decentralized, unified, and cross-platform identity infrastructure helps Web3 projects build faster and more simply. It is also the key to realizing the vision of giving users ultimate control and portability of their information across applications and networks by breaking down information silos and putting users at the center of the web.
With IDX, every user gets a cross-platform decentralized identifier (DID) and an identity index document to which developers can attach various pieces of data relevant to their experience. Since IDX identities are public and permissionless, any developer can openly discover, query, and import data from an identity into their application, creating a rich ecosystem of information around each user.
Eth.Build repo: https://github.com/austintgriffith/eth.build
IDX Website: https://idx.xyz
IDX Docs: https://idx.xyz/docs
IDX and Ceramic Tutorials: https://blog.ceramic.network/tag/tutorials/
Ceramic website: https://www.ceramic.network
Dev Chat: chat.idx.xyz
Review the code, but more importantly run the test and linter locally before merging the PR.
Include "network" ID.
Describe the bug
I sometimes get this error of 500 bad gateway while interacting through ceramic and it makes the user to refresh the application(retrying ceramic requests) and try again.
To Reproduce
Steps to reproduce the behavior:
1 - Using packages @ceramicnetwork/http-client, @ceramicstudio/idx, 3id-connect
2 - Sometimes, when i get the error,it's most of the time has these endpoints like -
a - https://ceramic-clay.3boxlabs.com/api/v0/documents
b - https://ceramic-clay.3boxlabs.com/api/v0/pins/
3 - There's a phase in my app where i am in need to get all the user details and so it may happens during that.
4 - Code where i think this error comes -
userDid ---> all user's DIDs
let promiseArray = [];
for(let i in userDID.data){
let DID = userDID.data[i].userDid;
promiseArray.push(blockchainDetails.idx.get('basicProfile',DID))
}
let allUsers = yield Promise.all(promiseArray);
Expected behavior
It should work as the rest of times it does,giving me the user details.
Screenshots
Ceramic versions
"@ceramicnetwork/http-client": "^0.9.3",
"@ceramicstudio/idx": "^0.7.0",
"3id-connect": "^1.0.0-alpha.13",
Machine, OS, browser information (please complete the following information):
Linux,testing on Chrome and Brave only for right now.
Additional context
It comes sometimes so not able to exactly know why is it coming.
The way of the fire
The current roadmap of Ceramic has three major milestones Slip, Clay, and Fire. Together they show the way to a live Ceramic network.
Slip is the network in it's current state. The typescript implementation is a functioning network which by default anchors records on the ropsten ethereum testnet. It has initial support for the three first doctypes: 3id, tile, and account-link. Currently it uses JWTs for signatures for making sure documents are signed by the correct owner. Most things are subject to change, but it can be used to try out the basic functionality.
The Clay testnet aims to be fully forward-compatible with the upcoming Fire mainnet release in terms of API and document data structure.
The API refactor will change some of the structure of the js-ceramic implementation, putting the core implementation and the http-client in parity. In addition to this it will make it easy to add custom doctypes, and an improved interface for interacting with documents.
In the background, improvements to the internal of js-ceramic will be made so it can properly scale while running as infrastructure.
More details can be found in the CeramicApi CIP.
To verify that the content of a document follows a specific format, schemas can be used. With schema support in Ceramic, json-schema definitions can be set on documents and will be automatically enforced. Schemas will be implemented as a feature in the 3id and tile doctypes, and will be enforced by the state transition function of the doctype. A schema will itself be defined as a Ceramic document, and when used it will be referenced by the docId and version of that schema document.
3ID Connect is the system that allows users to authenticate to 3ID identities with a blockchain account. It exposes the 3ID provider interface, which is currently used within the 3Box SDK. The 3ID provider interface is however not limited to be used within 3Box. By refactoring 3ID Connect, it will gain support to be used together with Ceramic. This will allow any user with a wallet to use Ceramic from their browsers.
JOSE is short for JSON Object Signatures and Encryption and it's a standard for just that. The dag-jose is a codec for IPLD which allows users to store signed and encrypted objects natively in IPFS. A rough spec of dag-jose can be found here: ipld/specs#251.
This milestone includes an implementation of the signature part of dag-jose in javascript, which allows js-ipfs to natively interpret these objects.
More information about dag-jose will be published in an IPLD spec soon.
Fire is the mainnet release of Ceramic. All documents created after this point will be permanently accessible in the network (given that someone pins them). The Fire release features improvements to the API, encryption support, metrics, transferrable documents, etc.
The default anchoring service configured in js-ceramic will start operating on the Ethereum mainnet. Other anchor services that operate on Ethereum or on other blockchains, such as Bitcoin etc, can be configured when a node is instantiated. It's up to each node operator to decide which anchoring service (and blockchains) they want to support.
An Ethereum Ropsten anchoring service will still be available and used for the Ceramic testnet which will continue to run in parallel with mainnet. This testnet will use a different pubsub topic to gossip updates for documents so that the data from different networks doesn't get mixed up.
Hooks are simple functions that you can add to a Ceramic node to perform actions when a document is updated. The hook will have have access to information about which document was updated, how the document content changed, and when the document was anchored.
A CIP that describes hooks in more detail will soon be available.
Currently 3ID identities in Ceramic are owned by one public key. However, in many cases there is a need to delegate the ability to act on an identity's behalf to other identities. A good example of this is a DAO. A DAO can delegate the ability to edit and update data on it's behalf (e.g. updating its profile) to one or multiple of its members. The delegate functionality will be an update to the 3id doctype that allows the owner of the 3ID to assign delegates that can sign documents on their behalf.
When running a Ceramic node it's useful to know what is happening internally in the node, what network communication is taking place, and how resources are being used. Node metrics will provide rich insight into this.
The Ceramic explorer will be a graphical interface that allows users to browse and search the graph of documents in Ceramic. The state of documents can be observed, including if they are pending or if an anchor has been confirmed. It will also be possible to view previous versions of documents using the explorer.
More information about the explorer can be found here: #12
Fibers is an improved model for conflict resolution in the Ceramic protocol. It removes the need for nodes to sync the entire history of a document, which can become quite large if there are a lot of updates. Instead only the essential parts of the document log (i.e. owner changes / key revocations) needs to be synced. This change will also allow Ceramic documents to be owned by NFTs, where only the current owner of the NFT can make updates.
A CIP that describes Ceramic fibers in more detail will soon be available.
Documents in Ceramic are usually owned by a DID or a public key. This means that changing ownership of a document is an action which is vulnerable to a double spend attack (described in detail in the specs). In most cases, this is not much of a problem because documents are centered around users. However, in some cases transferable documents are desirable. This can be enabled by allowing documents to be owned by NFTs. When a document is owned by an NFT the current owner of the token is allowed to update the document. When the NFT is transferred to a new owner, access to update the document is revoked and only the new owner can make updates. This will be implemented as an update to the 3id and the tile doctypes.
By describing a service in a service document, service providers can list their service on the Ceramic network as consumable by anyone. A service document simply describes the service's endpoint and how to use the service (inputs / outputs). It also includes information about settings, payments etc. Service documents will be flexible so that they can describe a wide range of services, including both web2 and web3 type services.
A CIP that describes service documents in more detail will be available future.
As mentioned above JOSE enables both signatures and encryption of JSON objects. Adding support for encryption in dag-jose is a critical step towards adding privacy to Ceramic. Encryption support in dag-jose enables storing encrypted data directly in IPFS. Decryption support for dag-jose could potentially be added directly into IPFS. In Ceramic, encryption will initially be used to encrypt data in documents.
Currently Ceramic relies on the 3ID provider interface. Many of the methods provided by the 3ID interface can be generalized into a DID provider. This provider will provide a generic json-rpc interface that can be shared by any DID in order to sign payloads and decrypt data encrypted to the public key of the DID. Creating this generalized provider allows wallets to support Ceramic operations in an unopinionated way using the DID method that they already use.
Having dag-jose implemented in javascript means that Ceramic only works with js-ipfs. Adding support for go-ipfs is crucial in order to make Ceramic work in as many environments as possible. The go implementation of dag-jose will start in parallel to the javascript implementation, but is expected to be delivered later.
A few tiny things I noticed going through the idx.xyz site
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.