Open wallet infrastructure.

Lightweight by design. Built to expand around what each user actually needs.

Open-source. Self-custodial. Lightweight. Community-driven.

Wallets should expandwithout becoming heavy.

A focused wallet can be too limited.

It may work well at first, but cannot grow around the needs users develop over time.

A feature-heavy wallet carries too much.

Every permanent capability adds navigation, friction, dependencies, and security surface for every user.

Salmon takes a modular approach.

Keep the wallet core clear and reliable, then add optional capabilities only when they solve a real user problem.

Wallet core + Powerups

A focused wallet core. Powerups when they earn their place.

Powerups are the modular model Salmon is building toward—not a catalog of products available today. The wallet core stays lightweight, reliable, and understandable; future optional capabilities must solve a clear user problem and operate within defined permissions.

Always available

Salmon Core

A focused foundation for controlling assets, understanding signing requests, and interacting safely with Solana.

BalanceSendReceiveConnectNFTs

Start here

The foundation has to work before anything else.

Create or import a wallet, move funds safely, understand what you are signing, and return because the product remains useful and reliable.

  1. · · ·orbit· · ·canyon· · ·velvet· · ·harbor· · ·signal· · ·ember· · ·quartz· · ·meadow· · ·anchor· · ·tundra· · ·marble· · ·pilot

    Wallet ready

    01

    Create or import a wallet

  2. From3xQm…8kLp
    Balance0.00 SOL5.00 SOL

    +5.00 SOL received · finalized

    02

    Receive funds

  3. To7xKX…9fRt
    2.4 SOLPendingConfirmed

    sig 5metKx…2PqA · finalized

    03

    Send a transaction

  4. dapp.example

    wants to connect

    ConnectConnected

    You approve every connection

    04

    Return to a useful, reliable wallet

Focused by default

Essential wallet activity remains clear, reliable, and understandable.

Modular by design

Future capabilities can be added without becoming permanent weight for every user.

Live product

Browser Extension, Web Wallet, Android, and a public open-source repository.

From integration to distribution

Useful integrationUser activationUseful actionRepeat usageDistribution proof

Integrations are not the goal. Usage is.

Salmon measures onboarding, completed actions, return usage, retained cohorts, integration performance, and partner feedback. What proves repeatable activation expands; what does not is improved, deprioritized, or stopped.

How integrations work

Open entry. Curated production.

Projects can apply through an open process. Production access is earned through qualification because integrations affect signing flows, permissions, navigation, performance, security, and the wider wallet experience.

  1. 01

    Apply

    Share the use case, target users, technical scope, permissions, maintenance plan, and distribution hypothesis.

  2. 02

    Qualify

    Salmon evaluates strategic fit, user value, technical feasibility, adoption potential, and product coherence.

  3. 03

    Build

    Salmon and the partner define ownership, milestones, dependencies, responsibilities, and implementation path.

  4. 04

    Validate

    Security, UX, signing flows, permissions, compatibility, maintainability, and operational impact are reviewed.

  5. 05

    Launch

    Approved integrations move into a controlled or production release with clear responsibilities and support expectations.

  6. 06

    Measure

    Activation, completed actions, repeat usage, retained cohorts, partner feedback, and maintenance status are tracked.

What Salmon evaluates

SecurityUser valueUX coherenceTechnical compatibilityMaintainabilityAdoption potential

Integration support levels

Experimental

Limited or controlled release to validate feasibility, UX, and demand.

Verified

Production-ready integration reviewed for security, UX, compatibility, and maintenance.

Featured

High-value integration with stronger visibility, onboarding, or coordinated partner activation.

Approval and promotion are separate decisions. Technical inclusion does not automatically guarantee endorsement or prominent placement.

Salmon Validator

Since June 2026

Salmon Wallet Validator

Operating a Solana validator is part of our long-term commitment to the ecosystem: contributing reliable infrastructure and making performance visible and verifiable. Native Stake coming soon.

5.73%

Est. APY

5%

Commission

61,796 SOL

Active stake

100.0%

Uptime

0%

Skip rate

65

Wiz Score

Active

Status

Live · Salmon Wallet

Manifesto

Salmon is open wallet infrastructure.

Salmon is community-driven today and being built toward community ownership. Critical wallet infrastructure should not remain permanently governed by private control alone. Salmon keeps the wallet core lightweight, reliable, and understandable. Selected Powerups expand what users can do when they solve a real problem, without turning the wallet into a heavy super-app filled with permanent features. Open does not mean automatic access or permissionless production. Integrations still require judgment, review, and accountability. Salmon makes the path to integration more open, structured, transparent, and measurable. Salmon starts with a concrete wedge. It helps Solana projects turn useful integrations into activation, repeat usage, and distribution. Open-source is not branding. It is how critical wallet infrastructure should work. Progress should be visible. What is shipping. What users are adopting. What is improving. What still needs proof.

FAQ

Product

Integrations

Security

Ownership

Get Salmon

A more open path to integration and distribution.

Have a protocol or integration to ship? Let's connect.