Backpack

• Name: Backpack
• URL: https://backpack.app/
• Category: self-custodial wallet / wallet-exchange hybrid / Solana-and-EVM wallet infrastructure
• Tags: solana-ecosystem ethereum-ecosystem
• Summary: Backpack is a wallet-plus-exchange access layer, not just a consumer wallet. The useful thing is the combined product surface: Solana and EVM wallet control, deeplink and localhost-RPC integration, hardware-wallet and multisig workflows, and an ED25519-signed exchange API. That still makes it more interesting as a user-access and trading-control stack than as a standalone wallet brand, but the named operator boundary around release workflow, documentation, integration defaults, and the combined wallet-to-market shell now lives separately in backpack.
• What it does:
  • Offers a self-custodial wallet for Solana plus multiple EVM networks across browser, iOS, and Android
  • Supports sending, receiving, swapping, staking, NFT management, developer testnets, and custom RPC configuration
  • Connects to Ledger, Trezor, and Keystone hardware wallets and documents multisig workflows via external platforms like Squads, Realms, and Safe
  • Publishes deeplink and localhost-RPC documentation for wallet integrations, including connect and signing flows
  • Operates an exchange API surface with REST and WebSocket endpoints, ED25519 request signing, and an official Rust client
• Key claims:
  • The official wallet docs describe Backpack as a self-custodial wallet for Solana plus multiple EVM networks, which is already broader than a single-chain wallet frame
  • The wallet docs are useful because they show Backpack spanning hardware-wallet imports, multisig coordination, custom RPCs, testnets, NFT management, and app integration rather than only send/receive UX
  • The hardware-wallet page claims Backpack Wallet is the only Solana wallet supporting Ledger, Trezor, and Keystone together, which makes the product look more like a wallet-control surface than a thin retail shell
  • The technical docs expose deeplink methods and localhost RPC endpoints, which is the clearest sign Backpack expects third-party integration rather than only end-user app usage
  • The exchange API docs require ED25519-signed requests for state-changing calls and support both REST and WebSocket access, showing the product surface extends materially beyond wallet UX into trading infrastructure
  • The API FAQ says the official SDK is currently Rust-only, while community clients exist for other languages, and the public bpx-api-client repository reinforces that the exchange surface is an active first-party developer product
• Whitepaper: No canonical Backpack whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the support-docs corpus for wallet and exchange behavior, plus the exchange API documentation and official Rust client; see ../whitepapers/backpack-primary-sources-2026-04-28.md.
• 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://support.backpack.exchange/wallet/technical-docs.md?ask=What%20is%20Backpack%20wallet%2C%20who%20is%20it%20for%2C%20what%20wallet%20technologies%20or%20protocols%20does%20it%20support%2C%20and%20what%20open-source%20or%20developer-facing%20components%20are%20part%20of%20the%20official%20product%20surface%3F
  • https://docs.backpack.exchange/
  • https://support.backpack.exchange/exchange/api-and-developer-docs/faqs.md
  • https://github.com/backpack-exchange/bpx-api-client

Internal linkages

• Company / operator boundary for release workflow, integration defaults, and the combined wallet-to-market shell: backpack.
• Best product-layer anchors: solana-wallet-adapter, squads, and rabby.

Protocol / company boundary

• Keep this note on the product surface: wallet behavior, hardware-wallet and multisig workflows, deeplinks and localhost RPC, and the exposed exchange API users and developers actually touch.
• Use backpack for the named-operator layer around release workflow, support docs, integration defaults, API authentication, and the broader distribution shell that ties wallet access and market access together.
• That split matters because what does Backpack expose? and who controls the wallet-plus-market-access shell around it? are related but not identical questions.

Control surface

• At the product layer, the leverage sits in wallet discovery, deeplink and localhost-RPC behavior, route defaults, hardware-wallet flows, and the exchange paths Backpack makes easiest to use.

• The important point is still simple: wallet access and market access sit close together here.

• For the broader operator shell above that product surface, read backpack.

• Last reviewed: 2026-08-07 UTC