Sharing the verification flow demo of
@Sign's Verifiable Credential system from our tech team standup today, presented by my Cornell alumni
@lazytitan62:
in the demo he shows an end user opens their phone wallet that holds the verifiable credentials, reveals and verifies his Cornell degree 4.0 GPA. (Diploma's the light example, such credentials can be expand to healthcare records, real estates, licenses, etc)
When designing such credential system for nations, we need to think about: Who decides what you prove, to whom, and what gets logged. Today a lot of system flow: verifier asks -> central system answers -> data copies, logs, spreads. Every check creates visibility you didn't choose. Sign's verifiable credentials invert it.
With our system: issuer signs once, holder stores, and verifier confirms signature revocation locally. States get scalable services without single points of failure and citizens get control over disclosure.
We are building a lot of cool systems with our clients, I will share more about what
$SIGN is building, and our progress with our community.