KM (key manager) Service Worker: define and implement UI to export one's identity via QR code (useful for multi-device)

[0xtsukino]

@0xtsukino to draft a plan for iteration 7

[0xtsukino]

Exporting QR Code

• In Setting, add a new section for "Accounts"
• In the new Account section, add a row for "export identity"
• should ask user to confirm password, and warn that raw identity will be shown on screen
• should export either private key or nullifier + trapdoor
• should serialize zk identity with just string concatenation, otherwise QR code might become too detailed to be captured
• render private key or zk identity in QR Code

Importing QR Code

• see QRScanner/index.tsx

Alternative:

• instead of rendering the raw identity with QRCode, we can use Waku pubsub stead
  1. on desktop, generate a new ECDH keypair
  2. on desktop, render ECDH Pubkey as QRCode
  3. on desktop, subscribe to a topic like this: "zkitter/pw_[ecdh_pubkey]/1.0.0/proto"
  4. on mobile, capture the QRCode
  5. on mobile, generate a new ECDH keypair
  6. on mobile, publish own pubkey + origin meta data
  7. on desktop, show that an incoming message is received from {ip: string; location: string; pubkey: string}
  8. on desktop, user should confirm that ip, localtion, and pubkey matches what's on mobile
  9. on desktop, click accept to send identity over waku topic using ECDH encryption

[0xtsukino]

Plan 1

[AtHeartEngineer]

https://github.com/CryptKeeperZK/crypt-keeper-extension/issues/99 same issue but for cryptkeeper