-
ens
Discontinued Implementations for ENS core functionality: The registry, registrars, and public resolvers.
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
namecoin.org
Namecoin.org website in Jekyll -- send PR's to beta branch, then merge into master and gh-pages
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
It's interesting to me the amount of energy people spend on convincing themselves that a technology (POW) that didn't even exist 12 years ago and ran on home PCs up until 7 years ago is somehow responsible for wildfires in California or deforestation in Brazil. DID has little to do with Bitcoin. I don't even know if it's the best option, but clearly the lack of decentralized identity on the web has been significant in propagating corporatist monopoly ownership and influence over the web. Nitting about an integration with one particular blockchain (DID works with multiple) is not productive and it's a distraction from the core point of the proposal.
At any rate, I've become fairly convinced at this point that something like ENS (https://ens.domains/) is better suited for a decentralized identity. Optionally registering a simple domain name via a smart contract and signing in to services with a public-private key pair (such as an Ethereum address) is a far superior experience to anything I've seen as far as simplicity goes. I don't need to give up personal contact info. I have ownership of my address. I can create new addresses if I need. And one-click sign in doesn't even require hitting the chain, just requires signing a message. It's pretty elegant. I just think it needs more standardization.
consumes more energy than most countries.
The amount of electricity PoW blockchains spend is orthogonal to the worthiness of the DID spec. That PoW spends a "staggering amount" of electricity is not a consequence of PoW blockchains' designs; it's a consequence of the governments of the world permitting it to happen.* The absolute energy use is not an intrinsic requirement for these systems -- PoW blockchains would work just the same if the world's budget for mining was only 1 KW.
I expected better from the W3C.
(Disclaimer: I am the author of one of the DID method specs).
[1] https://github.com/decentralized-identity/universal-resolver
Is someone going to reinvent Namecoin¹ and IPFS's IPNS²?
At least the abstract of the spec reads like that to me:
> Abstract
> Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. A DID refers to any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) as determined by the controller of the DID. In contrast to typical, federated identifiers, DIDs have been designed so that they may be decoupled from centralized registries, identity providers, and certificate authorities. Specifically, while other parties might be used to help enable the discovery of information related to a DID, the design enables the controller of a DID to prove control over it without requiring permission from any other party. DIDs are URIs that associate a DID subject with a DID document allowing trustable interactions associated with that subject.
> Each DID document can express cryptographic material, verification methods, or services, which provide a set of mechanisms enabling a DID controller to prove control of the DID. Services enable trusted interactions associated with the DID subject. A DID might provide the means to return the DID subject itself, if the DID subject is an information resource such as a data model.
> This document specifies the DID syntax, a common data model, core properties, serialized representations, DID operations, and an explanation of the process of resolving DIDs to the resources that they represent.
[ Source: https://www.w3.org/TR/did-core/ ]
¹ https://www.namecoin.org/
[3] https://github.com/ceramicstudio/datamodels/tree/main/packag...
Related posts
-
Irish State announce plan to build a porn preference register for most of the EU
-
ceramic VS db3 - a user suggested alternative
2 projects | 16 Jan 2023 -
We need a discovery platform for the web3?
-
An Old Timer's Tale: Segwit2x, The Block Wars: When Bitcoin Castrated the Most Powerful Players in the Ecosystem
-
Streams and schemas