verifier devices

Device provisioning & pairing

Each verifier tablet at the gate pairs with this event before doors. Pairing downloads the trust list, issuer keys, status list bitstring and the EventScopeCredential that binds the tablet to this card. Pairing once is enough; the tablet then runs the whole night offline.

Ready
2
Unpaired
1
Offline / archived
0

Tablets

3 provisioned
  • ● VERIFIER · GATE-A-01ready
    Gate A · paired 10 Mar 2027, 11:02
    issuer keys
    3
    DIDs
    24
    status list
    15:42
  • ● VERIFIER · GATE-B-01ready
    Gate B · paired 10 Mar 2027, 11:14
    issuer keys
    3
    DIDs
    24
    status list
    15:42
  • ● VERIFIER · BACKSTAGEunpaired
    Backstage
    issuer keys
    0
    DIDs
    0
    status list
    —
what gets cached on pair

On the tablet, offline

  • · 3 issuer keys — BBSL, NCRA, SLADO public signing keys
  • · N expected DIDs — fighters on the card
  • · 1 status list bitstring — for revocation checks
  • · 1 EventScopeCredential — binds this tablet to this event
  • · 1 schema set — all credential types it might see

All of that fits in under 200KB. The tablet refreshes the status list whenever it has WiFi, but verifications proceed even with no connection.