Skip to content

Latest commit

 

History

History
42 lines (32 loc) · 1.47 KB

2-Bidirectional-Communication.md

File metadata and controls

42 lines (32 loc) · 1.47 KB

Overview

Communicating across platforms

Decisions

  • Remove dependency on Wallet Connect
  • Attest the knowledge of a wallet private key (ARC-31-Discussion)
  • Guard credential creation

Implementation

Sessions should be guarded by the "proof of knowledge" of a wallet's private key. Currently there is a heavy reliance on Wallet Connect for communicating with Wallets.

This implementation should replace Wallet Connect with the following sequence

sequenceDiagram
    participant Website
    participant Server
    participant Wallet
    Note over Website, Wallet: Link devices
    Website->>Server: Subscribe to 'wss:link'
    Website-->>Website: Display QR Connect Nonce
    Wallet->>Website: Scan QR Code
    Wallet->>Server: POST Nonce + Signature
    Server-->>Server: Validate Signature
    Server-->>Website: HTTPOnly Session
    Server->>Wallet: Ok Response + HTTPOnly Session
    Server->>Website: Emit to `wss:link` client
    Website-->>Website: Continue FIDO2 Flow
    Wallet-->>Wallet: Continue FIDO2 Flow
Loading

Once the session is attested to by the wallet private key, we allow for credential creation. This limits the knowledge emitted by the wallet keys to only the nonce for connecting. The only time the private key of the wallet is required is when registering credentials on a new device.

*Note: This process may be deprecated in the future in favor of passkeys which also support FIDO2 credentials with an additional hybrid cross-platform authenticator.