Salmon Wallet: open wallet infrastructure for Solana

Salmon Wallet (salmonwallet.io) markets itself as open wallet infrastructure for Solana: open-source, self-custodial, community-driven software that treats integrations as a distribution path for protocols—not only as a place to hold SOL and tokens.

The product line that ships today is a normal wallet surface (create/import, balances, send/receive, NFTs, dApp connect). The thesis on top is different from a closed consumer wallet: keep the core small, grow capability through selected modular Powerups, and give partners a structured path from application to measured usage.

What ships today

Locales on the marketing site include English, Spanish, and Portuguese. Socials: @salmonwallet, Telegram t.me/salmon_wallet, GitHub org branding under Salmon-HQ. Integrations contact: integrations@salmonwallet.io.

Product model: Core + Powerups

Salmon Core is the always-on wallet: control assets, understand signing requests, connect to Solana safely. Docs describe basic flows— balance, send, receive, connect, NFTs—as core, not bolted-on growth features.

Powerups are optional modules (swap, bridge, explore, and a backlog of community/coming-soon items like portfolio, stake UI, on/off-ramp, news, chat, private send). The design goal is to avoid a permanent super-app surface area: modules can be tested, improved, demoted, or promoted based on usage instead of freezing every idea into the binary forever.

Integrations are open entry, not auto-production

Salmon’s partner story is explicit: projects can apply, but production access is curated because wallet integrations touch signing, permissions, navigation, performance, and security. The published pipeline is:

1. Apply (use case, scope, permissions, maintenance, distribution hypothesis)
2. Qualify (fit, value, feasibility, adoption, coherence)
3. Build (ownership, milestones, implementation path)
4. Validate (security, UX, signing, compatibility, ops)
5. Launch (controlled or production release)
6. Measure (activation, completed actions, repeat usage, cohorts, feedback)

Support levels: Experimental, Verified, Featured. Inclusion ≠ automatic endorsement or homepage placement. Success metrics are usage-shaped (activation and return behavior), not “logo on a partners page.”

Audience they call out: emerging Solana protocols, NFT communities, security / self-custody tools, Solana-first apps where the wallet is the gateway, and builders who care about open infrastructure.

Chains, keys, and recovery (docs)

Official docs (docs.salmonwallet.io) state:

• Chains: Solana (mainnet + dev/test) and Bitcoin (mainnet, testnet, regtest on dev builds)
• BIP44 paths: Solana m/44'/501'/{index}'/0'; Bitcoin m/44'/0'/{index}'/0/0
• Self-custodial: keys stay on device, encrypted with the user password; recovery via seed + matching path in any BIP44 wallet

Builder / stack notes

Developer-zone docs describe a multi-target app:

• React 18 + React Native 0.70 shared UI/logic
• Web via CRA; extensions for Chromium/Firefox
• Solana via @solana/web3.js 1.95.x; Bitcoin via BitcoinJS
• Node 18+; env templates for local/develop/main/prod

There is a dedicated chapter on the wallet adapter system: standard Solana adapter interfaces, explicit connect/sign prompts with dApp identity, simulation/summary before sign, origin checks, re-approval on network or lock changes. That is the surface dApp builders care about when testing “does Salmon work like other wallets?”

User → dApp "connect"
  → Salmon prompt (name, icon, origin)
  → approve → public key only
dApp → signTransaction
  → simulate / show amounts, fees, programs
  → approve → signature (keys never leave isolated context)

Docs also cover onboarding wizard, AppContext state, storage/persistence, i18n, and a blockchain account abstraction layer aimed at multi-chain interactions behind one interface.

Note for researchers: the public GitHub org page for Salmon-HQ may show few or zero listed public repos depending on visibility settings even while the product claims open-source and docs point at a multi-package layout. Verify the live repository URLs and license before assuming auditability of a specific commit.

Validator

Since June 2026 Salmon operates a Salmon Wallet Validator on Solana mainnet as ecosystem infrastructure (site-published snapshot metrics include est. APY, 5% commission, active stake, uptime, skip rate, Wiz score). Native in-wallet staking is still listed as coming soon; the site links out to validators.app for operator details (SA1LFXr4os2P4VKGUyRv84uFfuUYgcQkFh2uA4SmRcr on the public link path). Treat live metrics as time-varying—check the site or validators.app for current numbers.

How it compares (positioning, not a scorecard)

For app builders, day-to-day checklist is still the same as any wallet: Wallet Standard / adapter connect, transaction simulation quality, mobile deeplinks, and whether your users already have Salmon installed. For protocol teams shopping for distribution, the interesting bit is the Powerup + measured integration program— contact and apply flows are first-class on the site.

Resources

• salmonwallet.io
• docs.salmonwallet.io · llms-full.txt
• Web wallet · Chrome extension · Android
• @salmonwallet · GitHub Salmon-HQ
• DevRels organisation

Summary

Salmon is a live multi-platform self-custodial Solana wallet with a clear infrastructure narrative: small core, modular Powerups, curated partner integrations aimed at real activation, open-source positioning, and a mainnet validator. Builders should read the adapter/security docs and verify the public code path; protocols evaluating distribution should look at the integration levels and metrics model, not only the install links.