At #GDC26, Global Digital Collaboration conference, the first session of Day 3 in Alpha room, speakers Richard Esplin, Steffen Schwalm, Martin Westerkamp, Tom Sugden, and Louise de Laat underscored that the KERI Foundation needs to collaborate more with European developments.
The panel highlighted how to solve organizational identity across jurisdictions.
There were two fundamental misconceptions about #vLEI and #KERISuite that we would like to address (in a collaborative way 🙂 ):
1. vLEI stands for verifiable LEI (not “virtual” LEI), a fundamental detail that differentiates KERI from all other established identifier systems.
2. “KERI and ACDC are not standard yet; the KERI Foundation should work on this. Until then, don’t use them for business wallets.” This is a misconception, as laid out below.
#KERI, #ACDC, and #CESR are ratified standards under #TrustoverIP. The KERI Foundation is actively striving to continue this process by applying for IETF standardization.
There’s no reason not to use KERI, ACDC and CESR; the technology is mainly a means to an end that is able to comply with a wide variety of principal values in digital identifier systems that you need to implement organizational identity across jurisdictions. Just to name a few unique to the #KERISuite:
- Cryptographically verifiable to the root of trust
- Persistent identifiers (key rotation)
- Globally scalable
- Fault-tolerant (be able to recover from incidents)
- No shared secrets
- Interoperable by design
- Gradual selective disclosure schemes
- Accountability and recourse options
The ISO standard for vLEI in authentic chained data container (ACDC) credentials is ISO 17442.
The KERISuite specs (ToIP ratified): https://lnkd.in/eZ63jKy6, https://lnkd.in/ez2YkiSU and https://lnkd.in/eE_NYhMH
The LinkedIn post includes an image. Download it from the original if it should appear here. The image address on LinkedIn expires, so it is not embedded.
LinkedIn had collapsed the rest of this post behind “meer”. This draft stops at the visible text.
Originally published on LinkedIn: https://www.linkedin.com/feed/update/urn:li:share:7501213726415638528/