dh

_posts/web-standards/DIDs-and-VCs/2023-09-08-VC-ZKP-CL.md

@@ -68,6 +68,23 @@ last_modified_at: 2023-09-29
   > It’s only when I started to take a step back that I realized that the architecture of Indy being a private, permissioned ledger leaves it heading in the same direction as many large corporations now extinct browser and intranet projects for many of the same reasons.
 * [Moving Toward Identity Technology Ready for Mass Adoption](https://trinsic.id/moving-toward-identity-technology-ready-for-mass-adoption/) 2022-09-09 Trinsic
   > when we realized our customers were facing critical limitations caused by the underlying tech stack, we began developing an updated version of our platform that would reduce our dependency on these technologies and enable a better platform for our customers.
+* [Response to Kaliya’s “Being Real” Post](https://daniel-hardman.medium.com/response-to-kaliyas-being-real-post-13fddb9410f0)
+
+**Link Secrets and Privacy-Trust Paper**
+- Significant section of critique discusses link secrets
+- Repeats old claim they are insecure
+- Cites 2019 paper by Arnold and Longley for support
+- Assertion made that the paper has inaccuracies and misrepresentations
+- Rebuttal sent to W3C CCG with supporting documentation
+- Encourages reading both sources before deciding on credential security
+
+**Misunderstanding About Credential Formats (AnonCreds vs. VC Spec)**
+- Differences in how "credential" is defined between AnonCreds and VC spec
+- AnonCreds' internal "credentials" are not designed for sharing or verification
+- Verifiable AnonCreds "proofs" should be evaluated as verifiable credentials
+- Interoperability work focuses on proofs, not credential formats per se
+- Mapping between AnonCreds proofs and VC data model already exists
+- Lack of willingness to alter UX and messaging may hinder interoperability
 
 ## Prior Work
 * [How is IDEMix Implemented?](https://forum.sovrin.org/t/how-idemex-is-implemented-in-sovrin-indy/)