move for easier to think this way
This commit is contained in:
⧉ infominer
parent
9d7babb9cf
commit
0c45becd18
|
|
@ -1,3 +0,0 @@
|
|||
---
|
||||
published: false
|
||||
---
|
||||
|
|
@ -0,0 +1,7 @@
|
|||
---
|
||||
published: false
|
||||
---
|
||||
ethereum ocean ipld
|
||||
|
||||
http://www.truevaluemetrics.org/DBpdfs/BlockChain/The-IXO-Protocol-Draft-White-Paper-3.0-for-technical-review-12_8_2017.pdf
|
||||
|
||||
|
|
@ -10,6 +10,21 @@ published: false
|
|||
- [John Bradley’s Blog](https://www.thread-safe.com/)
|
||||
|
||||
|
||||
|
||||
* [Michael Becker Interviewed Kaliya re:SSI](https://identitypraxis.com/2020/11/16/an-interview-on-self-sovereign-identity-with-kaliya-young-the-identity-women/)
|
||||
> Kaliya’s purpose is to answer this profound question: “How do we own, control, manage, and represent ourselves in the digital world, independently of the BigTech companies (Facebook, Google, etc.)?”
|
||||
* [Tim Bouma is interviewed](https://medium.com/@trbouma/self-sovereign-identity-interview-with-tim-bouma-ca193f66f2bb) by SSI Ambassador - Adrian Doerk
|
||||
> Every technology is a two-edged sword, gunpowder, guns, you know anything? There’s an upside and there’s the downside. I think that’s something that we have to be very cognizant of.
|
||||
* [The Domains of Identity and SSI with “Identity Woman”](https://www.ubisecure.com/podcast/domains-of-identity-ssi-identity-woman-kaliya-young/), Kaliya Young
|
||||
> Kaliya and Oscar discuss the long-running Internet Identity Workshop (IIW) that she co-founded, the effects of moving to virtual identity conferences in 2020, insights from Kaliya’s books – ‘The Domains of Identity’, newly published in 2020, and ‘A Comprehensive Guide to Self Sovereign Identity’ – plus some great tips for all business leaders on how to view the role of identity in their organisation.
|
||||
* [Self-Sovereign Identity Authors Alex Preukschat & Shannon Appelcline](https://securetalkpodcast.com/podcast/self-sovereign-identity-alex-preukschat-shannon-appelcline/) Discussing
|
||||
> Decentralized digital identity and verifiable credentials explain what Self-Sovereign Identity (SSI) is, why it’s important, and provide examples of practical applications for individuals and organizations.
|
||||
|
||||
An academic nerdy podcast, out of [RMIT](https://www.rmit.edu.au/), Australia
|
||||
|
||||
* [Episode 6: 'Digital Identity & Blockchain' with Kaliya Young, Prof. Jason Potts, & Prof. Ellie Rennie](https://open.spotify.com/episode/4kO6VVT9PmRPrie6e5plPj)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,85 +0,0 @@
|
|||
---
|
||||
published: false
|
||||
---
|
||||
|
||||
# Highlights
|
||||
## Identosphere
|
||||
We created an [Identosphere Group on Tru.net](https://tru.net/Identosphere)
|
||||
|
||||
## History
|
||||
|
||||
* [A brief history of SSI: Where does it come from? A timeline.](https://jolocom.io/blog/a-brief-history-of-ssi-where-does-it-come-from-a-timeline/)
|
||||
|
||||
A short timeline highlights just how quickly SSI has developed. It underlines the path and development of the evolution of Internet Identity.
|
||||
|
||||
* [WAO wraps up for the holidays](https://blog.weareopen.coop/wao-wraps-up-for-the-holidays-c85bff4c910c) We Are Open Co-op
|
||||
|
||||
Great Work on Badges!
|
||||
|
||||
In May, we did some [workshopping with the crypto platform NEAR](https://weareopen.coop/near/), which was the first time we accepted cryptocurrency as part of our fee. In May, We Are Open Cooperative also [turned 5 years old](https://blog.weareopen.coop/wao-turns-five-30747f4df0f9). We celebrated this momentous occasion by launching our [new website](https://weareopen.coop/) and adding more stuff to our [free learning resource hub](https://learnwith.weareopen.coop/).
|
||||
|
||||
* [An Outlook on 2022](https://jolocom.io/blog/an-outlook-on-2022/) JoloCom
|
||||
|
||||
For us, interoperability will remain a very present topic for the next year ([https://jolocom.io/blog/can-we-avoid-a-ssi-babel/](https://jolocom.io/blog/can-we-avoid-a-ssi-babel/).
|
||||
* Christopher Allen: [Not Moxie Marlinspike](https://www.moxytongue.com/2021/09/not-moxie-marlinspike.html), Oft confused, no more.
|
||||
* [Link to a corrected attribution Devon Lofretto is not Moxie Marlinspike](https://github.com/lifewithalacrity/lifewithalacrity.github.io/commit/52c30ec1d649494066c3e9c9fa1bbaf95cd6386f)
|
||||
> Self-Sovereign Identity has deep roots. It did not just emerge in 2016 after a blog post was written. It did not fail to exist when wikipedia editors denied it subject integrity with the stated message: "good luck with that".
|
||||
|
||||
* [An Identity Through Time](https://iiw.idcommons.net/23D/_An_Identity_Through_Time) by David Schmudde
|
||||
|
||||
The history of identity online. Finger, CompuServe, DNS/WWW, Facebook
|
||||
|
||||
The slides are based on this blog post: [https://schmud.de/posts/2021-04-22-id-through-time.html](https://schmud.de/posts/2021-04-22-id-through-time.html)
|
||||
|
||||
---
|
||||
|
||||
Nothing to prevent players to take advantage of SSI. They may add something small and useful aspects to the protocols.
|
||||
|
||||
The hope is that our stuff is super interoperable. So you can actually really leave.
|
||||
|
||||
Facebook is interesting because it was based on the .edu domain. Small network. Solving for the endstate that we see now is different than starting back then.
|
||||
|
||||
Zero-knowledge proofs and trustless networks may require high-trust environments for adoptions.
|
||||
|
||||
|
||||
* [State of Identity with IDRamp](https://oneworldidentity.com/podcast/idramp-2/) (Enterprise SSI company)
|
||||
> As someone who has uniquely spent their full career immersed in identity, Mike Vesey (CEO of IdRamp) shares an insider perspective of how the industry has evolved during his tenure. This episode dives into the impacts of rapid digitalization worldwide, where identity is heading due to digital transformation, and the benefits that come with it.
|
||||
|
||||
SSI vs Santa
|
||||
|
||||
* [Phil Wolff shares](https://twitter.com/evanwolf/status/1339128612650291203):
|
||||
> In 2021 Santa decentralizes his list, no longer relying on children’s Real Names in compliance with kid privacy laws. Self-sovereign identity lets kids ask Santa, confident their identities are authenticated (right toys to the right kid) & that he uses verified naughty/nice data.
|
||||
#
|
||||
Narrative
|
||||
|
||||
Digital Caribou shares their thoughts on [Digital Transformation and inclusion](https://medium.com/caribou-digital/transformation-in-a-digital-age-9068338fd778) - very good thinking for all of us working on digital identity.
|
||||
|
||||
> We believe that the emphasis on transformation as both process and effects is particularly important, especially as although digitization and digitalization are well underway, accelerated by the response to COVID-19 (remote working, payments, etc.), these are not inevitable processes. They are the results of human decisions. Similarly, the effects of these are not inevitable, either.
|
||||
|
||||
* [Michael Becker Interviewed Kaliya re:SSI](https://identitypraxis.com/2020/11/16/an-interview-on-self-sovereign-identity-with-kaliya-young-the-identity-women/)
|
||||
> Kaliya’s purpose is to answer this profound question: “How do we own, control, manage, and represent ourselves in the digital world, independently of the BigTech companies (Facebook, Google, etc.)?”
|
||||
* [Tim Bouma is interviewed](https://medium.com/@trbouma/self-sovereign-identity-interview-with-tim-bouma-ca193f66f2bb) by SSI Ambassador - Adrian Doerk
|
||||
> Every technology is a two-edged sword, gunpowder, guns, you know anything? There’s an upside and there’s the downside. I think that’s something that we have to be very cognizant of.
|
||||
* [The Domains of Identity and SSI with “Identity Woman”](https://www.ubisecure.com/podcast/domains-of-identity-ssi-identity-woman-kaliya-young/), Kaliya Young
|
||||
> Kaliya and Oscar discuss the long-running Internet Identity Workshop (IIW) that she co-founded, the effects of moving to virtual identity conferences in 2020, insights from Kaliya’s books – ‘The Domains of Identity’, newly published in 2020, and ‘A Comprehensive Guide to Self Sovereign Identity’ – plus some great tips for all business leaders on how to view the role of identity in their organisation.
|
||||
* [Self-Sovereign Identity Authors Alex Preukschat & Shannon Appelcline](https://securetalkpodcast.com/podcast/self-sovereign-identity-alex-preukschat-shannon-appelcline/) Discussing
|
||||
> Decentralized digital identity and verifiable credentials explain what Self-Sovereign Identity (SSI) is, why it’s important, and provide examples of practical applications for individuals and organizations.
|
||||
|
||||
An academic nerdy podcast, out of [RMIT](https://www.rmit.edu.au/), Australia
|
||||
|
||||
* [Episode 6: 'Digital Identity & Blockchain' with Kaliya Young, Prof. Jason Potts, & Prof. Ellie Rennie](https://open.spotify.com/episode/4kO6VVT9PmRPrie6e5plPj)
|
||||
|
||||
## Enterprise
|
||||
|
||||
|
||||
* [Self-Sovereign Identity for the Enterprise with Switchboard](https://medium.com/energy-web-insights/unlocking-the-potential-of-self-sovereign-identity-for-enterprise-with-energy-web-switchboard-ab41499003a0) Energy Web
|
||||
|
||||
This release includes major updates to the front-end Switchboard web application as well as the back-end libraries and components, giving companies access to the full suite features offered by legacy identity access management solutions in a decentralized architecture.
|
||||
* [LEIs to enable corporate digital ID with verifiable credentials](https://www.ledgerinsights.com/lei-corporate-digital-identity-verifiable-credentials-did/)
|
||||
> The Global Legal Entity Identifier Foundation (GLEIF) is the umbrella body that delegates responsibility for issuing LEIs to local organizations.
|
||||
>
|
||||
> It’s such a pressing issue that it was raised by the OECD and B20 (G20 business) just three months ago when they suggested a [Global Value Chain (GVC) Passport](https://www.ledgerinsights.com/oecd-saudi-blockchain-business-passport-financial-compliance/).
|
||||
|
||||
* [GLEIF Press Release](https://www.gleif.org/en/newsroom/press-releases/gleif-advances-digital-trust-and-identity-for-legal-entities-globally)
|
||||
* [Layering Digital ID on Top of Traditional Data Management](https://hiplatform.org/blog/2020/5/20/layering-digital-id-on-top-of-traditional-data-management) HIP
|
||||
> While Digital ID could offer benefit to humanitarian agencies and beneficiaries, alike, many questions remain to be answered. The cost effectiveness of ID solutions remains to be established. Given that many of these systems are only operating at pilot-scale, it is difficult to know what the primary drivers of cost are and how they can be mitigated. In addition, the digital ID space is fairly young and while initiatives like ID4D and ID2020 are working to drive meaningful interoperability among providers in the space, it remains to be seen what the most effective factors, in addition to open source software, open APIs, and common data formats, can be used to general meaningful interoperability.
|
||||
|
|
@ -1,14 +0,0 @@
|
|||
# Auth0
|
||||
|
||||
* [Auth0 Identity Platform Now Available on Microsoft Azure](https://auth0.com/blog/auth0-identity-platform-now-available-on-microsoft-azure/)
|
||||
|
||||
The addition of Azure as an Auth0 private cloud platform option unlocks a secure cloud deployment option for organizations seeking strategic fit with their technology stack, supporting regional data residency capabilities and higher control over customer data.
|
||||
* [Sign-in with Decentralized Identifiers with Dock Labs](https://auth0.com/blog/sign-in-with-decentralized-identifiers-with-dock-labs/) Auth0
|
||||
|
||||
The DID and VC W3C standards are core building blocks to enable Decentralized Identity scenarios. [The Auth0 Lab team](https://twitter.com/Auth0Lab) has been following the space closely, and we're excited to support Dock with this important work.
|
||||
* [Introducing the Identity Maturity Framework](https://auth0.com/blog/introducing-the-identity-maturity-framework/) Auth0
|
||||
> we’ve consolidated our expertise and our customers’ knowledge and experiences into a solution we call the [Auth0 Identity Maturity Framework (IMF)](https://auth0.com/imf-form): a collection of tools, tactics, and expert input that will help you understand what’s working about your identity solution and what needs to change.
|
||||
* [Building an Identity Solution — Quantity Doesn’t Equal Quality](https://auth0.com/blog/building-an-identity-solution-quantity-doesnt-equal-quality/) Auth0
|
||||
|
||||
Why adding more developers to an identity project doesn’t always work out as intended
|
||||
|
||||
|
|
@ -1,371 +0,0 @@
|
|||
---
|
||||
published: false
|
||||
---
|
||||
|
||||
### CCG
|
||||
* [Open API for Interoperable Traceability](https://w3c-ccg.github.io/traceability-interop/openapi/%23overview) CCG
|
||||
> `resolve:dids - Grants permission to resolve DIDsissue:credentials - Grants permission issue Verifiable Credentialsverify:credentials - Grants permission verify Verifiable Credentialsread:credentials - Grants permission to get Verifiable Credentialsupdate:credentials - Grants permission to update the status of Verifiable Credentialsprove:presentations - Grants permission to prove Verifiable Presentationsverify:presentations - Grants permission verify Verifiable Presentationssubmit:presentations - Grants permission to submit Verifiable Presentations`
|
||||
|
||||
## Schema
|
||||
|
||||
* [Announcing Schema Markup Validator: validator.schema.org (beta)](http://blog.schema.org/2021/05/announcing-schema-markup-validator.html)
|
||||
|
||||
SDTT is a tool from Google which began life as the [Rich Snippets Testing Tool](https://developers.google.com/search/blog/2010/09/rich-snippets-testing-tool-improvements) back in 2010. Last year Google [announced plans](https://developers.google.com/search/blog/2020/07/rich-results-test-out-of-beta) to migrate from SDTT to successor tooling, the [Rich Results Test](https://search.google.com/test/rich-results), alongside plans to "deprecate the Structured Data Testing Tool". The newer Google tooling is focused on helping publishers who are targeting specific schema.org-powered [search features](https://developers.google.com/search/docs/guides/search-gallery) offered by Google, and for these purposes is a huge improvement as it contextualizes many warnings and errors to a specific target application.
|
||||
|
||||
## JWT
|
||||
|
||||
* [Beginners Guide to JWTs](https://developer.okta.com/blog/2020/12/21/beginners-guide-to-jwt)
|
||||
> A JWT is a structured security token format used to encode JSON data. The main reason to use JWT is to exchange JSON data in a way that can be cryptographically verified. There are two types of JWTs:
|
||||
> - JSON Web Signature (JWS)
|
||||
> - JSON Web Encryption (JWE)
|
||||
> The data in a JWS is public—meaning anyone with the token can read the data—whereas a JWE is encrypted and private. To read data contained within a JWE, you need both the token and a secret key.
|
||||
|
||||
## Semantics
|
||||
* [The Importance of Data Inputs and Semantics for SSI with Paul Knowles [Podcast]](https://northernblock.io/semantics-for-ssi-with-paul-knowles/)
|
||||
> The platform was an incredibly federated platform when I built it because I didn’t know that SSI existed. So as soon as I found that ecosystem, I tore up the rulebook and said, “This isn’t going to work; I have to rebuild it.”
|
||||
* [What is the VC-Generator App and How to Leverage it?](https://academy.affinidi.com/what-is-the-vc-generator-app-and-how-to-leverage-it-4fa5a54844f2)
|
||||
> In simple terms, the VC-Generator allows you to choose a credential type that needs to be issued or verified from a drop-down list and displays the associated VC schema.
|
||||
|
||||
* [https://github.com/transmute-industries/xmss](https://github.com/transmute-industries/xmss)
|
||||
|
||||
|
||||
* [Gordian QR Tool Supports Vaccine Records, 2FAs, Cryptoseeds, and More](https://www.blockchaincommons.com/projects/Releasing-QRTool/) Blockchain Commons
|
||||
> Some possible architectural issues arise from using QR codes for confidential data, such as the fact that you’re actually transmitting the data (not a proof of the data), that the QRs tend to contain all of the data (not just a selection), and that there’s no way to rescind a QR or expire it. Those issues will have to be dealt with at a foundational level as we figure out what can safely be encoded as a QR — and more importantly how to offer restricted proofs rather than complete information.
|
||||
* [Build an SSI proof of concept in <30 minutes](https://iiw.idcommons.net/21G/_Build_an_SSI_proof_of_concept_in_30_minutes) by Riley Hughes
|
||||
|
||||
The session began with a short introduction to SSI, an introduction to Trinsic, and an overview of how to get started. Then, everybody present starting building an SSI proof of concept, creating issuers, verifiers, and schemas to learn first-hand how it all works. A step-by-step guide on how to replicate this session can be found at the following link:
|
||||
|
||||
* [https://www.notion.so/trinsic/Build-an-SSI-Proof-of-Concept-dae9d6e565eb4770be41b61d55e090cb](https://www.notion.so/trinsic/Build-an-SSI-Proof-of-Concept-dae9d6e565eb4770be41b61d55e090cb)
|
||||
* [App Framework for Mobile Agent Dev - “No more forking”](https://iiw.idcommons.net/22A/_App_Framework_for_Mobile_Agent_Dev_-_%2522No_more_forking%2522) by Horacio Nunez
|
||||
|
||||
This session had the objective to present a solution to the problem of forking when developing new mobile agents. With the current starting kits available in the community it is very easy to start a path where it is almost impossible to retrofit updates to the kit back into our custom agent.
|
||||
|
||||
The solution consists in using a framework-first approach and ensuring that custom code can reside exclusively outside of the framework, thus ensuring updates can be executed more easily.
|
||||
|
||||
The following link can be used as the public url for the project:
|
||||
|
||||
* [https://www.notion.so/App-Framework-for-Mobile-Agent-Development-No-more-forking-52ebe4e5635d400eb225b0ed537404d8](https://www.notion.so/App-Framework-for-Mobile-Agent-Development-No-more-forking-52ebe4e5635d400eb225b0ed537404d8)
|
||||
|
||||
## Code
|
||||
|
||||
* [Auto-Generating Language-Specific Wrappers for Rust Libraries](https://iiw.idcommons.net/22E/_Auto-Generating_Language-Specific_Wrappers_for_Rust_Libraries) by Steve McCown
|
||||
|
||||
Rust, FFI, Code generation, language bindings, UDL
|
||||
|
||||
- Implementation of FFI that makes it easy to call Rust code
|
||||
- Define API contracts using UDL
|
||||
- Generates language specific code that’s idiomatic to the language used
|
||||
- Tutorial documentation and source code: [https://github.com/sudoplatform-labs/ffi-tutorials](https://github.com/sudoplatform-labs/ffi-tutorials)
|
||||
- Slides: [https://docs.google.com/presentation/d/183cn6NyrMUJLdid8-IoKmPZjVslmp4X0UvYIQvyeSBU/edit#slide=id.p1](https://docs.google.com/presentation/d/183cn6NyrMUJLdid8-IoKmPZjVslmp4X0UvYIQvyeSBU/edit%23slide%3Did.p1)
|
||||
* [How We Test Our Android Code at Anonyome Labs](https://anonyome.com/2021/08/insight-how-we-test-our-android-code-at-anonyome-labs/)
|
||||
|
||||
At Anonyome Labs we value well-written code that has good tests. This is a guide on how we go about producing useful and meaningful tests for our Android code. Testing approach: SDK or app?
|
||||
* [Falsehoods Programmers Believe About Names - With Examples](https://shinesolutions.com/2018/01/08/falsehoods-programmers-believe-about-names-with-examples/) Shine Solutions Group
|
||||
|
||||
In this post I’m going to list all 40 of Patrick’s original falsehoods, but give you an example (or two) drawn from my experiences working in this space. Ready? Let’s go!
|
||||
|
||||
1. People have exactly one canonical full name.
|
||||
2. People have exactly one full name which they go by.
|
||||
* [Technical Debt](https://www.continuumloop.com/technical-debt/)
|
||||
|
||||
A short note to point folks at Seth Godin’s recent podcast about Project Debt. He covers some great topics:
|
||||
|
||||
- Technical Debt – Seth covers it well but missed a major cause of technical debt. That being the shortcuts that are taken to meet deadlines and requirements – with the hope/fantasy that we’ll go back and do them right later (hint: we never do).
|
||||
- Project Debt
|
||||
- Why saying NO to those simple things may be the best thing. For some hints on how to do that see [Say No With Grace](https://www.continuumloop.com/say-no-with-grace/).
|
||||
|
||||
Give it a listen on [Overcast](https://overcast.fm/%2BL0YUSAwxA) (my fave) or [Apple Podcasts](https://podcasts.apple.com/us/podcast/project-debt/id1345042626?i%3D1000536252965).
|
||||
|
||||
* [Welcome to Dock’s API - Testnet Sandbox](https://blog.dock.io/welcome-to-docks-api-testnet-sandbox/)
|
||||
|
||||
You can test our API in the sandbox testnet by simply switching the toggle to test mode. To get started; create a free account, log into your dashboard and acquire your API key.
|
||||
* [The Journey of an SSI Developer](https://academy.affinidi.com/the-journey-of-an-ssi-developer-6ef4f642779c) Affinidi
|
||||
|
||||
## HowTo
|
||||
|
||||
* [Rendering credentials in a human-friendly way](https://medium.com/mattr-global/rendering-credentials-in-a-human-friendly-way-e47f4a32fd4b) Mattr
|
||||
|
||||
For example, this update formats address fields to make them more readable; formats names and proper nouns where possible; makes URLs, telephone numbers and email addresses clickable; highlights images and icons for better trust and brand signaling; and creates basic rules for language localization that adjust to a user’s device settings.
|
||||
* [Using Decentralized Identifiers (DIDs) Without a Digital Wallet](https://academy.affinidi.com/using-decentralized-identifiers-dids-without-a-digital-wallet-34646074ba42) Affinidi
|
||||
|
||||
there are many known DID methods, but most of them require you to have a [digital identity wallet](https://academy.affinidi.com/5-reasons-to-use-an-identity-wallet-c289ba2980cf) 🔒, where you will keep a seed ([private key](https://academy.affinidi.com/role-of-public-key-cryptography-in-self-sovereign-identity-8c2dc37a2bf3) 🔑.
|
||||
|
||||
While this may sound convenient for many of us, it comes with its shortcomings as well.
|
||||
|
||||
|
||||
|
||||
* [Introducing New Tools for Creators to Build Trusted Communities](https://www.civic.com/blog/introducing-new-tools-for-creators-to-build-trusted-communities/) CIVIC
|
||||
|
||||
Our goal is to make the process of building trust easier and more effective for creators. With that in mind, we’re sharing an overview of our plan to address the pain points of creators and marketplaces in the NFT space using identity tools.
|
||||
|
||||
|
||||
|
||||
* [An authentication system built with Ceramic & self.id](https://github.com/dabit3/decentralized-identity-example) dabit3
|
||||
|
||||
This project implements a user authentication flow leveraging an Ethereum wallet for single sign on capabilities across all of Web3.
|
||||
|
||||
The technologies used are [DID (decentralized identifiers)](https://www.w3.org/TR/did-core/), [Ceramic](https://ceramic.network/), [3id-connect](https://github.com/ceramicstudio/3id-connect), and [Self.ID](https://developers.ceramic.network/tools/self-id/overview/)
|
||||
* [DTDL models - Azure Digital Twins | Microsoft Docs](https://docs.microsoft.com/en-us/azure/digital-twins/concepts-models)
|
||||
|
||||
MSFT does know how to do to JSON-LD they just pretend not to
|
||||
|
||||
DTDL is based on JSON-LD and is programming-language independent. DTDL isn't exclusive to Azure Digital Twins, but is also used to represent device data in other IoT services such as [IoT Plug and Play](https://docs.microsoft.com/en-us/azure/iot-develop/overview-iot-plug-and-play).
|
||||
* [The Journey of an SSI Developer](https://academy.affinidi.com/the-journey-of-an-ssi-developer-6ef4f642779c) Affinidi
|
||||
|
||||
* [Building capability-based data security for Ceramic](https://blog.ceramic.network/capability-based-data-security-on-ceramic/)
|
||||
|
||||
The 3Box Labs team recently published a new standard for creating capability containers for accessing decentralized data to the Chain Agnostic Standards Alliance. Capability containers are an approach for managing advanced data security and permissions, commonly referred to as “Object Capabilities” or “OCAPs.”
|
||||
|
||||
This new standard is currently in development for use on Ceramic. Once deployed in a future version of the protocol, it will allow Ceramic to be fully compatible with the new Sign-in with Ethereum (SIWE) specification as well as provide advanced data flow control features for resources stored on the Ceramic network.
|
||||
* [Create Verifiable Credentials Without Writing a Single Line of Code](https://blog.dock.io/verifiable-credentials-without-code/) Dock
|
||||
|
||||
* [The SSI Kit](https://walt.id/blog/p/ssi-kit) Walt ID
|
||||
|
||||
Introducing the SSI Kit, which offers developers and organisations an easy and fast way to use Self-Sovereign Identity (SSI).
|
||||
|
||||
* [The human impact of identity exclusion in financial service](https://medium.com/caribou-digital/the-human-impact-of-identity-exclusion-in-financial-services-ce1e0d769389) Caribou Digital
|
||||
|
||||
we spoke to a range of participants who are or who have felt excluded from financial systems for different reasons and we’ll be sharing these stories over the next few months. This research is the foundation for Women in Identity to build an Identity Code of Conduct — a set of guiding principles and a framework for inclusive ID-product development.
|
||||
|
||||
* [Auth0 Lab](https://twitter.com/Auth0Lab/status/1468974610058137604)
|
||||
|
||||
early experiment with Sign in With Ethereum + auth0
|
||||
|
||||
usernameless + passwordless auth
|
||||
|
||||
Support for [@MetaMask](https://twitter.com/MetaMask), walletlink
|
||||
|
||||
profile enriched with ENS + NFTs through [@graphprotocol](https://twitter.com/graphprotocol)
|
||||
|
||||
Interested? discuss [https://discord.gg/rkjYHWHJ](https://t.co/dVK1CTV2JC)
|
||||
* [No Code Solution Using Self-Sovereign Identity on Redundant Blockchains](https://www.pressrelease.cc/2021/12/02/entrustient-launches-the-first-no-code-solution-for-trusted-decentralized-digital-identity-using-self-sovereign-identity-on-redundant-blockchains/) Entrustient
|
||||
|
||||
Our goal was to put the power back into the hands of users who do not have any coding knowledge or experience, to accelerate the time to configure and launch an entire Trusted Decentralized Digital Identity peer-to-peer ecosystem
|
||||
|
||||
* [tbDEX: A Liquidity Protocol v0.1](https://tbd54566975.ghost.io/introducing-tbdex/)
|
||||
|
||||
The tbDEX protocol facilitates decentralized networks of exchange between assets by providing a framework for establishing social trust, utilizing decentralized identity (DID) and verifiable credentials (VCs) to establish the provenance of identity in the real world.
|
||||
|
||||
* [How to Handle JWTs in Python](https://auth0.com/blog/how-to-handle-jwt-in-python/)
|
||||
|
||||
JSON Web Tokens, or JWTs for short, are all over the web. They can be used to track bits of information about a user in a very compact way and can be used in APIs for authorization purposes. This post will cover what JSON Web Tokens are and how to create JWTs in Python using the most popular JWT library: [PyJWT](http://pyjwt.readthedocs.io/). We are also going to see how you can sign and verify JWTs in Python using asymmetric algorithms.
|
||||
|
||||
|
||||
* [Clear is better than clever](https://dave.cheney.net/2019/07/09/clear-is-better-than-clever) Cheney.net
|
||||
|
||||
“why would I read your code?” To be clear, when I say I, I don’t mean me, I mean you. And when I say your code I also mean you, but in the third person. So really what I’m asking is, “why would you read another person’s code?”
|
||||
|
||||
* [The next architecture for building Web3 data apps](https://blog.ceramic.network/the-next-architecture-for-building-web3-data-applications/) Ceramic
|
||||
|
||||
We're replacing the popular IDX runtime with a more powerful set of tools for building applications on Ceramic including DID DataStore, DataModels, and Self.ID.
|
||||
|
||||
* [Q&A with Gravity’s lead engineer: François Guérin](https://medium.com/gravity-earth/q-a-with-gravitys-lead-engineer-fran%25C3%25A7ois-gu%25C3%25A9rin-babb3659be86)
|
||||
|
||||
As the Lead Developer, a big part of my role is to build Gravity’s decentralized identity protocol and blockchain architecture on Tezos.
|
||||
|
||||
* [PRESENTATION EXCHANGE WITH SIOP V2](https://sphereon.com/solution/dif-presentation-exchange-with-siop-v2/)
|
||||
|
||||
Sphereon has developed a Typescript/Javascript Library that implements the functionality described in the [DIF Presentation Exchange](https://identity.foundation/presentation-exchange/) specification.
|
||||
|
||||
* [Digital Identity for Development — and protection](https://medium.com/caribou-digital/digital-identity-for-development-and-protection-d92716f24bb6) Caribou Digital
|
||||
|
||||
the deployment of digital identification systems needs to get smarter about understanding the political interests and risks that shape the contexts in which identification systems are used — our [ID Ecosystem Mapping tool](https://medium.com/caribou-digital/kenyas-identification-ecosystem-7cbc2ee27) supports risk assessment arising from the deployment of digital identification systems.
|
||||
|
||||
|
||||
* [Spruce Developer Update #11](https://sprucesystems.medium.com/spruce-developer-update-11-7766b44e1075)
|
||||
|
||||
* [Developers Guide to GPG and YubiKey](https://developer.okta.com/blog/2021/07/07/developers-guide-to-gpg) Okta
|
||||
|
||||
I’ll walk through configuring a YubiKey and highlight some of the things I’ve learned along the way.
|
||||
|
||||
* [What Is an API? How APIs Work (for Non-Developers)](https://auth0.com/blog/what-is-an-api-how-apis-work-for-non-developers/) Auth0
|
||||
|
||||
Learn how APIs can accelerate software development and delivery.
|
||||
|
||||
* [Introducing SSI SDK](https://bloom.co/blog/introducing-ssi-sdk/) Bloom
|
||||
|
||||
- @bloomprotocol/vc
|
||||
- @bloomprotocol/ecdsa-secp256k1-signature-2019
|
||||
- @bloomprotocol/ecdsa-secp256k1-verification-key-2019
|
||||
- @bloomprotocol/elem-did-legacy-non-anchored
|
||||
- @bloomprotocol/waci-core
|
||||
- @bloomprotocol/waci-jose
|
||||
- @bloomprocotol/waci-kit-react
|
||||
- @bloomprotocol/presentation-exchange
|
||||
- @bloomprotocol/credential-manifest
|
||||
|
||||
* [How to write verifiable credentials in golang](https://ringaile.medium.com/how-to-write-verifiable-credentials-in-golang-7447234d5c16)
|
||||
Note: the code is written following the
|
||||
[Verifiable Credentials Data Model 1.0](https://www.w3.org/TR/vc-data-model/)
|
||||
You can find full code here:
|
||||
[https://github.com/ringaile/ver-cred](https://github.com/ringaile/ver-cred)
|
||||
|
||||
|
||||
* [Spruce Developer Update #5](https://sprucesystems.medium.com/spruce-developer-update-5-86d6f517a220)
|
||||
|
||||
This is so exciting to see what Wayne and his team are building.
|
||||
|
||||
> At Spruce, we’re building a product suite to manage all aspects of the data supply chain.
|
||||
- [Tezos DID Method](https://did-tezos-draft.spruceid.com/) - Specifies VC compatible DID creation and management
|
||||
- [DIDKit](https://sprucesystems.medium.com/introducing-didkit-an-identity-toolkit-e0dfa292f53d) - cross-platform toolkit for working with DIDs and VCs.
|
||||
- [Credible](https://medium.com/@sprucesystems/spruce-developer-update-2-484368f87ee9) - Spruce’s credential wallet.
|
||||
- Intake - onboarding tool \ secure document collection and processing.
|
||||
* [@BartHanssens shares](https://twitter.com/BartHanssens/status/1319604882068787200):
|
||||
> proofs: https://w3c-ccg.github.io/ld-proofs, cryptosuite: https://w3c-ccg.github.io/ld-cryptosuite-registry, #GnuPG: signatures https://gpg.jsld.org/contexts
|
||||
* [EPS for SSI (Self-Sovereign Identity)](https://kokumai.medium.com/eps-for-ssi-self-sovereign-identity-8c742e2b1d02)
|
||||
> In my earlier post, I failed to refer specifically to the people working for Self-Sovereign Identity and the likes of blockchain that support the distributed/decentralised storage of secrets. [...] you might all be interested to hear that the key function of Expanded Password System is to convert images to high-entropy codes that work as very long passwords and also as the seeds of symmetric/asymmetric cryptographic keys.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* [New Tools to Support Production Deployments](https://trinsic.id/new-tools-to-support-production-deployments/)
|
||||
|
||||
* [Introduction to Trinsic’s APIs](https://trinsic.id/an-introduction-to-trinsics-apis/)
|
||||
* [Provider](https://docs.trinsic.id/reference#assets) • [Credentials](https://docs.trinsic.id/reference#connections) • [Wallet](https://docs.trinsic.id/reference#connection)
|
||||
* [Building and Securing a Go and Gin Web Application](https://developer.okta.com/blog/2021/02/17/building-and-securing-a-go-and-gin-web-application) Okta
|
||||
> Today, we are going to build a simple web application that implements a to-do list. The backend will be written in Go. It will use the Go Gin Web Framework which implements a high-performance HTTP server. The front end will use the Vue.js JavaScript framework to implement a single page application (SPA). We will secure it using Okta OAuth 2.0 authentication.
|
||||
* [Dillo plugin for DID URLs](https://lists.w3.org/Archives/Public/public-credentials/2021Feb/0038.html) Charles E. Lehner
|
||||
> I would like to announce dillo-did, a plugin for the Dillo web browser implementing support for DIDs. This plugin enables navigating to DID URLs in Dillo and viewing the resolved/dereferenced DID documents and resources like web pages. The implementation of the DID functionality used is from ssi/DIDKit.
|
||||
* [Status.trinsic.id](http://status.trinsic.id/)
|
||||
> View historical uptime: Using the status page, you can see the last 90 days of uptime of all our externally-facing services. You can also inspect individual incidents and view incident reports.Be notified of incidents: By clicking the “subscribe” button in the upper-left of the screen, you can have any downtime or incidents trigger a notification to your email or Slack workspace.
|
||||
|
||||
* [Transmute releases technical workbenches](https://medium.com/transmute-techtalk/transmute-releases-technical-workbenches-892f8140ac6e) by Orie Steele, Transmute
|
||||
> This new suite of tools is available for developers to experiment with today and includes:
|
||||
>
|
||||
> - [Element Ropsten Workbench](http://staging.element.transmute.industries/)
|
||||
> - [Encrypted Data Vault Workbench](https://staging.data-vault.transmute.industries/)
|
||||
> - [DID Key Workbench](http://did.key.transmute.industries/)
|
||||
>
|
||||
> Transmute leverages these workbenches as part of our global trade solutions, where our customers benefit from verifiable data workflows and integrated capabilities.
|
||||
|
||||
|
||||
|
||||
### Code
|
||||
* [Spruce Systems introduces DIDKit](https://sprucesystems.medium.com/introducing-didkit-an-identity-toolkit-e0dfa292f53d)
|
||||
> DIDKit is a cross-platform toolkit for working with W3C Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs). It allows you to resolve and manage DID documents, and also manage the entire lifecycle of Verifiable Credentials including their issuance, presentation, and verification.
|
||||
* [A repository of JSON Schemas for Verifiable Credentials](https://github.com/rsksmart/vc-json-schemas)
|
||||
> The Credential Schema is a document that is used to guarantee the structure, and by
|
||||
* [Spruce Systems Developer Update #4](https://sprucesystems.medium.com/spruce-developer-update-4-cd6472c58fe1)
|
||||
|
||||
- The [Tezos DID Method](https://did-tezos-draft.spruceid.com/) specifies how Tezos can be used for DID creation and management, compatible with the issuance, storage, and verification of Verifiable Credentials.
|
||||
- [DIDKit](https://sprucesystems.medium.com/introducing-didkit-an-identity-toolkit-e0dfa292f53d) is a cross-platform toolkit for working with W3C Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs).
|
||||
- [Credible](https://medium.com/@sprucesystems/spruce-developer-update-2-484368f87ee9) is Spruce’s native credential wallet for the consumption, storage, and presentation of Verifiable Credentials on Android and iOS.
|
||||
- Keylink is Spruce’s tool to link existing enterprise accounts to keypairs.
|
||||
- Intake is a smarter onboarding tool for businesses via secure document collection and processing. These artifacts can then be used as evidence to generate and issue credentials to the counterparty that originally uploaded them.
|
||||
* [Create Custom Verifiable Credentials with Affinidi’s Schema Manager](https://academy.affinidi.com/create-custom-verifiable-credentials-with-affinidis-schema-manager-86149b2d49d6) Affinidi
|
||||
|
||||
Overall, the creation of a new schema type via the SDK was not a straightforward process.
|
||||
|
||||
This is where Affinidi’s [Schema Manager](http://ui.schema.affinidi.com/) comes into play
|
||||
|
||||
* [Contributing to Complex Projects](https://mitchellh.com/writing/contributing-to-complex-projects) Mitchell H
|
||||
|
||||
Inspiration - for folks engaging with new code
|
||||
|
||||
As a frequent open source maintainer and contributor, I’m often asked: where do you start? How do you approach a new project with the goal of making meaningful changes? How can you possibly understand the internals of a complex project?
|
||||
|
||||
* [Will decision making improve if we understand the bias in the decision making unit?](https://www.mydigitalfootprint.com/2022/03/will-decision-making-improve-if-we.html) My Digital Footprint
|
||||
|
||||
At the most superficial level, we know that the expectations of board members drive decisions. The decisions we take link to incentives, rewards and motivations and our shared values.
|
||||
|
||||
* [Are Transactional Relationships Enough?](https://www.windley.com/archives/2022/03/are_transactional_relationships_enough.shtml) Phil WIndley
|
||||
|
||||
Our online relationships are almost all transactional. A purely transaction digital life can't feel as rich and satisfying as one based on interactional relationships. As more of our relationships are intermediated by technology, finding ways to support interactional relationships will allow us to live authentic digital lives.
|
||||
|
||||
* [Verifiable Actions for signing and verifying VCs with DIDs](https://medium.com/@Transmute/verifiable-actions-for-signing-and-verifying-vcs-with-dids-a4176fb5ba3f) Transmute
|
||||
|
||||
This weekend I worked on making a [github action](https://github.com/features/actions) that can sign and verify verifiable credentials with decentralized identifiers.
|
||||
* [@AnastasiaU · Apr 25](https://twitter.com/AnastasiaU/status/1518568893970894848)
|
||||
|
||||
8/ Animo ([@AnimoSolutions](https://twitter.com/AnimoSolutions) is DID/VC provider working on systems and infrastructure for SSI. They built this Aries CLI so you can play around and create invitations, schemas, and credentials.
|
||||
|
||||
* [https://agent-cli.animo.id/](https://agent-cli.animo.id/)
|
||||
|
||||
* [@mfosterio · Apr 29](https://twitter.com/mfosterio/status/1520130657468440576) Twitter
|
||||
|
||||
I created a DID at [http://GoDiddy.com](https://t.co/QhwQhqUz0k) did:key:z6MkfxFPD3vwny367HZVQoqUnKatH4RTHEitcbEdvxst3nZm#z6MkfxFPD3vwny367HZVQoqUnKatH4RTHEitcbEdvxst3nZm DIDs are important in Self Sovereign Identity. You can learn about DIDs [@bluesky_commons](https://twitter.com/bluesky_commons)
|
||||
|
||||
* [Semantic Overlay Architecture](https://www.ownyourdata.eu/en/semantic-overlay-architecture/) Own Your Data
|
||||
|
||||
We have documented the [functionality of SOyA](https://ownyourdata.github.io/soya/) in a W3C-conforming Specifiation and the full source code is available under the MIT License [on Github](https://github.com/OwnYourData/soya/). Examples and an introduction how to use SOyA is [available in a dedicated Tutorial](https://github.com/OwnYourData/soya/blob/main/tutorial/README.md)
|
||||
|
||||
* [An Introduction to Verifiable Credentials](https://verifiablecredential.io/learn) VerifiableCredential.io
|
||||
|
||||
Learn about verifiable credentials, then head to the playground to view examples, explore multiple use-cases and start using them.
|
||||
* [Open Recognition is for every type of learning](https://blog.weareopen.coop/open-recognition-is-for-every-type-of-learning-ffd137a6fe17) From cold hard credentialing to warm fuzzy recognition
|
||||
|
||||
we want to explain what we talk about when we talk about Open Recognition. It builds on this [previous post](https://blog.weareopen.coop/what-is-open-recognition-anyway-9f38ec1f8629), and aims to move from the abstract to practicalities.
|
||||
|
||||
|
||||
* [Self Sovereign Identity (SSI) at T-Systems MMS: Interview mit Mujtaba Idrees, T-Systems MMS](https://www.youtube.com/watch?v%3DA311QHASy5Y) 7min video on YouTube
|
||||
|
||||
► Dr. Ivan Gudymenko, Subject Matter Lead SSI and Confidential Computing, T-Systems MMS
|
||||
|
||||
►Mujtaba Idrees, Advanced Software Engineer, T-Systems MMS
|
||||
|
||||
► [Credentials as a Service Providing Self Sovereign Identity as a Cloud Service Using Trusted Execution Environments](https://ieeexplore.ieee.org/document/9610297)
|
||||
|
||||
* [Hygiene for a computing pandemic](https://fossandcrafts.org/episodes/20-hygiene-for-a-computing-pandemic.html)
|
||||
|
||||
This episode of FOSS and Crafts features Christopher Lemmer Webber discussing the object capability security approach. Its a generalization not specific to VCs, continuing from the conversation on the CCG mailinglist, [Hygiene for a computing pandemic: separation of VCs and ocaps/zcaps](https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0028.html), we shared last month.
|
||||
|
||||
The podcast *show-notes include an epic list of references* supporting the discussion.
|
||||
|
||||
|
||||
|
||||
|
||||
* [EBSI Demo Day](https://ec.europa.eu/digital-building-blocks/wikis/display/EBSI/EBSI%2BDemo%2BDay) ([presentation](https://ec.europa.eu/digital-building-blocks/wikis/download/attachments/464979566/EBSI_Demo_Day.pdf)) ([video playlist](https://www.youtube.com/playlist?list%3DPLPMb0otsCuFLpE4UYiAZ_y3HhP2VX6q8O)
|
||||
|
||||
first time since the launch of [the Early Adopters Programme](https://ec.europa.eu/digital-building-blocks/wikis/x/DABXGw) in 2021, we are ready to showcase, in real-time and with real data, the outcomes of the EBSI multi-university pilot.
|
||||
* [Engineer your world this summer: K-University student + teacher opportunities are live!](https://kidoyo.com/join) KidOYO
|
||||
|
||||
Whether a beginning learner, or interested in advanced concepts like Game Development, Hardware Prototyping, or Competitive Coding, you will find tools, lessons and mentors
|
||||
|
||||
|
||||
* [Upgradeable Decentralized Identity - DID Method Traits](https://blog.spruceid.com/upgradeable-decentralized-identity/) SpruceID
|
||||
|
||||
DID method traits are testable properties about DID methods that can help implementers tame complexity and choose the right DID method(s) for their use case.
|
||||
|
||||
|
||||
* [Keep Badges Weird is about breaking boundaries: How the KBW community is convening systems](https://blog.weareopen.coop/keep-badges-weird-is-about-breaking-boundaries-42afb0415826) WeAreOpenCoop
|
||||
|
||||
KBW helps people understand the badge landscape. The community is there to provide solidarity for badge champions and newbies. We do not assume prior knowledge of Open Badges or Verifiable Credentials. We recognise and celebrate those who can share their experience. Anyone interested in badges or integrating [Open Recognition](https://blog.weareopen.coop/what-is-open-recognition-anyway-9f38ec1f8629) are welcome to join.
|
||||
|
||||
* [chapi.io launches, includes VC playground](https://lists.w3.org/Archives/Public/public-credentials/2022Jun/0055.html) Manu Sporny CCG
|
||||
|
||||
TL;DR: chapi.io is a site that helps developers integrate Verifiable Credential issuance, holding, and presentation into their applications. It includes a playground that can issue arbitrary VCs to digital wallets (web and native). It also includes tutorials on how Web Developers can add CHAPI integration to their websites. All you need to try it out is a web browser.
|
||||
|
||||
Interoperability
|
||||
|
||||
* [JFF & VC-EDU Plugfest #1: Leaping Towards Interoperable Verifiable Learning & Employment Records](https://kayaelle.medium.com/jff-vc-edu-plugfest-1-892b6f2c9dfb) Kayaelle
|
||||
|
||||
With this badge, they qualify to participate in Plugfest #2 which will focus on issuing and displaying LER VCs. Plugfest #2 will take place in November 2022 with plans to meet in person the day before the [Internet Identity Workshop](https://internetidentityworkshop.com/) on November 14 in Mountainview, CA. If vendors are interested in Plugfest #2 and didn’t participate in Plugfest #1, there is still an opportunity to do so by fulfilling the same requirements listed above including the video and earning a Plugfest #1 badge.
|
||||
|
||||
|
||||
* [Using a Theory of Justice to Build a Better Web3](https://www.windley.com/archives/2022/05/using_a_theory_of_justice_to_build_a_better_web3.shtml) Phil Windley
|
||||
|
||||
Summary: Building a better internet won't happen by chance or simply maximizing freedom. We have to build systems that support justice. How can we do that? Philosophy discussions are the black hole of identity. Once you get in, you can't get out. Nevertheless, I find that I'm drawn to them
|
||||
|
||||
* [Common Digital Identification Project Anonymous authentication system using Absolute Identifier & Decentralized OTP](https://www.sec.gov/comments/s7-07-22/s70722-20117318-268533.pdf)
|
||||
|
||||
* [Introducing Noir: The Universal Language of Zero-Knowledge](https://medium.com/aztec-protocol/introducing-noir-the-universal-language-of-zero-knowledge-ff43f38d86d9) Aztec Network
|
||||
|
||||
Noir is a Rust-based domain specific language (DSL) for creating and verifying zero-knowledge proofs. It’s the easiest way to write zk applications that are compatible with any proving system.
|
||||
|
||||
* [Spruce Developer Update #24](https://blog.spruceid.com/spruce-developer-update-24/)
|
||||
|
||||
- We recently added support for EIP-1271 (smart contract wallets) on our Python library ([siwe-py #30](https://github.com/spruceid/siwe-py/pull/30).
|
||||
- There is ongoing work on supporting EIP-1271 in our Rust library as well, along with an API refactor ([siwe-rs #43](https://github.com/spruceid/siwe-rs/pull/43).
|
||||
- We're updating dependencies in our NextAuth library ([siwe-next-auth-example #9](https://github.com/spruceid/siwe-next-auth-example/pull/9), [#14](https://github.com/spruceid/siwe-next-auth-example/pull/14)).
|
||||
- We're finalizing various improvements to our Sign-In with Ethereum TypeScript library toward a v2.1 release.
|
||||
* [...]
|
||||
- We're adding support for did:jwk into ssi ([ssi #466](https://github.com/spruceid/ssi/pull/466).
|
||||
- We've updated DIDKit to reflect the recent ssi refactor ([DIDKit #312](https://github.com/spruceid/didkit/pull/312).
|
||||
|
||||
Rebase
|
||||
|
||||
- We're making some additional changes and finalizing our Solana wallet flow ([rebase #32](https://github.com/spruceid/rebase/pull/32).
|
||||
|
|
@ -16,9 +16,6 @@ Decentralized identity will make our increasingly decentralized lives easier. Or
|
|||
* [@UbikomProject tweets](https://twitter.com/UbikomProject/status/1405945396208209932): “Nice overview, somewhat questionable assumptions”
|
||||
* [To Succeed In Decentralizing Digital Identity, Focus On Relationships First](https://www.forbes.com/sites/forbestechcouncil/2021/06/16/to-succeed-in-decentralizing-digital-identity-focus-on-relationships-first/?sh=6f133ef11824)
|
||||
> 2020 forced the world of identity to step up, and it has. There's much more innovation on the horizon to look forward to.
|
||||
* [We Told You So: Apple’s New Privacy Changes Validate What We’ve Done For Years](https://anonyome.com/2021/07/we-told-you-so-apples-new-privacy-changes-validate-what-weve-done-for-years/) Anonyme
|
||||
|
||||
Privacy changes from big tech are coming thick and fast right now.
|
||||
* [Is Self-Sovereign Identity Going Exponential?](https://corporate.sybrin.com/webinar-SSI) Sybrin
|
||||
|
||||
Watch the [first episode](https://www.youtube.com/watch?v%3DxWy0rP8uTiU) of #GameChangers, hosted by [Colin Iles](https://www.linkedin.com/in/coliniles/), sponsored by Sybrin. He asks the question: "Is self-sovereign identity going exponential?" Together with [Andrew Baker](https://www.linkedin.com/in/andrew-baker-b1357939/), Head of EC2 Engineering at AWS, and [Lohan Spies](https://www.linkedin.com/in/lohanspies/), Chair of the [Sovrin Steward Council](https://sovrin.org/join-the-new-sovrin-steward-council/), they explore the concept of Self-Sovereign Identity (SSI) in detail, discussing what profound implications SSI will have and whether it is indeed the next game changer?
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
# Auth0
|
||||
|
||||
* [Auth0 Lab](https://twitter.com/Auth0Lab/status/1468974610058137604)
|
||||
|
||||
early experiment with Sign in With Ethereum + auth0
|
||||
|
||||
usernameless + passwordless auth
|
||||
|
||||
Support for [@MetaMask](https://twitter.com/MetaMask), walletlink
|
||||
|
||||
profile enriched with ENS + NFTs through [@graphprotocol](https://twitter.com/graphprotocol)
|
||||
* [What Is an API? How APIs Work (for Non-Developers)](https://auth0.com/blog/what-is-an-api-how-apis-work-for-non-developers/) Auth0
|
||||
|
||||
Learn how APIs can accelerate software development and delivery.
|
||||
|
||||
* [How to Handle JWTs in Python](https://auth0.com/blog/how-to-handle-jwt-in-python/)
|
||||
> JSON Web Tokens, or JWTs for short, are all over the web. They can be used to track bits of information about a user in a very compact way and can be used in APIs for authorization purposes. This post will cover what JSON Web Tokens are and how to create JWTs in Python using the most popular JWT library: [PyJWT](http://pyjwt.readthedocs.io/). We are also going to see how you can sign and verify JWTs in Python using asymmetric algorithms.
|
||||
* [Auth0 Identity Platform Now Available on Microsoft Azure](https://auth0.com/blog/auth0-identity-platform-now-available-on-microsoft-azure/)
|
||||
|
||||
The addition of Azure as an Auth0 private cloud platform option unlocks a secure cloud deployment option for organizations seeking strategic fit with their technology stack, supporting regional data residency capabilities and higher control over customer data.
|
||||
* [Sign-in with Decentralized Identifiers with Dock Labs](https://auth0.com/blog/sign-in-with-decentralized-identifiers-with-dock-labs/) Auth0
|
||||
|
||||
The DID and VC W3C standards are core building blocks to enable Decentralized Identity scenarios. [The Auth0 Lab team](https://twitter.com/Auth0Lab) has been following the space closely, and we're excited to support Dock with this important work.
|
||||
* [Introducing the Identity Maturity Framework](https://auth0.com/blog/introducing-the-identity-maturity-framework/) Auth0
|
||||
> we’ve consolidated our expertise and our customers’ knowledge and experiences into a solution we call the [Auth0 Identity Maturity Framework (IMF)](https://auth0.com/imf-form): a collection of tools, tactics, and expert input that will help you understand what’s working about your identity solution and what needs to change.
|
||||
* [Building an Identity Solution — Quantity Doesn’t Equal Quality](https://auth0.com/blog/building-an-identity-solution-quantity-doesnt-equal-quality/) Auth0
|
||||
|
||||
Why adding more developers to an identity project doesn’t always work out as intended
|
||||
|
||||
* [Podcast] [Privacy-preserving measures and SD-JWT with Daniel Fett](https://identityunlocked.auth0.com/public/49/Identity%252C-Unlocked.--bed7fada/3bbcbab8) IdentityUnlocked Auth0
|
||||
|
||||
The discussion gets very concrete when Daniel describes selective disclosure JWT, or SD-JWT, a new IETF specification he is coauthoring that offers a simple and easy-to-adopt approach to produce JWTs capable of supporting selective disclosure. Here at Identity, Unlocked, we are huge fans of this new specification, and we hope this episode will help you get started!
|
||||
|
|
@ -17,6 +17,17 @@ Auth0 will operate as an independent unit inside of Okta, and both platforms wil
|
|||
* [Implement Client Credentials with Kong Konnect and Okta](https://developer.okta.com/blog/2021/05/25/client-credentials-kong-konnect)
|
||||
> The OIDC plugin enables Kong, as the API gateway, to communicate with Okta via the OAuth/OIDC flows.
|
||||
|
||||
* [Beginners Guide to JWTs](https://developer.okta.com/blog/2020/12/21/beginners-guide-to-jwt)
|
||||
> A JWT is a structured security token format used to encode JSON data. The main reason to use JWT is to exchange JSON data in a way that can be cryptographically verified. There are two types of JWTs:
|
||||
> - JSON Web Signature (JWS)
|
||||
> - JSON Web Encryption (JWE)
|
||||
> The data in a JWS is public—meaning anyone with the token can read the data—whereas a JWE is encrypted and private. To read data contained within a JWE, you need both the token and a secret key.
|
||||
* [Developers Guide to GPG and YubiKey](https://developer.okta.com/blog/2021/07/07/developers-guide-to-gpg) Okta
|
||||
|
||||
I’ll walk through configuring a YubiKey and highlight some of the things I’ve learned along the way.
|
||||
* [Building and Securing a Go and Gin Web Application](https://developer.okta.com/blog/2021/02/17/building-and-securing-a-go-and-gin-web-application) Okta
|
||||
> Today, we are going to build a simple web application that implements a to-do list. The backend will be written in Go. It will use the Go Gin Web Framework which implements a high-performance HTTP server. The front end will use the Vue.js JavaScript framework to implement a single page application (SPA). We will secure it using Okta
|
||||
|
||||
### Kuppinger Cole Comment: [Okta & Auth0](https://www.kuppingercole.com/blog/tolbert/okta-auth0)
|
||||
|
||||
Here are the strengths each has:
|
||||
|
|
@ -26,6 +26,9 @@
|
|||
> The most recent FATF updated draft guidance from March 2021 introduces significant changes to the legal definition of DeFi platforms, expanding the types of entities that fall under FATF's umbrella. In this guidance, FATF defines most operators of decentralized finance platforms as “Virtual Asset Service Providers” that have AML/CFT obligations.
|
||||
* [@ilanolkies](https://twitter.com/ilanolkies) shares: *Okey, so, today I mapped the work done in the last 3 month by [@rif_os](https://twitter.com/rif_os) about Self-Sovereign Identity protocols in a single link [https://github.com/rsksmart/rif-identity](https://github.com/rsksmart/rif-identity). All compatible with existent protocols and fully integrated into [@RSKsmart](https://twitter.com/RSKsmart) blockchain. The future is one step closer.*
|
||||
|
||||
* [A repository of JSON Schemas for Verifiable Credentials](https://github.com/rsksmart/vc-json-schemas)
|
||||
> The Credential Schema is a document that is used to guarantee the structure, and by
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
@ -52,6 +55,9 @@ Developed last year and launched in Q1 of 2022, the [Verite standard](https://ve
|
|||
* [Introducing Verite](https://docs.centre.io/blog/introducing-verite) Justin Hunter, Pinata, Centre
|
||||
|
||||
But as the world shifts to an increasingly digital native format, and as people take more ownership over their identity, how can the issuance of, presentation of, and verification of credentials be managed?
|
||||
* [Verification Patterns, Part 1](https://docs.centre.io/blog/verification-patterns-1) Verite
|
||||
|
||||
Since verification is off-chain (and generally fast/inexpensive, depending on the provider), and since this avoids on-chain storage of potentially correlatable data, this is often the preferred solution.
|
||||
|
||||
|
||||
|
||||
|
|
@ -208,6 +214,9 @@ Block is a new name, but our purpose of economic empowerment remains the same.
|
|||
5 years after establishing Decentralized Identity at Microsoft, where I had the opportunity to work with great folks developing open source DID infrastructure (e.g. ION), standards, and products, I am joining Square to lead Decentralized Identity.
|
||||
|
||||
### Energy Web
|
||||
* [Self-Sovereign Identity for the Enterprise with Switchboard](https://medium.com/energy-web-insights/unlocking-the-potential-of-self-sovereign-identity-for-enterprise-with-energy-web-switchboard-ab41499003a0) Energy Web
|
||||
|
||||
This release includes major updates to the front-end Switchboard web application as well as the back-end libraries and components, giving companies access to the full suite features offered by legacy identity access management solutions in a decentralized architecture.
|
||||
|
||||
* [Energy Web Quarterly Update](https://medium.com/energy-web-insights/energy-web-quarterly-update-855feb5878b6)
|
||||
|
||||
|
|
@ -0,0 +1,63 @@
|
|||
# Apple
|
||||
|
||||
* [Apple, with support from Google, just announced the Mobile Document Request API](https://github.com/WICG/proposals/issues/67) Web Incubator CG
|
||||
> The API is concerning because it lists "Define the native communication between the User Agent and the application holding the mdoc." as out of scope. That is, digital wallet selection is out of scope. Also out of scope is "issuing" and "provisioning". The specification focuses on delivery from a digital wallet to a website.
|
||||
|
||||
* [We Told You So: Apple’s New Privacy Changes Validate What We’ve Done For Years](https://anonyome.com/2021/07/we-told-you-so-apples-new-privacy-changes-validate-what-weve-done-for-years/) Anonyme
|
||||
|
||||
Privacy changes from big tech are coming thick and fast right now.
|
||||
* [Talao SSI wallet now available on Apple AppStore and Google Play](https://medium.com/@talao_io/talao-ssi-wallet-now-available-on-apple-appstore-and-google-play-1435b4a01b1c)
|
||||
|
||||
- Work on Android and iOS
|
||||
- Wallet DID: did: tz, did: key (curve Ed25519)
|
||||
- Issuer DID supported: did: tz, did: web, did: key; did: ethr, did: pkh.
|
||||
- Revocation of VCs: RevocationList2020
|
||||
- SDK development environment: PHP, Python, NodeJS, java, C, Flutter,…
|
||||
- Wallet templates: employer certificate, experience certificate, skills certificate, company pass , proof of email, proof of telephone, certificate of residence, loyalty card, diplomas, student card
|
||||
|
||||
* [iOS 15 Code Points to Biometric Onboarding for Apple’s Mobile ID](https://findbiometrics.com/ios-15-code-points-biometric-onboarding-apples-mobile-id-77202104/)
|
||||
|
||||
The iPhone’s incoming mobile ID feature will use selfie biometrics for identity verification, suggests code uncovered by 9to5Mac. The news indicates that Apple will be even more directly in competition […] The post iOS 15 Code Points to Biometric Onboarding for Apple’s Mobile ID appeared first on FindBiometrics.
|
||||
* ["Apple launches the first driver’s license and state ID in Wallet with Arizona”](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0231.html) Liam McCarty (Wednesday, 23 March)
|
||||
> It’s sad and frustrating that this isn’t based on verifiable credentials… it appears vendor lock in is going to be hard to prevent.
|
||||
>
|
||||
> For anyone who missed the November coverage about this, here’s a pretty outrageous CNBC article: "[Apple is sticking taxpayers with part of the bill for rollout of tech giant's digital ID card](https://www.cnbc.com/2021/11/14/apple-sticking-taxpayers-with-part-of-the-bill-for-digital-id-rollout.html)”
|
||||
* [Apple announces first states signed up to adopt driver’s licenses and state IDs in Apple Wallet](https://www.apple.com/newsroom/2021/09/apple-announces-first-states-to-adopt-drivers-licenses-and-state-ids-in-wallet/)
|
||||
|
||||
Arizona, Connecticut, Georgia, Iowa, Kentucky, Maryland, Oklahoma, and Utah are among the first states to bring state IDs and driver’s licenses in Wallet to their residents
|
||||
* [Apple iPhones Can Soon Hold Your ID. Privacy Experts Are On Edge](https://www.npr.org/2021/06/12/1005624457/apple-iphones-can-soon-hold-your-id-privacy-experts-are-on-edge?mc_cid%3De63363caf1%26mc_eid%3D12e697f479)
|
||||
> Elizabeth Renieris, a fellow at Stanford University who studies digital identification systems, said the feature may be easy-to-use and save time. Those conveniences, however, come at a cost: Turning every instance in which we show our ID into a business opportunity.-
|
||||
|
||||
* [Apple Confirms Biometric Onboarding for Mobile ID](https://findbiometrics.com/apple-confirms-biometric-onboarding-mobile-id-79032021/)
|
||||
|
||||
Apple has revealed a handful of states that it is working with to develop virtual, mobile driver’s licenses, and confirmed that the Transportation Security Administration will accept is mobile IDs
|
||||
|
||||
* [Apple’s Move beyond passwords](https://developer.apple.com/videos/play/wwdc2021/10106/)
|
||||
|
||||
Explore the next frontier in account security with secure-by-design, public-key-based credentials that use the Web Authentication standard. Discover in this technology preview how Apple is approaching this standard in iOS 15 and macOS Monterey.
|
||||
|
||||
* [What Apple’s WWDC PassKeys Annoucement Means for Enterprise IAM](https://www.hypr.com/what-apples-wwdc-passkeys-announcement-means-for-enterprise-iam/)
|
||||
|
||||
Apple’s approach to passwordless is not particularly unique since it adheres to the FIDO standard, however their implementation and approach to the credential recovery problem is unique and relevant to enterprises. One refreshing aspect of their messaging and stance on authentication is their dedication to eliminating shared secrets.
|
||||
|
||||
* [Apple continues to move into the identity space.](https://medium.com/global-id/gid-report-164-what-apples-missing-about-digital-identity-1d587693e285)
|
||||
|
||||
Apple’s story is more about individual convenience in service of Apple. When it comes to the Big in Big Tech, Apple’s as Big as they come — all while being renowned control freaks. Their top-down approach to digital identity isn’t about portability or interoperability, it’s about strengthening their platform moat, where Apple takes a 30 percent cut on all sales.
|
||||
|
||||
* [What US states will support Apple Wallet digital identity cards?](https://www.cnet.com/news/what-us-states-will-support-apple-wallet-digital-identity-cards/) CNet
|
||||
|
||||
* [Now Apple wants to store your driver’s license on Apple Wallet](https://mashable.com/article/apple-wallet-digital-ids-privacy-wwdc-2021/) Mashable
|
||||
|
||||
* [Apple iPhones Can Soon Hold Your ID. Privacy Experts Are On Edge](https://www.npr.org/2021/06/12/1005624457/apple-iphones-can-soon-hold-your-id-privacy-experts-are-on-edge?mc_cid%3De63363caf1%26mc_eid%3D12e697f479)
|
||||
> Elizabeth Renieris, a fellow at Stanford University who studies digital identification systems, said the feature may be easy-to-use and save time. Those conveniences, however, come at a cost: Turning every instance in which we show our ID into a business opportunity.-
|
||||
|
||||
* [Apple Confirms Biometric Onboarding for Mobile ID](https://findbiometrics.com/apple-confirms-biometric-onboarding-mobile-id-79032021/)
|
||||
|
||||
Apple has revealed a handful of states that it is working with to develop virtual, mobile driver’s licenses, and confirmed that the Transportation Security Administration will accept is mobile IDs
|
||||
|
||||
* [You’ll soon be able to use your iPhone as ID at the airport: Apple Wallet is also getting support for hotel keys](https://www.theverge.com/2021/6/7/22522864/apple-wallet-iphone-airport-ids-hotel-key-card-ios-15-wwdc)
|
||||
|
||||
Apple has announced a forthcoming update to its Wallet app that will allow you to use your iPhone as digital identification in select US airports. The company showed how you’ll be able to scan your driver’s license or state ID in participating US states, which will then be encrypted and stored in the iPhone’s secure enclave. The company says it’s working with the TSA to enable the iPhone to be used as identification at airport security checkpoints.
|
||||
* [Apple vs (or plus) Adtech, Part II](https://blogs.harvard.edu/doc/2021/05/30/apple-vs-or-plus-adtech-part-ii/)
|
||||
|
||||
To review… in Settings—> Privacy—> Tracking, is a single OFF/ON switch for “Allow Ads to Request to Track.” It is by default set to ON.
|
||||
|
|
@ -1,6 +1,11 @@
|
|||
# Microsoft
|
||||
|
||||
## Azure AD
|
||||
* [DTDL models - Azure Digital Twins | Microsoft Docs](https://docs.microsoft.com/en-us/azure/digital-twins/concepts-models)
|
||||
|
||||
MSFT does know how to do to JSON-LD they just pretend not to
|
||||
|
||||
DTDL is based on JSON-LD and is programming-language independent. DTDL isn't exclusive to Azure Digital Twins, but is also used to represent device data in other IoT services such as [IoT Plug and Play](https://docs.microsoft.com/en-us/azure/iot-develop/overview-iot-plug-and-play).
|
||||
* [Expanding the public preview of verifiable credentials](https://techcommunity.microsoft.com/t5/azure-active-directory-identity/expanding-the-public-preview-of-verifiable-credentials/ba-p/3295508) Ankur Patel Microsoft Identity
|
||||
|
||||
more than 1,000 enterprises with premium subscriptions have issued and verified tens of thousands of verifiable credentials […] from [remote onboarding at work,](https://go.microsoft.com/fwlink/p/?LinkID%3D2184957%26clcid%3D0x409%26culture%3Den-us%26country%3DUS) [collaboration across business boundaries](https://customers.microsoft.com/en-us/story/1478082375112165122-avanade-partner-professional-services-verifiable-credentials) as well as [enabling education beyond the campus](https://customers.microsoft.com/en-us/story/1481006006183422060-rmit-university-higher-education-azure-active-directory?culture%3Den-us%26country%3DUS) [...] we are extending the public preview […] for all Azure Active Directory (Azure AD) Free and Premium users.
|
||||
|
|
@ -1,5 +1,10 @@
|
|||
# Animo
|
||||
|
||||
* [@AnastasiaU · Apr 25](https://twitter.com/AnastasiaU/status/1518568893970894848)
|
||||
|
||||
8/ Animo ([@AnimoSolutions](https://twitter.com/AnimoSolutions) is DID/VC provider working on systems and infrastructure for SSI. They built this Aries CLI so you can play around and create invitations, schemas, and credentials.
|
||||
|
||||
* [https://agent-cli.animo.id/](https://agent-cli.animo.id/)
|
||||
* [https://demo.animo.id/](https://demo.animo.id/)
|
||||
|
||||
It allows people to experience SSI first-hand by choosing a character and 'playing' through their unique use cases. The student can enrol in college, visit a club or join a gym, while the business woman can attend a conference and check into a hotel for example. It was built with Aries Framework JavaScript's REST API and supports the Lissi and the Trinsic wallet
|
||||
|
|
@ -1,5 +1,17 @@
|
|||
# Anonoyome - MySudo
|
||||
|
||||
* [Auto-Generating Language-Specific Wrappers for Rust Libraries](https://iiw.idcommons.net/22E/_Auto-Generating_Language-Specific_Wrappers_for_Rust_Libraries) by Steve McCown
|
||||
|
||||
Rust, FFI, Code generation, language bindings, UDL
|
||||
|
||||
- Implementation of FFI that makes it easy to call Rust code
|
||||
- Define API contracts using UDL
|
||||
- Generates language specific code that’s idiomatic to the language used
|
||||
- Tutorial documentation and source code: [https://github.com/sudoplatform-labs/ffi-tutorials](https://github.com/sudoplatform-labs/ffi-tutorials)
|
||||
- Slides: [https://docs.google.com/presentation/d/183cn6NyrMUJLdid8-IoKmPZjVslmp4X0UvYIQvyeSBU/edit#slide=id.p1](https://docs.google.com/presentation/d/183cn6NyrMUJLdid8-IoKmPZjVslmp4X0UvYIQvyeSBU/edit%23slide%3Did.p1)
|
||||
* [How We Test Our Android Code at Anonyome Labs](https://anonyome.com/2021/08/insight-how-we-test-our-android-code-at-anonyome-labs/)
|
||||
|
||||
At Anonyome Labs we value well-written code that has good tests. This is a guide on how we go about producing useful and meaningful tests for our Android code. Testing approach: SDK or app?
|
||||
- [We’ve Introduced the Sudo Platform Decentralized Identity Relay](https://anonyome.com/2022/06/weve-introduced-the-sudo-platform-decentralized-identity-relay/)
|
||||
* [Whitepaper – Innovating Identity and Access Management with Decentralized Identity](https://anonyome.com/2022/08/whitepaper-innovating-identity-and-access-management-with-decentralized-identity/)
|
||||
* [Dr Paul Ashley Presents on How to Solve the Privacy Problem](https://anonyome.com/2021/05/dr-paul-ashley-presents-on-how-to-solve-the-privacy-problem/) Anonyome
|
||||
|
|
@ -1,5 +1,10 @@
|
|||
# DOCK
|
||||
|
||||
* [Welcome to Dock’s API - Testnet Sandbox](https://blog.dock.io/welcome-to-docks-api-testnet-sandbox/)
|
||||
|
||||
You can test our API in the sandbox testnet by simply switching the toggle to test mode. To get started; create a free account, log into your dashboard and acquire your API key.
|
||||
|
||||
* [Create Verifiable Credentials Without Writing a Single Line of Code](https://blog.dock.io/verifiable-credentials-without-code/) Dock
|
||||
|
||||
* [Dock DIDs Now Support Multiple Key Pairs](https://blog.dock.io/dids-multikey-support/) Dock
|
||||
|
||||
|
|
@ -32,3 +32,41 @@ TreeLDR is an open-source developer tool with a DSL that makes managing data sch
|
|||
Our open banking platform is guided by our [data responsibility principles](https://www.mastercard.com/news/perspectives/2022/data-responsibility-and-inclusion/). Mastercard
|
||||
|
||||
|
||||
* [Spruce Developer Update #11](https://sprucesystems.medium.com/spruce-developer-update-11-7766b44e1075)
|
||||
* [Spruce Developer Update #5](https://sprucesystems.medium.com/spruce-developer-update-5-86d6f517a220)
|
||||
> This is so exciting to see what Wayne and his team are building.
|
||||
>
|
||||
> > At Spruce, we’re building a product suite to manage all aspects of the data supply chain.
|
||||
- [Tezos DID Method](https://did-tezos-draft.spruceid.com/) - Specifies VC compatible DID creation and management
|
||||
- [DIDKit](https://sprucesystems.medium.com/introducing-didkit-an-identity-toolkit-e0dfa292f53d) - cross-platform toolkit for working with DIDs and VCs.
|
||||
- [Credible](https://medium.com/@sprucesystems/spruce-developer-update-2-484368f87ee9) - Spruce’s credential wallet.
|
||||
- Intake - onboarding tool \ secure document collection and processing.
|
||||
* [Spruce Systems introduces DIDKit](https://sprucesystems.medium.com/introducing-didkit-an-identity-toolkit-e0dfa292f53d)
|
||||
> DIDKit is a cross-platform toolkit for working with W3C Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs). It allows you to resolve and manage DID documents, and also manage the entire lifecycle of Verifiable Credentials including their issuance, presentation, and verification.
|
||||
* [Spruce Systems Developer Update #4](https://sprucesystems.medium.com/spruce-developer-update-4-cd6472c58fe1)
|
||||
- The [Tezos DID Method](https://did-tezos-draft.spruceid.com/) specifies how Tezos can be used for DID creation and management, compatible with the issuance, storage, and verification of Verifiable Credentials.
|
||||
- [DIDKit](https://sprucesystems.medium.com/introducing-didkit-an-identity-toolkit-e0dfa292f53d) is a cross-platform toolkit for working with W3C Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs).
|
||||
- [Credible](https://medium.com/@sprucesystems/spruce-developer-update-2-484368f87ee9) is Spruce’s native credential wallet for the consumption, storage, and presentation of Verifiable Credentials on Android and iOS.
|
||||
- Keylink is Spruce’s tool to link existing enterprise accounts to keypairs.
|
||||
- Intake is a smarter onboarding tool for businesses via secure document collection and processing. These artifacts can then be used as evidence to generate and issue credentials to the counterparty that originally uploaded them.
|
||||
|
||||
* [Upgradeable Decentralized Identity - DID Method Traits](https://blog.spruceid.com/upgradeable-decentralized-identity/) SpruceID
|
||||
|
||||
DID method traits are testable properties about DID methods that can help implementers tame complexity and choose the right DID method(s) for their use case.
|
||||
* [Spruce Developer Update #24](https://blog.spruceid.com/spruce-developer-update-24/)
|
||||
|
||||
- We recently added support for EIP-1271 (smart contract wallets) on our Python library ([siwe-py #30](https://github.com/spruceid/siwe-py/pull/30).
|
||||
- There is ongoing work on supporting EIP-1271 in our Rust library as well, along with an API refactor ([siwe-rs #43](https://github.com/spruceid/siwe-rs/pull/43).
|
||||
- We're updating dependencies in our NextAuth library ([siwe-next-auth-example #9](https://github.com/spruceid/siwe-next-auth-example/pull/9), [#14](https://github.com/spruceid/siwe-next-auth-example/pull/14)).
|
||||
- We're finalizing various improvements to our Sign-In with Ethereum TypeScript library toward a v2.1 release.
|
||||
* [...]
|
||||
- We're adding support for did:jwk into ssi ([ssi #466](https://github.com/spruceid/ssi/pull/466).
|
||||
- We've updated DIDKit to reflect the recent ssi refactor ([DIDKit #312](https://github.com/spruceid/didkit/pull/312).
|
||||
|
||||
Rebase
|
||||
|
||||
- We're making some additional changes and finalizing our Solana wallet flow ([rebase #32](https://github.com/spruceid/rebase/pull/32).
|
||||
|
||||
* [Sign in with Ethereum](https://login.xyz/) is being developed by Spruce
|
||||
|
||||
Already used throughout web3, this is an effort to standardize the method with best practices and to make it easier for web2 services to adopt it.
|
||||
|
|
@ -1,5 +1,8 @@
|
|||
# TBD - Bluesky
|
||||
|
||||
* [tbDEX: A Liquidity Protocol v0.1](https://tbd54566975.ghost.io/introducing-tbdex/)
|
||||
|
||||
The tbDEX protocol facilitates decentralized networks of exchange between assets by providing a framework for establishing social trust, utilizing decentralized identity (DID) and verifiable credentials (VCs) to establish the provenance of identity in the real world.
|
||||
* [A Self-Authenticating Social Protocol](https://blueskyweb.xyz/blog/3-6-2022-a-self-authenticating-social-protocol) Bluesky
|
||||
|
||||
In law, a [“self-authenticating” document](https://www.law.cornell.edu/rules/fre/rule_902) requires no extrinsic evidence of authenticity. In computer science, an [“authenticated data structure”](https://www.cs.umd.edu/~mwh/papers/gpads.pdf) can have its operations independently verifiable. When resources in a network can attest to their own authenticity, then that data is inherently live – that is, canonical and transactable – no matter where it is located.
|
||||
|
|
@ -1,5 +1,23 @@
|
|||
# Transmute Industries
|
||||
|
||||
* [https://github.com/transmute-industries/xmss](https://github.com/transmute-industries/xmss)
|
||||
* [Transmute releases technical workbenches](https://medium.com/transmute-techtalk/transmute-releases-technical-workbenches-892f8140ac6e) by Orie Steele, Transmute
|
||||
> This new suite of tools is available for developers to experiment with today and includes:
|
||||
>
|
||||
> - [Element Ropsten Workbench](http://staging.element.transmute.industries/)
|
||||
> - [Encrypted Data Vault Workbench](https://staging.data-vault.transmute.industries/)
|
||||
> - [DID Key Workbench](http://did.key.transmute.industries/)
|
||||
>
|
||||
> Transmute leverages these workbenches as part of our global trade solutions, where our customers benefit from verifiable data workflows and integrated capabilities.
|
||||
|
||||
* [Verifiable Presentation Personas: Certifiers, Consolidators, & Submitters](https://medium.com/@Transmute/verifiable-presentation-personas-certifiers-consolidators-submitters-b38a281eb92f) Transmute
|
||||
|
||||
The arrow for “Issue Credentials” is exactly the same as “Send Presentation,” leading us to believe these activities are similar, but how are they similar? We can’t adequately answer these questions by looking at the above picture and the specification doesn’t provide a ton of help either…
|
||||
|
||||
|
||||
* [Verifiable Actions for signing and verifying VCs with DIDs](https://medium.com/@Transmute/verifiable-actions-for-signing-and-verifying-vcs-with-dids-a4176fb5ba3f) Transmute
|
||||
|
||||
This weekend I worked on making a [github action](https://github.com/features/actions) that can sign and verify verifiable credentials with decentralized identifiers.
|
||||
* [Transmute Closes $2M Seed Round](https://medium.com/transmute-techtalk/transmute-closes-2m-seed-round-a0a2e6c90467) this week. This is fantastic news for them and the whole ecosystem. Transmute is a great company developing products for supply chain use-cases and is collaborating with GS1. They also are part of the SVIP (Silicon Valley Innovation program) lead by Anil John. *Full disclosure Kaliya has a formal advising relationship with Transmute.*
|
||||
* [Identity Terms Provide Value along the Supply Chain: How We Know When to Buy the Farm](https://medium.com/@Transmute/identity-terms-provide-value-along-the-supply-chain-how-we-know-when-to-buy-the-farm-738701967e3d) Jessica Tacka, Transmute
|
||||
> Supply chain credentialing in the form of bills of lading, certificates of origin, or letters of credit is used to protect honest parties and their merchandise from being confused with dishonest parties or entities that are engaged in unethical practices, such as environmental destruction, or forced labor.
|
||||
|
|
@ -1,5 +1,16 @@
|
|||
# trinsic
|
||||
|
||||
* [Build an SSI proof of concept in <30 minutes](https://iiw.idcommons.net/21G/_Build_an_SSI_proof_of_concept_in_30_minutes) by Riley Hughes
|
||||
|
||||
The session began with a short introduction to SSI, an introduction to Trinsic, and an overview of how to get started. Then, everybody present starting building an SSI proof of concept, creating issuers, verifiers, and schemas to learn first-hand how it all works. A step-by-step guide on how to replicate this session can be found at the following link:
|
||||
|
||||
* [https://www.notion.so/trinsic/Build-an-SSI-Proof-of-Concept-dae9d6e565eb4770be41b61d55e090cb](https://www.notion.so/trinsic/Build-an-SSI-Proof-of-Concept-dae9d6e565eb4770be41b61d55e090cb)
|
||||
* [New Tools to Support Production Deployments](https://trinsic.id/new-tools-to-support-production-deployments/)
|
||||
|
||||
* [Introduction to Trinsic’s APIs](https://trinsic.id/an-introduction-to-trinsics-apis/)
|
||||
* [Provider](https://docs.trinsic.id/reference#assets) • [Credentials](https://docs.trinsic.id/reference#connections) • [Wallet](https://docs.trinsic.id/reference#connection)
|
||||
* [Status.trinsic.id](http://status.trinsic.id/)
|
||||
> View historical uptime: Using the status page, you can see the last 90 days of uptime of all our externally-facing services. You can also inspect individual incidents and view incident reports.Be notified of incidents: By clicking the “subscribe” button in the upper-left of the screen, you can have any downtime or incidents trigger a notification to your email or Slack workspace.
|
||||
* [How Yoma Uses Trinsic to Help African Youth Build Digital CVs](https://trinsic.id/customer-story-yoma/)
|
||||
|
||||
Verifiable credentials is a beautiful set of technology that allows people and organizations to get the data in a verifiable form that still respects agency.”
|
||||
|
|
@ -12,3 +12,8 @@ FlexID is giving users a blockchain wallet that stores their verificable credent
|
|||
* [Local digital identity startup FlexID receives funding from Algorand Foundation](https://www.techzim.co.zw/2022/05/local-digital-identity-startup-flexid-receives-funding-from-algorand-foundation/) TechZim
|
||||
|
||||
Zimbabwean founded blockchain start-up, [FlexID Technologies](https://www.flexfintx.com/) (formerly FlexFinTx), has signed a Simple Agreement For Equity (SAFE) with the [Algorand Foundation](https://www.algorand.com/), to further develop and scale their Self Sovereign Identity (SSI) platform
|
||||
|
||||
### Gravity Earth
|
||||
* [Q&A with Gravity’s lead engineer: François Guérin](https://medium.com/gravity-earth/q-a-with-gravitys-lead-engineer-fran%25C3%25A7ois-gu%25C3%25A9rin-babb3659be86)
|
||||
|
||||
As the Lead Developer, a big part of my role is to build Gravity’s decentralized identity protocol and blockchain architecture on Tezos.
|
||||
|
|
@ -7,6 +7,19 @@ we can expect more awareness and adoption in five years because of the enormous
|
|||
* [An Overview of Affinidi’s Terms of Use for Developers](https://academy.affinidi.com/an-overview-of-affinidis-terms-of-use-for-developers-fa7a04bcf635) Affinidi
|
||||
|
||||
This article provides an overview of our [Terms of Use](https://www.affinidi.com/developer-terms-of-use) for any developer who wants to use our APIs and SDKs.
|
||||
* [What is the VC-Generator App and How to Leverage it?](https://academy.affinidi.com/what-is-the-vc-generator-app-and-how-to-leverage-it-4fa5a54844f2)
|
||||
> In simple terms, the VC-Generator allows you to choose a credential type that needs to be issued or verified from a drop-down list and displays the associated VC schema.
|
||||
* [Create Custom Verifiable Credentials with Affinidi’s Schema Manager](https://academy.affinidi.com/create-custom-verifiable-credentials-with-affinidis-schema-manager-86149b2d49d6) Affinidi
|
||||
|
||||
Overall, the creation of a new schema type via the SDK was not a straightforward process.
|
||||
|
||||
This is where Affinidi’s [Schema Manager](http://ui.schema.affinidi.com/) comes into play
|
||||
* [Using Decentralized Identifiers (DIDs) Without a Digital Wallet](https://academy.affinidi.com/using-decentralized-identifiers-dids-without-a-digital-wallet-34646074ba42) Affinidi
|
||||
|
||||
there are many known DID methods, but most of them require you to have a [digital identity wallet](https://academy.affinidi.com/5-reasons-to-use-an-identity-wallet-c289ba2980cf) 🔒, where you will keep a seed ([private key](https://academy.affinidi.com/role-of-public-key-cryptography-in-self-sovereign-identity-8c2dc37a2bf3) 🔑.
|
||||
|
||||
While this may sound convenient for many of us, it comes with its shortcomings as well.
|
||||
* [The Journey of an SSI Developer](https://academy.affinidi.com/the-journey-of-an-ssi-developer-6ef4f642779c) Affinidi
|
||||
|
||||
* [Singapore Fintech Festival…Here We [Affinidi] Come!](https://academy.affinidi.com/singapore-fintech-festival-here-we-come-d8ffb59bc1cf)
|
||||
|
||||
|
|
@ -4,6 +4,11 @@
|
|||
> This is a significant undertaking for both IATA and the other parties involved. As part of MATTR’s role in supporting this initiative, we developed a series of educational videos in partnership with IATA to explain the value and mechanics of a decentralised identity ecosystem.
|
||||
* [Why we’re launching MATTR VII](https://medium.com/mattr-global/launching-mattr-vii-4e11bcb9aaef)
|
||||
> Inspired by the [seven states of matter](https://en.wikipedia.org/wiki/State_of_matter), our platform gives builders and developers all the tools they need at their fingertips to create a whole new universe of decentralized products and applications. We provide all the raw technical building blocks to allow you to create exactly what you have in mind. MATTR VII is composable and configurable to fit your needs, whether you’re a well-established business with legacy systems or a start-up looking to build the next best thing in digital privacy. Best of all, MATTR VII is use-case-agnostic, meaning we’ve baked minimal dependencies into our products so you can use them the way that makes the most sense for you.
|
||||
|
||||
* [Rendering credentials in a human-friendly way](https://medium.com/mattr-global/rendering-credentials-in-a-human-friendly-way-e47f4a32fd4b) Mattr
|
||||
|
||||
For example, this update formats address fields to make them more readable; formats names and proper nouns where possible; makes URLs, telephone numbers and email addresses clickable; highlights images and icons for better trust and brand signaling; and creates basic rules for language localization that adjust to a user’s device settings.
|
||||
|
||||
* [ARUCC is pleased to announce a partnership between Digitary, its service partner, and MATTR, a friend of MyCreds™](https://mycreds.ca/2021/04/14/bridging-today-and-tomorrow-ensuring-self-sovereignty-for-learners-through-aruccs-mycreds/).
|
||||
|
||||
These two international organizations are combining their talents to deliver SSI (self-sovereign identity) and Verifiable Credentials for the ARUCC [MyCreds™](https://mycreds.ca/) virtual wallet. This groundbreaking work means the Canadian [MyCreds™](https://mycreds.ca/) credential wallet along with other international members of the Digitary global network will be able to reach an even higher bar of service delivery for mobile learners, creating a triangle of trust that includes them and the Canadian colleges and universities.
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
# WaltID
|
||||
|
||||
* [The SSI Kit](https://walt.id/blog/p/ssi-kit) Walt ID
|
||||
|
||||
Introducing the SSI Kit, which offers developers and organisations an easy and fast way to use Self-Sovereign Identity (SSI).
|
||||
|
|
@ -0,0 +1,41 @@
|
|||
---
|
||||
published: false
|
||||
---
|
||||
# History
|
||||
|
||||
* [A brief history of SSI: Where does it come from? A timeline.](https://jolocom.io/blog/a-brief-history-of-ssi-where-does-it-come-from-a-timeline/)
|
||||
|
||||
A short timeline highlights just how quickly SSI has developed. It underlines the path and development of the evolution of Internet Identity.
|
||||
|
||||
|
||||
* [An Outlook on 2022](https://jolocom.io/blog/an-outlook-on-2022/) JoloCom
|
||||
|
||||
For us, interoperability will remain a very present topic for the next year ([https://jolocom.io/blog/can-we-avoid-a-ssi-babel/](https://jolocom.io/blog/can-we-avoid-a-ssi-babel/).
|
||||
* Christopher Allen: [Not Moxie Marlinspike](https://www.moxytongue.com/2021/09/not-moxie-marlinspike.html), Oft confused, no more.
|
||||
* [Link to a corrected attribution Devon Lofretto is not Moxie Marlinspike](https://github.com/lifewithalacrity/lifewithalacrity.github.io/commit/52c30ec1d649494066c3e9c9fa1bbaf95cd6386f)
|
||||
> Self-Sovereign Identity has deep roots. It did not just emerge in 2016 after a blog post was written. It did not fail to exist when wikipedia editors denied it subject integrity with the stated message: "good luck with that".
|
||||
|
||||
* [An Identity Through Time](https://iiw.idcommons.net/23D/_An_Identity_Through_Time) by David Schmudde
|
||||
|
||||
The history of identity online. Finger, CompuServe, DNS/WWW, Facebook
|
||||
|
||||
The slides are based on this blog post: [https://schmud.de/posts/2021-04-22-id-through-time.html](https://schmud.de/posts/2021-04-22-id-through-time.html)
|
||||
|
||||
---
|
||||
|
||||
Nothing to prevent players to take advantage of SSI. They may add something small and useful aspects to the protocols.
|
||||
|
||||
The hope is that our stuff is super interoperable. So you can actually really leave.
|
||||
|
||||
Facebook is interesting because it was based on the .edu domain. Small network. Solving for the endstate that we see now is different than starting back then.
|
||||
|
||||
Zero-knowledge proofs and trustless networks may require high-trust environments for adoptions.
|
||||
|
||||
|
||||
* [State of Identity with IDRamp](https://oneworldidentity.com/podcast/idramp-2/) (Enterprise SSI company)
|
||||
> As someone who has uniquely spent their full career immersed in identity, Mike Vesey (CEO of IdRamp) shares an insider perspective of how the industry has evolved during his tenure. This episode dives into the impacts of rapid digitalization worldwide, where identity is heading due to digital transformation, and the benefits that come with it.
|
||||
|
||||
SSI vs Santa
|
||||
|
||||
* [Phil Wolff shares](https://twitter.com/evanwolf/status/1339128612650291203):
|
||||
> In 2021 Santa decentralizes his list, no longer relying on children’s Real Names in compliance with kid privacy laws. Self-sovereign identity lets kids ask Santa, confident their identities are authenticated (right toys to the right kid) & that he uses verified naughty/nice data.
|
||||
|
|
@ -158,3 +158,6 @@ They are actually coming to the [Interoperability Working Group](https://www.not
|
|||
|
||||
A Self- Sovereign Identity can unlock the full potential of the digital global economy. The identity of people, organizations and things is relevant to any transaction, while protecting Personal Identifiable Information (PII) is of increasing importance.
|
||||
|
||||
* [JFF & VC-EDU Plugfest #1: Leaping Towards Interoperable Verifiable Learning & Employment Records](https://kayaelle.medium.com/jff-vc-edu-plugfest-1-892b6f2c9dfb) Kayaelle
|
||||
|
||||
With this badge, they qualify to participate in Plugfest #2 which will focus on issuing and displaying LER VCs. Plugfest #2 will take place in November 2022 with plans to meet in person the day before the [Internet Identity Workshop](https://internetidentityworkshop.com/) on November 14 in Mountainview, CA. If vendors are interested in Plugfest #2 and didn’t participate in Plugfest #1, there is still an opportunity to do so by fulfilling the same requirements listed above including the video and earning a Plugfest #1 badge.
|
||||
|
|
@ -3,6 +3,7 @@ published: false
|
|||
---
|
||||
|
||||
# Literature
|
||||
► [Credentials as a Service Providing Self Sovereign Identity as a Cloud Service Using Trusted Execution Environments](https://ieeexplore.ieee.org/document/9610297)
|
||||
|
||||
* [Universal Declaration of Digital Rights](https://docs.google.com/document/d/1y9C-5TPYmRruRQqJq39-HePk3ypWLDpSAEVzuonOH2Q/edit) Johannes Ernst
|
||||
> all states should recognise and promote universal respect for and observance of both fundamental human and digital rights in physical domain and the digital spaces environment and ensure that these rights are upheld as core elements of a free, open and representative society
|
||||
|
|
@ -1,5 +1,11 @@
|
|||
* [Announcing Pico Engine 1.0](https://www.windley.com/archives/2021/02/announcing_pico_engine_10.shtml)
|
||||
> In addition to the work on the engine itself, one of the primary workstreams at present is to complete Bruce Conrad's excellent work to use DIDs and DIDComm as the basis for inter-pico communication, called ACA-Pico (Aries Cloud Agent - Pico). [...] This work is important because it will replace the current subscriptions method of connecting heterarchies of picos with DIDComm. [...] because DIDComm is protocological, this will support protocol-based interactions between picos, including credential exchange.
|
||||
* [The Most Inventive Thing I've Done](https://www.windley.com/archives/2022/07/the_most_inventive_thing_ive_done.shtml) Phil Windley
|
||||
|
||||
every pico is serverless and cloud-native, presenting an API that can be fully customized by developers. Because they're persistent, picos support databaseless programming with intuitive data isolation. As an actor-model programming system, different picos can operate concurrently without the need for locks, making them a natural choice for easily building decentralized systems.
|
||||
W3C Press Release - [Decentralized Identifiers (DIDs) v1.0 becomes a W3C Recommendation](https://www.w3.org/2022/07/pressrelease-did-rec) worth reading to see who contributed comments (and notice who didn’t)
|
||||
|
||||
For individuals in particular, DIDs can put them back in control of their personal data and consent, and also enable more respectful bi-directional trust relationships where forgery is prevented, privacy is honored, and usability is enhanced.
|
||||
|
||||
* [ACA-Pico working group](https://docs.google.com/document/d/12dWUFyL7u6OQkhnPObJOOlV-U2LDoHpF-ZQLj3hXbjA/edit)
|
||||
|
||||
|
|
@ -0,0 +1,155 @@
|
|||
---
|
||||
published: false
|
||||
---
|
||||
|
||||
|
||||
## Schema
|
||||
|
||||
* [Announcing Schema Markup Validator: validator.schema.org (beta)](http://blog.schema.org/2021/05/announcing-schema-markup-validator.html)
|
||||
|
||||
SDTT is a tool from Google which began life as the [Rich Snippets Testing Tool](https://developers.google.com/search/blog/2010/09/rich-snippets-testing-tool-improvements) back in 2010. Last year Google [announced plans](https://developers.google.com/search/blog/2020/07/rich-results-test-out-of-beta) to migrate from SDTT to successor tooling, the [Rich Results Test](https://search.google.com/test/rich-results), alongside plans to "deprecate the Structured Data Testing Tool". The newer Google tooling is focused on helping publishers who are targeting specific schema.org-powered [search features](https://developers.google.com/search/docs/guides/search-gallery) offered by Google, and for these purposes is a huge improvement as it contextualizes many warnings and errors to a specific target application.
|
||||
|
||||
## Semantics
|
||||
* [The Importance of Data Inputs and Semantics for SSI with Paul Knowles [Podcast]](https://northernblock.io/semantics-for-ssi-with-paul-knowles/)
|
||||
> The platform was an incredibly federated platform when I built it because I didn’t know that SSI existed. So as soon as I found that ecosystem, I tore up the rulebook and said, “This isn’t going to work; I have to rebuild it.”
|
||||
|
||||
## QR
|
||||
|
||||
* [Gordian QR Tool Supports Vaccine Records, 2FAs, Cryptoseeds, and More](https://www.blockchaincommons.com/projects/Releasing-QRTool/) Blockchain Commons
|
||||
> Some possible architectural issues arise from using QR codes for confidential data, such as the fact that you’re actually transmitting the data (not a proof of the data), that the QRs tend to contain all of the data (not just a selection), and that there’s no way to rescind a QR or expire it. Those issues will have to be dealt with at a foundational level as we figure out what can safely be encoded as a QR — and more importantly how to offer restricted proofs rather than complete information.
|
||||
|
||||
## Mobile Agent Dev
|
||||
* [App Framework for Mobile Agent Dev - “No more forking”](https://iiw.idcommons.net/22A/_App_Framework_for_Mobile_Agent_Dev_-_%2522No_more_forking%2522) by Horacio Nunez
|
||||
|
||||
This session had the objective to present a solution to the problem of forking when developing new mobile agents. With the current starting kits available in the community it is very easy to start a path where it is almost impossible to retrofit updates to the kit back into our custom agent.
|
||||
|
||||
The solution consists in using a framework-first approach and ensuring that custom code can reside exclusively outside of the framework, thus ensuring updates can be executed more easily.
|
||||
|
||||
The following link can be used as the public url for the project:
|
||||
|
||||
* [https://www.notion.so/App-Framework-for-Mobile-Agent-Development-No-more-forking-52ebe4e5635d400eb225b0ed537404d8](https://www.notion.so/App-Framework-for-Mobile-Agent-Development-No-more-forking-52ebe4e5635d400eb225b0ed537404d8)
|
||||
|
||||
|
||||
### Caribou - Research \ Advisory
|
||||
Digital Caribou shares their thoughts on [Digital Transformation and inclusion](https://medium.com/caribou-digital/transformation-in-a-digital-age-9068338fd778) - very good thinking for all of us working on digital identity.
|
||||
|
||||
> We believe that the emphasis on transformation as both process and effects is particularly important, especially as although digitization and digitalization are well underway, accelerated by the response to COVID-19 (remote working, payments, etc.), these are not inevitable processes. They are the results of human decisions. Similarly, the effects of these are not inevitable, either.
|
||||
* [The human impact of identity exclusion in financial service](https://medium.com/caribou-digital/the-human-impact-of-identity-exclusion-in-financial-services-ce1e0d769389) Caribou Digital
|
||||
> we spoke to a range of participants who are or who have felt excluded from financial systems for different reasons and we’ll be sharing these stories over the next few months. This research is the foundation for Women in Identity to build an Identity Code of Conduct — a set of guiding principles and a framework for inclusive ID-product development.
|
||||
* [Digital Identity for Development — and protection](https://medium.com/caribou-digital/digital-identity-for-development-and-protection-d92716f24bb6) Caribou Digital
|
||||
> the deployment of digital identification systems needs to get smarter about understanding the political interests and risks that shape the contexts in which identification systems are used — our [ID Ecosystem Mapping tool](https://medium.com/caribou-digital/kenyas-identification-ecosystem-7cbc2ee27) supports risk assessment arising from the deployment of digital identification systems.
|
||||
|
||||
## General Dev
|
||||
* [Technical Debt](https://www.continuumloop.com/technical-debt/)
|
||||
> - Technical Debt – Seth covers it well but missed a major cause of technical debt. That being the shortcuts that are taken to meet deadlines and requirements – with the hope/fantasy that we’ll go back and do them right later (hint: we never do).
|
||||
> - Project Debt
|
||||
> - Why saying NO to those simple things may be the best thing. For some hints on how to do that see [Say No With Grace](https://www.continuumloop.com/say-no-with-grace/).
|
||||
* [The Journey of an SSI Developer](https://academy.affinidi.com/the-journey-of-an-ssi-developer-6ef4f642779c) Affinidi
|
||||
* [Clear is better than clever](https://dave.cheney.net/2019/07/09/clear-is-better-than-clever) Cheney.net
|
||||
|
||||
“why would I read your code?” To be clear, when I say I, I don’t mean me, I mean you. And when I say your code I also mean you, but in the third person. So really what I’m asking is, “why would you read another person’s code?”
|
||||
* [Contributing to Complex Projects](https://mitchellh.com/writing/contributing-to-complex-projects) Mitchell H
|
||||
|
||||
Inspiration - for folks engaging with new code
|
||||
|
||||
As a frequent open source maintainer and contributor, I’m often asked: where do you start? How do you approach a new project with the goal of making meaningful changes? How can you possibly understand the internals of a complex project?
|
||||
|
||||
|
||||
### Civic
|
||||
|
||||
* [Introducing New Tools for Creators to Build Trusted Communities](https://www.civic.com/blog/introducing-new-tools-for-creators-to-build-trusted-communities/) CIVIC
|
||||
|
||||
Our goal is to make the process of building trust easier and more effective for creators. With that in mind, we’re sharing an overview of our plan to address the pain points of creators and marketplaces in the NFT space using identity tools.
|
||||
|
||||
### Ceramic
|
||||
|
||||
* [An authentication system built with Ceramic & self.id](https://github.com/dabit3/decentralized-identity-example) dabit3
|
||||
|
||||
This project implements a user authentication flow leveraging an Ethereum wallet for single sign on capabilities across all of Web3.
|
||||
|
||||
The technologies used are [DID (decentralized identifiers)](https://www.w3.org/TR/did-core/), [Ceramic](https://ceramic.network/), [3id-connect](https://github.com/ceramicstudio/3id-connect), and [Self.ID](https://developers.ceramic.network/tools/self-id/overview/)
|
||||
* [Building capability-based data security for Ceramic](https://blog.ceramic.network/capability-based-data-security-on-ceramic/)
|
||||
|
||||
The 3Box Labs team recently published a new standard for creating capability containers for accessing decentralized data to the Chain Agnostic Standards Alliance. Capability containers are an approach for managing advanced data security and permissions, commonly referred to as “Object Capabilities” or “OCAPs.”
|
||||
|
||||
This new standard is currently in development for use on Ceramic. Once deployed in a future version of the protocol, it will allow Ceramic to be fully compatible with the new Sign-in with Ethereum (SIWE) specification as well as provide advanced data flow control features for resources stored on the Ceramic network.
|
||||
* [The next architecture for building Web3 data apps](https://blog.ceramic.network/the-next-architecture-for-building-web3-data-applications/) Ceramic
|
||||
|
||||
We're replacing the popular IDX runtime with a more powerful set of tools for building applications on Ceramic including DID DataStore, DataModels, and Self.ID.
|
||||
|
||||
|
||||
## Entrustient
|
||||
* [No Code Solution Using Self-Sovereign Identity on Redundant Blockchains](https://www.pressrelease.cc/2021/12/02/entrustient-launches-the-first-no-code-solution-for-trusted-decentralized-digital-identity-using-self-sovereign-identity-on-redundant-blockchains/) Entrustient
|
||||
|
||||
Our goal was to put the power back into the hands of users who do not have any coding knowledge or experience, to accelerate the time to configure and launch an entire Trusted Decentralized Digital Identity peer-to-peer ecosystem
|
||||
|
||||
|
||||
|
||||
### Sphereon
|
||||
* [PRESENTATION EXCHANGE WITH SIOP V2](https://sphereon.com/solution/dif-presentation-exchange-with-siop-v2/)
|
||||
|
||||
Sphereon has developed a Typescript/Javascript Library that implements the functionality described in the [DIF Presentation Exchange](https://identity.foundation/presentation-exchange/) specification.
|
||||
|
||||
### bloom
|
||||
|
||||
* [Introducing SSI SDK](https://bloom.co/blog/introducing-ssi-sdk/) Bloom
|
||||
|
||||
- @bloomprotocol/vc
|
||||
- @bloomprotocol/ecdsa-secp256k1-signature-2019
|
||||
- @bloomprotocol/ecdsa-secp256k1-verification-key-2019
|
||||
- @bloomprotocol/elem-did-legacy-non-anchored
|
||||
- @bloomprotocol/waci-core
|
||||
- @bloomprotocol/waci-jose
|
||||
- @bloomprocotol/waci-kit-react
|
||||
- @bloomprotocol/presentation-exchange
|
||||
- @bloomprotocol/credential-manifest
|
||||
|
||||
### Ringaile
|
||||
* [How to write verifiable credentials in golang](https://ringaile.medium.com/how-to-write-verifiable-credentials-in-golang-7447234d5c16)
|
||||
Note: the code is written following the
|
||||
[Verifiable Credentials Data Model 1.0](https://www.w3.org/TR/vc-data-model/)
|
||||
You can find full code here:
|
||||
[https://github.com/ringaile/ver-cred](https://github.com/ringaile/ver-cred)
|
||||
|
||||
### EPS
|
||||
* [EPS for SSI (Self-Sovereign Identity)](https://kokumai.medium.com/eps-for-ssi-self-sovereign-identity-8c742e2b1d02)
|
||||
> In my earlier post, I failed to refer specifically to the people working for Self-Sovereign Identity and the likes of blockchain that support the distributed/decentralised storage of secrets. [...] you might all be interested to hear that the key function of Expanded Password System is to convert images to high-entropy codes that work as very long passwords and also as the seeds of symmetric/asymmetric cryptographic keys.
|
||||
|
||||
### Dillo-DID Plugin Dillo Browser
|
||||
|
||||
* [Dillo plugin for DID URLs](https://lists.w3.org/Archives/Public/public-credentials/2021Feb/0038.html) Charles E. Lehner
|
||||
> I would like to announce dillo-did, a plugin for the Dillo web browser implementing support for DIDs. This plugin enables navigating to DID URLs in Dillo and viewing the resolved/dereferenced DID documents and resources like web pages. The implementation of the DID functionality used is from ssi/DIDKit.
|
||||
|
||||
|
||||
### Godidy
|
||||
* [@mfosterio · Apr 29](https://twitter.com/mfosterio/status/1520130657468440576) Twitter
|
||||
|
||||
I created a DID at [http://GoDiddy.com](https://t.co/QhwQhqUz0k) did:key:z6MkfxFPD3vwny367HZVQoqUnKatH4RTHEitcbEdvxst3nZm#z6MkfxFPD3vwny367HZVQoqUnKatH4RTHEitcbEdvxst3nZm DIDs are important in Self Sovereign Identity. You can learn about DIDs
|
||||
|
||||
### ownyourdata
|
||||
* [Semantic Overlay Architecture](https://www.ownyourdata.eu/en/semantic-overlay-architecture/) Own Your Data
|
||||
|
||||
We have documented the [functionality of SOyA](https://ownyourdata.github.io/soya/) in a W3C-conforming Specifiation and the full source code is available under the MIT License [on Github](https://github.com/OwnYourData/soya/). Examples and an introduction how to use SOyA is [available in a dedicated Tutorial](https://github.com/OwnYourData/soya/blob/main/tutorial/README.md)
|
||||
|
||||
|
||||
### T-Systems
|
||||
* [Self Sovereign Identity (SSI) at T-Systems MMS: Interview mit Mujtaba Idrees, T-Systems MMS](https://www.youtube.com/watch?v%3DA311QHASy5Y) 7min video on YouTube
|
||||
|
||||
► Dr. Ivan Gudymenko, Subject Matter Lead SSI and Confidential Computing, T-Systems MMS
|
||||
|
||||
►Mujtaba Idrees, Advanced Software Engineer, T-Systems MMS
|
||||
|
||||
► [Credentials as a Service Providing Self Sovereign Identity as a Cloud Service Using Trusted Execution Environments](https://ieeexplore.ieee.org/document/9610297)
|
||||
|
||||
### KidOYO
|
||||
* [Engineer your world this summer: K-University student + teacher opportunities are live!](https://kidoyo.com/join) KidOYO
|
||||
|
||||
Whether a beginning learner, or interested in advanced concepts like Game Development, Hardware Prototyping, or Competitive Coding, you will find tools, lessons and mentors
|
||||
|
||||
|
||||
### Aztec
|
||||
|
||||
* [Introducing Noir: The Universal Language of Zero-Knowledge](https://medium.com/aztec-protocol/introducing-noir-the-universal-language-of-zero-knowledge-ff43f38d86d9) Aztec Network
|
||||
|
||||
Noir is a Rust-based domain specific language (DSL) for creating and verifying zero-knowledge proofs. It’s the easiest way to write zk applications that are compatible with any proving system.
|
||||
|
||||
|
|
@ -22,6 +22,19 @@ Verifiable Credential
|
|||
JSON-LD
|
||||
- [Complementary] JSON-LD ✓ (W3C)
|
||||
|
||||
### Data Privacy Vocab
|
||||
* [https://kantarainitiative.org/confluence/collector/pages.action?key=WA&src=sidebar-pages](https://kantarainitiative.org/confluence/collector/pages.action?key%3DWA%26src%3Dsidebar-pages)
|
||||
|
||||
W3C Data Privacy Vocabulary Control
|
||||
|
||||
* [https://dpvcg.github.io/dpv/#Representative](https://dpvcg.github.io/dpv/%23Representative)
|
||||
|
||||
* [Primer] [Data Privacy Vocabulary (DPV)](https://w3c.github.io/dpv/primer/%23core-taxonomy) w3c
|
||||
|
||||
Call for Comments/Feedbacks for DPV v1.0 release
|
||||
|
||||
Please provide your comments by 15-OCT-2022 via [GitHub](https://github.com/w3c/dpv/issues/50) or [public-dpvcg@w3.org](https://lists.w3.org/Archives/Public/public-dpvcg/) (mailing list).
|
||||
|
||||
### Credentials Community Group
|
||||
|
||||
- [Exchange] CHAPI ✓ (CCG)
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue