Backpack

• Name: Backpack
• URL: https://backpack.app/
• Category: wallet-and-exchange operator / wallet-control and market-access company / developer-facing wallet-integration company
• Tags: solana-ecosystem ethereum-ecosystem
• Summary: Backpack belongs in companies/ because the practical control surface is not only a self-custodial wallet exists or an exchange API exists; it is that one named operator ships the wallet, controls the docs and distribution shell, publishes the deeplink and localhost-RPC integration path, and runs the ED25519-signed exchange API the same users and integrators may rely on for market access. The project note stays on the product surface. This entity note is for the operator boundary around release and support workflow, wallet-integration defaults, API authentication, and the combined wallet-to-market shell users inherit.
• What it does:
  • Ships Backpack as a self-custodial wallet across browser extension, iOS, and Android for Solana and multiple EVM networks
  • Packages hardware-wallet connectivity, multisig guidance, custom RPC configuration, NFT handling, swaps, staking, and testnet access into the first-party wallet surface
  • Publishes developer-facing wallet integration surfaces including deeplinks, localhost RPC endpoints, and provider methods
  • Operates a first-party exchange API with REST and WebSocket access, ED25519-signed state-changing requests, and an official Rust client
  • Maintains the official support-docs corpus that tells users and integrators how Backpack expects wallet, hardware-wallet, multisig, and exchange flows to work
  • Presents the brand itself as an all-in-one crypto app spanning wallet and trading surfaces rather than as a narrow wallet binary
• Key claims:
  • The official homepage frames Backpack as The All-in-One Crypto App with futures, spot, lending, and a crypto wallet, which is the clearest first-party signal that the operator wants wallet access and market access read together rather than as separate products
  • The wallet definition docs describe Backpack as a self-custodial wallet for Solana plus multiple EVM chains, making the wallet surface broader than a single-chain retail client
  • The hardware-wallet docs say Backpack Wallet supports Ledger, Trezor, and Keystone together, while the multisig docs route users through Squads, Realms, and Safe, which makes the company-run wallet shell and integration guidance part of the trust boundary
  • The technical docs expose localhost RPC endpoints, deeplinks, and provider methods, which is strong evidence that Backpack is not only shipping an end-user app; it is also normalizing an application-integration path developers may start treating as default wallet behavior
  • The exchange API docs require ED25519-signed requests for state-changing calls, and the API FAQ plus official Rust client show that Backpack runs a real developer-facing market-access surface rather than only a consumer exchange frontend
  • Taken together, the official materials make the useful question who packages and controls the wallet-plus-market-access shell?, not only what can the wallet do?
• Whitepaper: No standalone company whitepaper is the important artifact here. The strongest primary-source snapshot is already captured in ../whitepapers/backpack-primary-sources-2026-04-28.md, which preserves the official homepage, wallet docs, technical docs, and exchange API materials that make the operator boundary legible.
• Sources:
  • https://backpack.app/
  • https://support.backpack.exchange/wallet/what-is-backpack-wallet.md
  • https://support.backpack.exchange/wallet/get-started/supported-browsers-and-platforms.md
  • https://support.backpack.exchange/wallet/actions/connect-hardware-wallet.md
  • https://support.backpack.exchange/wallet/actions/multisig.md
  • https://support.backpack.exchange/wallet/technical-docs.md
  • https://docs.backpack.exchange/
  • https://support.backpack.exchange/exchange/api-and-developer-docs/faqs.md
  • https://github.com/backpack-exchange/bpx-api-client
  • ../whitepapers/backpack-primary-sources-2026-04-28.md

Internal linkages

• Product-layer note: backpack.
• Useful wallet-operator contrasts: cake-labs, blockstream, and coinbase.
• Keep the stronger product comparisons on squads and rabby.

Protocol / company boundary

• Keep backpack focused on the product surface: wallet behavior, hardware-wallet and multisig workflows, deeplinks and localhost RPC, and the exposed exchange API surface users and developers actually touch.
• Keep this entity note focused on the named operator that ships the release and support shell, defines the first-party integration path, and couples wallet access with market access under one brand.
• That split matters because what features does Backpack expose? and who controls the wallet-plus-market-access shell users inherit? are related but not identical questions.

Control surface

• Practical leverage sits in wallet distribution, support and documentation workflow, deeplink and localhost-RPC behavior, hardware-wallet and multisig guidance, exchange API authentication, official client support, and which market paths Backpack makes easiest to reach from the wallet shell.

• Even when the wallet is self-custodial, users and integrators still depend on Backpack for the software supply path, the normalized integration surface, and the first-party market-access shell wrapped around it.

• Read the durable risk here as who controls the wallet-operating and market-access shell around the user's keys?, not only as is the wallet itself self-custodial?

• Last reviewed: 2026-08-07 UTC