Keylay

Secure, remote multisig coordination with no centralized servers

View on GitHub Launch App

Why Keylay?

Multisig wallets are the gold standard for securing bitcoin. But coordinating setup or signing across locations is hard—most options rely on in-person sharing or centralized infrastructure, creating new single points of failure for both loss and theft. Ad hoc communication channels are clunky and tempt users to violate wallet air gaps. Keylay changes that by acting as a coordination bridge—enabling remote, private, air-gapped, serverless coordination—right in your browser.

  • No server required
  • No compromise of air-gapped signing wallets
  • Private relay via encrypted Nostr messages
  • Browser-based—simply download and open in your browser

 

What Keylay Does

Keylay is a lightweight browser tool for setting up or signing multisig wallets when your co-signers are elsewhere—even offline. It acts as a coordination bridge, using local QR code scanning or file I/O with encrypted message relays to keep signer devices air-gapped and private.

  1. The initiator creates a temporary identity and shares a short code.
  2. Participants derive ephemeral keypairs and respond with encrypted messages and highly secure npubs.
  3. Once verified, xpubs are exchanged securely.
  4. Wallet descriptor is built and confirmed.
  5. Signing coordination uses the same process: fully air-gapped on each end, encrypted coordinatio in between.

All private keys stay local and air-gapped—only encrypted coordination messages are passed through relays like Nostr. No accounts. No metadata.

Who Keylay Is For

  • Journalists, NGOs, and activists securing pooled funds
  • Diaspora groups supporting causes across borders
  • Bitcoiners needing robust multisig with remote cosigners
  • Any user demanding private, secure coordination

Current Status

Version: Pre-Alpha

Current Features:

  • Session bootstrapping with short code to WebConnect demo
  • Scans a static QR code locally and displays it to remote participants
  • Decodes and displays the QR code payload

Next Steps:

  • Animated, bitcoin-standard UR2 QR codes
  • Local file I/O
  • Bootstrapping connection via Nostr
  • First security audit
  • Alpha release
  • User testing + feedback iteration
  • Final audit and production release
  • Integrated Tor support and relay diversity