← Back to Deck
A1

Product Status

  • Live product across browser extension, web wallet, and Android
  • Public open-source repository with ongoing development in the open
  • Structural relaunch completed with new team and deep refactor
  • Product now positioned for platform expansion and scale
A2

Why the Wallet Layer Matters

  • Wallets are the main user interface to crypto
  • They shape access across chains, apps, and governance
  • They are a point of control over discovery and integrations
  • They function as a strategic distribution layer
A3

Why Closed Wallet Control Is a Problem

  • Product decisions remain centralized
  • Integrations can be selectively prioritized
  • Monetization logic stays opaque
  • Open ecosystems remain dependent on closed access layers
A4

Why Salmon's Target Segment Matters

  • Crypto-native users influence broader adoption disproportionately
  • Builders and contributors amplify the tools they trust
  • High-alignment users create stronger ecosystem credibility
  • Strategic density matters more than raw user count
A5

Execution Priorities

  • Product: maintain core wallet features and improve UX reliability
  • Infrastructure: strengthen security, performance, and operational resilience
  • Platform: expand mobile parity and multi-network support
  • Distribution: deepen integrations, tooling, and community-led growth
A6

Strategic Positioning

  • Salmon is not a convenience-first mass wallet play
  • Salmon is an open wallet infrastructure play
  • The wedge is alignment, transparency, and ecosystem fit
  • The ambition is to become the wallet most aligned with this ecosystem
A7

Why the Timing Is Better Now

  • Open infrastructure is regaining relevance
  • Crypto-native coordination is more mature
  • Serious builders increasingly value verifiable tools
  • Salmon now has product, team, and timing aligned