Post

"details aren't stored on protocol" Is anything stored on protocol (a signed verifiable credential for example) or is this a proprietary thing that requires queries to an external API? Is it extensible in a way that other verifiers could participate? Will it support all EIDAS / EUDI countries?

0 reposts0 likes

The label is stored, but it's just a label. The model is extensible. Just sharing a demo for now as we're getting it ready for next week's conference (at which people will be able to use it themselves). It's important to get this right, so I can't commit to a release date yet!

Presumably there is some kind of signature a client can verify? Where is the root of trust? Governments? Or an intermediate verification entity? Looking forward to the release, this sounds exciting. (Will the presentation be recorded?)

@caesar.dev I'm banging on this one. Recorded! PLEASE! Let's have a foundation doc and a place to discuss it. This war between "experts" is tiring me out. We all have to breathe the same atmosphere. bsky.app/profile/simo...

simonfj.eurosky.social@simonfj.eurosky.social

Its so funny. I'm thinking about the silly arguments between @anna.wsocial.eu and @robin.berjon.com organisations. Then I looked at their web mastheads. eurosky.tech vs. wsocial.news technical boffins vs. news aggregators Yep. And never the twain shalt meet. 🤣

That's why I put the demo up. 24 countries so far. You can see the eIDAS legislated "mandatory" attributes - the standard so far. I have mentioned the edugain guys (R&E sector) are trialing linking between eIDAS (few attributes) and edugain accounts (lots of creds).