...
Mobile Infrastructure
Discussion Topics
- Mobile Verifiers
- We need them.
- Flow
- Holder displays QR, Verifier scans with mobile app and sees the result. - Common Model, assumed by those new to industry.
- 'presenting' the QR code feels natural when 'presenting' a credential.
- QR is best as invitation, not requiring user to know in advance what to present.
- Verifier can also display QR.
- Speed of transaction
- User prepares to have transaction happen fast
- Preselect or preauthorize set of actions
- Can be assisted by governance / trust registry to find common targets
- build set of 'reapprovals' after done initially.
- save my authorization
- User prepares to have transaction happen fast
- Unique Features
- Offline Verifications
- Can't use shortened QR codes
- BLE Verification useful offline
- Needs framework support
- Machine Readable Governance - cached
- Cache schemas
- Cache public keys for verifiers?
- Pass file? (Interaction)
- Common Hardware
- Framework support required
- Offline aware
- UI Supports required
- Cache Needed
- Speed of local assets
- Mechanisms
- Trust Registry Protocols - https://wiki.trustoverip.org/display/HOME/ToIP+Trust+Registry+Protocol+Specification
- Machine Readable Governance
- Hard Coded
- TTL
- User Experience
- Clear for Holder
- Clear for Verifier
- Clear indication of where in the flow they are. Universal progress bar?
- Particularly for non-happy paths
- Internationalization / Localization
- Performance
- Offline Verifications
- Device Recovery (Backup/Restore/Sync/Rotation to new keys)
- Backup / Restore Formats?
- Secure Element usage
- SDK / Embedding Agents into existing Mobile Apps
...