If you read through the DID/ION, etc... standards, you'll quickly notice the Blockchain / crypto pedigree once you start looking for the keywords.
"Trustless", "decentralized", "ledger", etc... all make a regular appearance.
> Introduction to Microsoft Entra Verified ID
In a similar discussion I tried to politely make the point that despite over two decades of "identity" experience under my belt, I have literally no clue what any of this technical gibberish is trying to solve (other than making crypto a mainstream thing).
I've read the entire Entra document. I've read most of the backing standards papers, like ION.
It's wall-to-wall gibberish.
I won't go through the criticism in detail, but let's just look at the the practical example shown in this section: https://learn.microsoft.com/en-us/azure/active-directory/ver...
What. The. Eff?
Why would anyone solve this problem with blockchain!? Or "distributed" anything?
This is a Solved Problem with vastly simpler and more direct (not distributed) solutions.
For example, similar discounts are offered to students and education staff by various shops. They simply ask students to sign up with an email that has an ".edu" or similar suffix.
For this specific example, the shop could simply use any identifier that is PKI-signed by the employer! A simple 2D barcode would do, shown via a simple phone app. Literally just a public key and a barcode. No ledgers, IPFS, wallets, distributed this, trustless that.
A printout on dead trees would suffice.
This all feels like boiling the ocean to make a crypto pot of tea.