RT @ntnsndr: @vbuterin If there is still promise in crypto, it means recognizing that the ecosystem is a commons, and it must be designed…
RT @mikarv: New 📄: “Denied by Design? Data Access Rights in Encrypted Infrastructures”. Tension: Platforms are using more edge/privacy-enha…
RT @n1ckler: Proofs of zero-knowledge often feel incomplete. For example, in Bulletproofs removing blinding values from the protocol does n…
RT @vinayvasanji: Good primer on the history of local names/petnames (in the context on online identity)
I’m increasingly coming around to…
RT @ElonkaDunin: MY BOOKS ARE HERE!!! @KlausSchmeh and I started writing in 2017, our 1st ed. came out in Dec 2020, and now here is the new…
Replying to @BrendanEich, @ben221199, @paulroales, @dwr and @balajis
The SSL v1 spec was presented at the big Crypto conference in Santa Barbara, and broken in hours. I presume that some proceedings are out there with it.
Replying to @BrendanEich, @ben221199, @paulroales, @dwr and @balajis
It looks like SSL 1.0 was never made public “due to conceptual weaknesses with regards to security” but there is a really good overview starting on p29 of “20 Years of SSL/TLS Research An Analysis of the Internet’s Security Foundation” by Christopher Meyer http://marjan.fesb.hr/~mcagalj/CNS/Lectures/SSL_TLS_20_years.pdf
I’m also a big fan of Ostrom’s Principles, which talk about the cooperative maintenance of a commons. It talks about how a community creates rules for the commons and sets boundaries to separate it from the larger environment. [4/10] http://www.lifewithalacrity.com/2015/11/a-revised-ostroms-design-principles-for-collective-governance-of-the-commons-.html
This idea came from a number of different disciplines, perhaps the most important of which is Living Systems Theory. It’s about entities that are part of a larger ecosystem and interact with it through a selective boundary. [3/10] https://en.wikipedia.org/wiki/Living_systems
I feel like this secret origin story underlines what’s really important about self-sovereign identity: individuals controlling a personal core of information, but also maintaining connections with each other as peers. [2/10]
It’s been 7 years since I wrote “The Path to Self-Sovereign Identity”. As it’s evolved, self-sovereign identity has occasionally diverged from that path. My article today thus talks about the origins and more importantly the original goals of SSI. [1/10] https://www.blockchaincommons.com/musings/origins-SSI/
But it’s also important because the self-sovereign systems that we imagined seven years ago are becoming codified today in regulations like the EU’s eIDAS, but without any understanding of what self-sovereign identity was meant to achieve. [7/10] https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation
This is especially important today because of a power shift that occurred in the ’10s, as governments handed off control of our digital identities to post-sovereignty corporations like @Google, @Facebook & @X. We had no say! [6/10]
That’s what self-sovereign identity is meant to be about: setting boundaries for the core resources of your identity. It doesn’t give you control of the ecosystem, but it does let you negotiate for your own needs as a peer. [5/10]
If you have more general interest in ensuring the future of self-sovereign identity on the internet, become a financial sponsor of Blockchain Commons [10/10]. https://github.com/sponsors/BlockchainCommons
I am now accepting new advisory retainers if your company is developing an SSI system and needs strategic insights into the pitfalls of identity. Message me directly [9/10].
What do we want from self-sovereign identity? How can we achieve those goals? How can it be more than traditional state identity in digital space? These are the questions we should be asking. I hope this article on SSI’s origins helps frame them. [8/10] https://www.blockchaincommons.com/musings/origins-SSI/
RT @real_or_random: The current @bitcoinoptech newsletter has a great field report “Field Report: Implementing MuSig2” by Brandon Black fro…
RT @jamesob: Building on a post @ajtowns wrote back in June, I’ve put together some thoughts on how bitcoin might scale to a lot of users,…
I wrote a series of rating systems articles with @Appelcline starting in 2015, where we tested our ideas with real code & community through 2017. So I appreciate this quote from @VitalikButerin’s deep dive into Twitter’s latest rating system: “Engineer’s algorithms are pragmatic… https://twitter.com/VitalikButerin/status/1691643403602407429
RT @apar1984: The term, “authoritarianism” should be used with care. But when conditions for it emerge, we should call it out without fear.…
RT @matthew_d_green: I took a look at some of the privacy decisions made by Worldcoin, the eyeball-scanning cryptocurrency. https://t.co/iN…
RT @evacide: This is your regular reminder that the data broker industry is absolutely out of control and needs strong regulation: https://…
@ShannonFogg I’m working on a book (or documentary) that includes chapters contrasting Carmille’s actions in France vs Lentz’s actions the Netherlands in WWII. The French side of this story needs more fact-checking and depth. Can I share with you a draft?
RT @a16zcrypto: Stateless blockchains – which could make being a validator so cheap that you could run a full node on a smartphone – are im…
Replying to @JWWeatherman_ and @whalesaredrones
I wish we had 90% 😉, but we have used some cycles to puzzle on it. I do think we now have a greater understanding for some better solutions for foundations that are the hardest technical parts of decentralization. The hard part is a business model for the team that is required…
Replying to @utxoclub
Can you give a presentation on this at our next Gordian Developers community call? We are focused on wallet interoperability and collaborative backup (what we call Collaborative Seed Recovery) now, but we’d like move toward approaches like yours next. https://github.com/BlockchainCommons/Gordian-Developer-Community/discussions/115