3A/ ION 101-401: what is ION (the public, permissionless DID network), how can you use it today, and what comes next
ION 101-401: What is ION (the Public, Permissionless DID Network), How Can You Use It Today, and What Comes Next
Tuesday 3A
Convener: Daniel Buchner (Microsoft)
Notes-taker(s): Jan Christoph Ebersbach
Tags for the session - technology discussed/ideas considered:
Identifiers, DID, ion
Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:
Decentralization of did:ion if anchoring transactions are batched by an operator: it’s possible to choose the operator or to incur the cost of anchoring the transactions. Furthermore, the operator doesn’t gain access to the private key.
ION delivers: massive scale, cost efficiency (despite running on the bitcoin network - best case if bitcoin a transaction costs 100 USD one action costs 1 cent), decentralized & flexible, decentralized registries
ION has a type system so that DIDs can be used, e.g. for software packages, vehicles, … This makes it possible to make the centralized data repositories that we rely on today, npm registries etc., to be fully decentralized. This is a Sidetree feature that is currently only used by ION.
DIF is currently working on personal data stores. Expected impact on private messaging, social media, gig services, ..
ION is live and in production today
Ion-tools is a selection of tools to interact with the ION network: https://github.com/decentralized-identity/ion-tools
Resilience of ION: It’s pointed out that not only Bitcoin needs to survive attacks but also the IPFS network as both are required for ION to work properly. With Bitcoin it looks unlikely that it’s currently possible to reverse transactions on the network. However, with IPFS data can be unpinned and potentially disappear from the network.