Benefits and Limitations
All you need to know to understand if our solution works for you
Benefits
Easy of Learn and Use:
Everyone knows how to work with paper
Holders do not have to remember any secrets at all
Users carry a minimal additional physical object
No electronics, no accounts, no payments
Error-proof procedure for any age
Trusted:
The signed payload is cryptographically protected and thus impossible to tamper
Issuers place their public keys on their DNS records, facilitating trust from a known website
Observation-proof: Signed cards are bound to a person's ID. An attacker cannot impersonate a user after observing them present a credential
Knowledge-proof: It is not possible for an attacker to impersonate a holder by exploiting knowledge of personal details
Hack-proof: Nothing a verifier could possibly leak can help an attacker impersonate the user to another verifier
Theft-proof: An attacker in possession of a Holder's credentials cannot use them for presentation to another party.
Small:
Complete QR-code payloads range between 100 and 200 bytes, ideal for low-end and feature phones
It is ideal to cheaply transfer the payload via SMS
Private with selective disclosure:
Users can easily choose which attributes to present and withhold the rest
No centralized PII, no exposure to government, private companies
No central point of failure
No need for PII at the vaccination site or at tracking systems
Protection for vulnerable populations
Easy to backup: A picture serves as a backup of the code
Negligible Cost per User
Generalizable: Any record/payload can be created and signed in the same format
Modular: Add QR Codes to app/computers for additional features
Scheduling, Reminders, Backups, Self-reporting, etc
OpenSource Specifications under MIT License
Limitations
Traceability of the QR Codes is possible by colluding verifiers
Solutions include generating multiple salted QR Codes to be given away as opposed to one code that is read everywhere
Chance of losing the card, losing the data
The issuer might have a copy of the event record, but it is not a requirement
Apps and pictures of the card can serve as a backup
No Revocation of cards/credentials
The only option is to remove the public key from the database, invalidating all certificates
Card information itself is not encrypted
The only information security feature is on the tri-fold mechanism of the paper card
Last updated