← Back to Deck
A1

Core Thesis

  • Salmon builds open wallet infrastructure
  • The core wallet should remain lightweight, reliable, and understandable
  • Selected modular integrations expand what users can do without permanent feature accumulation
  • Partners need a credible path from integration to activation, feedback, usage, and traction
  • Salmon’s wedge is turning selected integrations into measurable distribution
A2

Product Foundation

  • The wallet core focuses on asset control, signing clarity, safety, and reliable interaction
  • Salmon should avoid becoming a heavy financial super-app
  • Useful capabilities can be added as modular integrations / Powerups
  • Powerups should justify their place through real user value
  • Integrations can be improved, deprioritized, or removed without rebuilding the entire product
A3

Partner Wedge

  • Salmon prioritizes partners whose integrations give users a concrete reason to use the wallet
  • Initial target groups include Solana-native applications, NFT communities, self-custody/security tools, infra products, and aligned builders
  • Selection depends on strategic fit, user value, and adoption potential
  • The goal is not to collect integrations, but to prove repeatable user behavior
  • Strategic density matters more than generic wallet volume
A4

Integration Application Pipeline

  • Apply: partner submits use case, users, scope, permissions, maintenance plan, and distribution hypothesis
  • Qualify: Salmon evaluates strategic fit, user value, technical feasibility, and product coherence
  • Build: Salmon and partner define ownership, milestones, dependencies, and implementation path
  • Validate: Salmon reviews security, UX, compatibility, permissions, and operational impact
  • Launch & Measure: approved integrations go live and are measured through activation, usage, retention, and feedback
A5

Integration Evaluation Standards

  • Security: permissions, signing flows, dependencies, attack surface, and user risk
  • User value: clear problem solved for wallet users
  • UX coherence: fit with navigation, flows, and user comprehension
  • Technical compatibility: architecture, performance, and regression risk
  • Maintainability and adoption potential: ongoing support, partner commitment, usage potential, and return behavior
A6

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 mean endorsement or prominent placement
A7

Curation Today and Governance Evolution

  • Today, Salmon is operated by the current team
  • The team owns integration curation and final production approval
  • The objective is accountable curation, not permissionless production
  • If the MetaDAO raise succeeds, the framework can evolve toward community-owned oversight
  • Governance can shape policies, mandates, priorities, budgets, and escalation without reviewing every pull request
A8

Product Status

  • Salmon launched in 2022
  • Salmon is live across browser extension, Android, iOS, and public repository
  • The team has completed launch, relaunch, and deep technical refactor
  • Salmon operates an active Solana validator
  • The next phase is reliability, modular integrations, distribution proof, and governance readiness
A9

One Reliable Experience

  • Users should be able to:
  • Create or import a wallet
  • Receive funds
  • Send transactions safely
  • Understand and approve signing requests
  • Use the integration that brought them to Salmon
  • Return because the product remains useful and reliable
A10

Raise Structure

  • Target Raise: $450,000 gross
  • Approximately $360,000 is intended for operating capital after liquidity provision
  • Monthly operating budget: approximately $30,000
  • The raise funds Salmon's next 12-month execution phase
  • This phase is designed to strengthen the wallet core, establish the Powerup model, and generate measurable evidence of adoption, retention, and ecosystem pull
  • If demand exceeds the target, Salmon may selectively accept additional capital where it materially strengthens execution or runway efficiency
A11

Monthly Operating Budget

  • Team & Product: 70%
  • Infrastructure, Security & SaaS: 10%
  • Powerups & Integrations: 7%
  • Community & Distribution: 7%
  • Legal, Accounting & Governance: 6%
  • Total monthly operating budget: $30,000
  • The allocation is indicative and may vary between categories based on operating needs while remaining within the approved monthly budget.
A12

Roadmap Detail

  • Q4 2026 — Powerup Foundation & First Releases: implement the Powerup framework, move the first core Powerups through testing and staged release, and begin measuring usage
  • Q1 2027 — Core Powerup Expansion: progressively release additional priority Powerups and iterate based on usage, technical performance, and feedback
  • Q2 2027 — Usage & Integration Validation: improve recurring usage, onboard selected ecosystem integrations, and measure partner-driven activity and early economic signals
  • Q3 2027 — Distribution Evidence & Scale Decisions: evaluate Powerups, integrations, transaction activity, fees, validator contribution, and early revenue to determine what deserves deeper investment
  • Each phase moves from controlled product execution toward measurable product, distribution, and economic evidence.
A13

Measurement Framework

  • Wallet adoption: active wallets, new active wallets, activation, return usage, and retained cohorts
  • Powerup behavior: discovery, installations, first use, repeat use, removals, rotation between Powerups, and wallet retention by Powerup cohort
  • Partner funnel: applications, qualified proposals, integrations started, integrations launched, and repeat partner demand
  • Integration performance: users arriving by integration, completed actions, repeat usage, partner feedback, maintenance status, and expansion requests
  • Ecosystem pull: partner referrals, contributor activity, demand for reusable integration tooling, and partner-driven adoption
  • Economic signals: transaction volume attributable to Powerups, fees generated, early revenue, and revenue per active wallet
  • Salmon evaluates product progress through behavior-based, ecosystem, and economic metrics together, reducing dependence on any single measure that may be amplified or suppressed by short-term market conditions.
A14

GTM and Distribution Logic

  • Salmon grows first through selected partner integrations
  • Partner communities and existing use cases provide initial distribution
  • Builders and contributors improve credibility and implementation capacity
  • Public code, visible progress, and integration metrics support trust
  • Salmon avoids broad paid acquisition before proving repeatable activation and retention
A15

Token and Governance Readiness

  • Proposed ownership coin: SALMON
  • No existing token or prior TGE is part of the proposed setup
  • No day-one airdrop or immediate team unlock is planned
  • Proposed team performance package: 5M SALMON
  • The package is subject to an 18-month cliff, 3-month TWAP, and performance brackets at 2x / 4x / 8x / 16x / 32x
  • Tranche allocation: 0.5M / 0.75M / 1M / 1.25M / 1.5M SALMON
  • Higher performance brackets unlock progressively larger portions of the package
  • Governance and token language must remain aligned with the final MetaDAO and legal structure
A16

IP, Asset Readiness, and Disclosure Standards

  • Core assets should be capable of aligning with DAO governance if the raise succeeds
  • Priority assets include brand, domains, GitHub, release accounts, infrastructure accounts, validator-related rights, and contributor rights
  • Launch readiness requires identifying dependencies tied to individuals, vendors, or legacy entities
  • Material obligations should be disclosed before launch
  • The standard is no hidden agreements, no unclear token promises, and no undisclosed asset restrictions
A17

Team and Execution Model

  • Nacho Mileo: product direction, roadmap prioritization, wallet UX, and partner coordination
  • Angel Mazzarello: operations, partnerships, use-of-funds discipline, and community accountability
  • Dario Santos: architecture, security, reliability, integrations, and engineering execution
  • Rodrigo Menendez: legal structure, IP readiness, contributor rights, disclosures, and governance preparation
  • The operating model is lean, clearly owned, and aligned with the planned burn
A18

Prior Funding and Early Build Support

  • Bootstrapped funding: approximately $80,000
  • Serum grant: $2,500
  • Eclipse grant: $40,000
  • Prior resources helped absorb early product and technical risk
  • The current raise funds reliability, integrations, distribution proof, and governance readiness