The architecture is relatively straightforward and also needs to take into account abstraction.
Here is a write-up and questions with link to a published whitepaper. There is an ongoing effort on this, if anyone from the DeFi protocols or L2s is interested in contributing, please DM me.
@turboblitz using the international passport schema is one step. There also needs to be a root of trust that does the passport reading and digital translation. That is a second credential that establishes the legal identity of the passport data reader and attester. So one is not enough.
Generally speaking, to simplify the circuits, one should also use W3C Verifiable Credentials (at a minimum, ideally with W3C DIDs). Here is a recent write-up on the topic as well as a link to the whitepaper on the topic of identity and standards and key management across chains from the Ethereum Open Community Projects L2 Standards WG.
Thank you for the clarification. I agree that using the international passport schema is just the first step, and having a root of trust for passport reading and digital translation is crucial to ensuring legal identity verification. This second credential would indeed strengthen the system by confirming the validity and trustworthiness of the passport data reader and attester.
I also appreciate your point on simplifying the process using W3C Verifiable Credentials, which would offer a more streamlined and interoperable approach, especially when combined with W3C DIDs. This would facilitate secure and decentralized identity management. I’ll review the write-up and whitepaper from the Ethereum Open Community Projects L2 Standards WG to further understand how these standards can be applied effectively across chains for identity verification and key management.
Thanks for sharing the resources!