Where do you put a trust registry in a decentralized digital ecosystem? Not where it turns into a wrench!

Up until recently, the majority of digital identity systems have been federated, where a small group of “identity providers” supply individuals with a digital identity that can be used to access other websites and services within the federation. Now we’re seeing the shift to decentralized identity solutions and open ecosystems based on verifiable credentials, where anyone can participate, issue, and verify.

May the government restrict DeFi (decentralized finance) tools, and force people to use third-party intermediaries, precisely to take advantage of the extra surveillance power that the third-party doctrine would provide? This question has taken on added importance in the context of emerging web3 technologies, with implications for coders, customers, and entrepreneurs.

Work under the World Wide Web Consortium (W3C) hood continues on Decentralized Identifiers (DIDs): Key Event Receipt Infrastructure to expand the reach of DIDs

These foundational principles of SSI (available in 15 languages) are intended for use by any digital identity ecosystem. Any organization is welcomed to incorporate these principles into its digital identity ecosystem governance framework provided they are included in their entirety. The principles of SSI shall be limited only by official laws and regulations that apply in a relevant jurisdiction.

Swarm is granting tokens to devlopers for promoting experimental projects using decentralized storage usage for cities.

There’s been a rather interesting disagreement between two guys from Signal and Matrix recently. Many of the points they make relating to building competitive, privacy/freedom-protecting products and the difficulties are quite relevant. Here is the original post from Signal that lead now to the response from Matrix.

The Decentralized Web Camp will be from July 18th - 21st and you are invited to join.