Experimental
Limited or controlled release to validate feasibility, UX, and demand.
Lightweight by design. Built to expand around what each user actually needs.
Open-source. Self-custodial. Lightweight. Community-driven.
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
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
A focused foundation for controlling assets, understanding signing requests, and interacting safely with Solana.
Start here
Create or import a wallet, move funds safely, understand what you are signing, and return because the product remains useful and reliable.
Wallet ready
+5.00 SOL received · finalized
sig 5metKx…2PqA · finalized
dapp.example
wants to connect
You approve every connection
Essential wallet activity remains clear, reliable, and understandable.
Future capabilities can be added without becoming permanent weight for every user.
Browser Extension, Web Wallet, Android, and a public open-source repository.
From integration to distribution
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
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.
Share the use case, target users, technical scope, permissions, maintenance plan, and distribution hypothesis.
Salmon evaluates strategic fit, user value, technical feasibility, adoption potential, and product coherence.
Salmon and the partner define ownership, milestones, dependencies, responsibilities, and implementation path.
Security, UX, signing flows, permissions, compatibility, maintainability, and operational impact are reviewed.
Approved integrations move into a controlled or production release with clear responsibilities and support expectations.
Activation, completed actions, repeat usage, retained cohorts, partner feedback, and maintenance status are tracked.
Limited or controlled release to validate feasibility, UX, and demand.
Production-ready integration reviewed for security, UX, compatibility, and maintenance.
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 2026Operating 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.
Manifesto
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.
Product
Integrations
Security
Ownership
Have a protocol or integration to ship? Let's connect.