[rhyzomatic]

I must be missing something here, but why not just go with a challenge-proof type scheme? Something like

1. You want to prove to $PotentialEmployer that you own address A which has necessary credentials.

2. $PotentialEmployer sends you a random string.

3. You sign it with the private key of address A and send them the proof.

4. $PotentialEmployer verifies the signed string.

If the employer has this proof and can see in the metadata that it's your name and date of birth (or whatever), wouldn't that be enough?

[tobz]

The idea was that, for the lowest common denominator of "hmm, what was your GPA/degree/whatever?", it's easier to give bits of more-or-less secret information than to do a challenge response on the spot.

Everything was about leaving the institutions granting credentials / third parties who consume the blockchain data to handle the technical bits, while an employer or potential employee only had to know where to go and what secret values to use.

I suppose this could be wrapped up in a simple app or something, but I was going for bulletproof-ish. It's easy to remember a social security number, full name, etc. It persists through broken laptops and smartphones.