How to set up a Leather wallet? (Stacks/Bitcoin L2)

Understanding Leather Wallet Fundamentals

1. Leather is a non-custodial browser extension wallet designed specifically for the Stacks blockchain and Bitcoin Layer 2 applications.

2. It supports STX tokens, sBTC, and other assets built on Clarity smart contracts.

3. The wallet integrates directly with Hiro’s ecosystem, enabling seamless interaction with dApps like Arkadiko, Alex, and CityCoins.

4. Unlike traditional Bitcoin wallets, Leather requires connection to a Stacks node or Hiro’s public API endpoints to fetch balances and broadcast transactions.

5. It does not store private keys on remote servers—users retain full control over seed phrases and signing logic executed locally in the browser.

Installation and Initial Setup Process

1. Navigate to leather.io and download the official extension for Chrome, Firefox, or Edge.

2. Confirm the extension ID matches Hiro’s verified publisher signature before installation.

3. Click “Create a new wallet” and choose a strong password—this encrypts your local key storage but does not replace the recovery phrase.

4. Write down the 24-word BIP-39 mnemonic phrase on physical medium and store it offline; digital copies introduce irreversible risk.

5. Import the phrase into Leather by selecting “Restore wallet” if reinstalling or switching devices—no backup cloud sync exists.

Connecting to Stacks and Bitcoin L2 Services

1. Open Leather and click the network selector in the top-right corner to switch from “Mainnet” to “Testnet” if developing.

2. Enable “Bitcoin L2” toggle in settings to activate sBTC and BTC-pegged asset support.

3. Approve permissions when prompted by dApps—Leather displays exact contract calls, function names, and parameter values before signing.

4. Use the built-in address book to label frequently transacted Stacks addresses and reduce copy-paste errors.

5. Monitor transaction status via the activity tab, which pulls real-time confirmations from Stacks Explorer and Hiro’s mempool indexer.

Security Configuration Best Practices

1. Disable “Auto-sign” mode in advanced settings to enforce manual confirmation for every transaction.

2. Enable hardware wallet integration with Ledger Nano S/X for Stacks app version 2.2.0+ to isolate private key operations.

3. Avoid using Leather on shared or public computers—even temporary session data could expose wallet state.

4. Regularly verify the authenticity of dApp domains; phishing sites mimic legitimate Stacks interfaces with subtle URL variations.

5. Audit permission history under “Settings > Permissions” to revoke access for unused or suspicious applications.

Frequently Asked Questions

Q: Can Leather hold native Bitcoin (BTC) directly?Leather does not store BTC on-chain. It manages sBTC—a trust-minimized, 1:1 pegged token backed by Bitcoin via the Stacks chain and threshold cryptography.

Q: Is there a mobile version of Leather?No official mobile app exists. Hiro recommends using the desktop extension with responsive dApps accessed via mobile browsers, though functionality may be limited.

Q: What happens if I lose my 24-word phrase and forget my password?Access to funds is permanently lost. Leather provides no account recovery mechanism—this is inherent to non-custodial design principles.

Q: Does Leather support multi-signature wallets?Not natively. Multi-sig coordination must occur off-chain using Clarity contracts deployed manually or through third-party tooling like Clarinet.