4 Deployment Models

4.1 Service-Driven Model (Primary)

In the predominant deployment model:

1. Service provider application (bank, government, SNS) initiates

2. Wallet is invoked from service app via OS-level Intent/deeplink

3. Wallet generates DIDComm message containing:

   • Communication DID (ephemeral or persistent based on service)

   • DID Document (public key only)

   • VC/ZKP proving required attributes

4. DIDComm message sent to service provider (HTTPS, typically)

5. Service provider performs:

   • Cryptographic verification of ZKP/VC

   • Authorization decision

   • Service execution

Trust origin: Service provider (centralized, established).

Endpoint lifecycle: Service-scoped (session-based).

4.2 Physical Proximity Model (Supplementary)

For in-person scenarios:

1. Bluetooth Low Energy (BLE) provides discovery via physical proximity

2. Public services (municipal offices, event gates)

3. Session completes within local network

4. No persistent endpoint contracts

Examples:

• Age verification at municipal counter

• Facility access control

• In-person credential verification