Security

What's cloaked, what's not, what you trust.

The honest version. If something isn't on this page, assume it's public.

  • An explorer watcher reads your tradeLegs move as Privacy Ring private transfers: no amount, no recipient. The escrow never receives a public transfer from you.Deposits into and withdrawals out of the Ring are public. Timing and round-trip amounts can hint.
  • Counterparty takes your leg and never paysSettlement only pays when both legs are in. Otherwise your leg is refunded at expiry or on cancel.Your leg is locked until expiry if the taker stalls. Pick a short expiry.
  • Server crash mid-settlementPayouts are recorded as pending with their signature before sending, then confirmed or retried. Ring nullifiers stop double spends.Settlement is delayed until the server is back.
  • Stale or manipulated pricePyth SOL/USD read on-chain; older than 120 s counts as no price, so conditional deals wait.Pyth itself is trusted for the band.
  • The desk operator misbehavesRules are open source; every payout is an on-chain transaction; disclosures are signed and verifiable.During a deal the escrow key is on the server. You trust the operator, as with any OTC desk.
  • Leaked storageDeal records are AES-256-GCM encrypted at rest; object names are hashed.A leaked master key would expose terms and control of live escrows. It's kept server-side and backed up offline.

Keys

  • Your private wallet is derived in your browser from a plain-text signature. It never reaches our servers.
  • Each escrow key is derived from the deal id and a server master key. Nothing per-deal is stored.
  • Sign-in is a second plain-text signature: a 24 h token that can't move funds.

Programs & code

  • Privacy Ring: ring1GaLCuJnkUMVkX2JeZLTTX17wKsV4fZmPVzXANW
  • Rings registry: regy3WAeRXMYuMYxr5iK3Bf9Arr3PcxGxyzAddbiqDQ
  • Settlement rules: lib/deal.ts (17 tests). Escrow agent: lib/deals.server.ts.
  • The Rings SDK is alpha. Start with small deals.