Skip to content
Samui

Public Roadmap

Samui Wallet Public Roadmap

This roadmap shares what the Samui team is building now, what’s next, and where the community can have outsized impact. It reflects current priorities and sequencing.

In addition, please take a look at our open GitHub issues.

How to read this

  • Now = in flight or imminent.
  • Next = queued after “Now,” dependent on feedback/uptake.
  • Later = larger bets or items gated on ecosystem maturity.
  • Each item lists Why, What, Status/Target, Issue/PR, and Community (whether it’s a good fit for external contributors).

How to contribute

  • Pick a “Community” item below, then open a GitHub Issue in this repo with the title: Roadmap: <item> — Contribution Proposal.
  • In your issue, include: goals, approach/design sketch, deliverables, estimated timeline, and how you’ll demo/measure success.
  • The Samui team will review and offer consulting (design feedback, API guidance, intros) so you can ship confidently.
  • Docs are credibly neutral and community‑owned: contribute guides, templates, and examples to the GitBook repo → https://github.com/murrlincoln/x402-gitbook (PRs welcome).

Recently shipped

  • Samui Wallet Hackathon submission

    • Why: Samui Wallet participated in the Cypherpunk Hackathon by Colosseum.
    • What: An initial version of the web version of Samui Wallet.
    • Status/Target: Shipped – Oct 30, 2025.
    • Community: Initial feedback and feature requests, pull requests and issues.

Now

  • User Settings

    • Why: DECIDE ON THE WHY.
    • What: Settings need to be loaded at boot time so that they are available.
    • Status/Target: Scoping → Before Breakpoint (next major release); ~2 weeks dev + spec approval + ~3 weeks audit.
    • Issue/PR: https://github.com/samui-build/samui-wallet/issues/342
    • Community: Work will be done by the core team.

  • OpenAPI endpoints + SDK

    • Why: We need a consistent and type-safe way to connect with the API from our clients.
    • What: Expose an OpenAPI endpoint and generated an SDK.
    • Status/Target: Scoping → Before Breakpoint (next major release); ~2 weeks dev + spec approval + ~3 weeks audit.
    • Issue/PR: TBD
    • Community: Work will be done by the core team.

  • Add main Wallet functionality to the extension

    • Why: The extension and web wallet need to have feature parity.
    • What: Load the wallet shell in the extension, connect signing logic and wallet-standard adapter.
    • Status/Target: Scoping → Before Breakpoint (next major release); ~2 weeks dev + spec approval + ~3 weeks audit.
    • Issue/PR: TBD
    • Community: Work will be done by the core team.

Next

  • Mobile App for Solana Seeker

    • Why: THE WHY.
    • What: THE WHAT.
    • Status/Target: THE WHEN.
    • Issue/PR: THE ISSUE
    • Community: THE COMMUNITY.

  • Privacy features

    • Why: THE WHY.
    • What: THE WHAT.
    • Status/Target: THE WHEN.
    • Issue/PR: THE ISSUE
    • Community: THE COMMUNITY.

Later

  • CLI App

    • Why: THE WHY.
    • What: THE WHAT.
    • Status/Target: THE WHEN.
    • Issue/PR: THE ISSUE
    • Community: THE COMMUNITY.

  • Desktop App

    • Why: THE WHY.
    • What: THE WHAT.
    • Status/Target: THE WHEN.
    • Issue/PR: THE ISSUE
    • Community: THE COMMUNITY.

Explicit community call‑outs (start here)

If you want to contribute, these items are especially well‑scoped for community ownership. Open an issue and we’ll co‑design with you:

  • NFT Support Load and render NFTs using the DAS api. Needs issue for specs.
  • More Community Items

Claiming a community item, or propose a new one!

  1. Open a GitHub Issue titled Roadmap: <item> — Contribution Proposal.
  2. Include problem, proposed approach, milestones/deliverables, and demo plan.
  3. We’ll respond with feedback and assign a CDP point‑of‑contact for consulting.

This roadmap is living; sequencing may change based on developer feedback, adoption, and partner timelines.

Credits

The structure of this roadmap is inspired by the x402 roadmap.