Leather

• Name: Leather
• URL: https://leather.io/
• Category: Bitcoin-and-Stacks wallet infrastructure / injected wallet-provider API / self-custodial Bitcoin access layer
• Tags: bitcoin-ecosystem stacks-ecosystem
• Summary: Leather is mostly a Bitcoin-and-Stacks access layer. The wallet matters because it exposes a provider API, signing methods, and app-approval surface for outside software; the consumer extension is just how users reach that control plane. The public docs and repos are enough to keep it in the corpus, but the note should stay narrow: this is wallet middleware, not a broader protocol or custody primitive.
• What it does:
  • Operates a self-custodial wallet for Bitcoin and the Stacks ecosystem across browser extension and mobile surfaces
  • Supports BTC, STX, Ordinals, BRC-20s, swaps, sBTC flows, stacking access, and hardware-wallet usage according to the official product site
  • Exposes a browser extension provider that injects window.LeatherProvider and implements a .request() interface aligned with the Modern Wallet APIs proposal
  • Documents developer methods for Bitcoin and Stacks flows including address retrieval, message signing, transfers, PSBT signing, Stacks transfers, structured-message signing, contract calls, and contract deployment
  • Publishes typed integration support through @leather.io/rpc and points developers to Stacks libraries such as @stacks/connect and micro-stacks
  • Maintains a public GitHub organization with the current mono repo plus archived public extension and desktop repos, which helps reveal the real operational and architectural surface behind the wallet brand
• Key claims:
  • The homepage positions Leather as a self-custodial wallet built for earning yield and managing assets in the Bitcoin ecosystem, explicitly calling out BTC, STX, Ordinals, BRC-20s, swaps, sBTC, stacking, and Ledger support
  • The developer docs say Leather empowers developers to build apps with Bitcoin and Stacks and expose a global LeatherProvider object for wallet interactions
  • The docs say the provider follows the .request pattern from the Modern Wallet APIs proposal, which makes Leather notable as a standards-leaning wallet integration surface rather than a one-off extension API
  • The developer method index and method pages document Bitcoin flows like sendTransfer, signMessage, and signPsbt, plus Stacks-specific signing and contract methods
  • The docs also expose TypeScript typings via @leather.io/rpc, which is a useful clue that Leather is trying to be a deliberate developer platform, not just a consumer wallet download page
  • The verified GitHub org shows a substantial public repo footprint centered on the browser extension and a current monorepo, reinforcing that the real source of truth lives partly in docs and code rather than marketing copy alone
• Whitepaper: No canonical standalone Leather whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official wallet site, developer docs, and public GitHub organization; see ../whitepapers/leather-primary-sources-2026-04-29.md.
• Sources:
  • https://leather.io/
  • https://leather.gitbook.io/developers
  • https://leather.gitbook.io/developers/overview/introduction.md
  • https://leather.gitbook.io/developers/bitcoin-methods/sendtransfer
  • https://github.com/leather-io

Internal linkages

• Best comparison points: xverse and walletconnect.

• Leather is the thinner Bitcoin-and-Stacks wallet-access note: provider injection and signing methods matter more here than broader hosted APIs, node-control surfaces, or cross-ecosystem session governance.

• Last reviewed: 2026-05-30 UTC