Docs · Product
Roadmap.
A living document, updated as things ship and as we hear feedback. If a feature you need isn't listed, tell us — see the last section.
Principles
Every roadmap item is filtered through three questions:
- Does it keep custody where it belongs? Users keep their keys and their funds. We don't become a middleman.
- Does it survive without our infrastructure? Every feature should stay usable even if
claima.fundisappears — either by being fully on-chain, or by being a small standalone client. - Is it worth the added surface? Every new surface is a new bug. We say no to more things than we say yes to.
Shipped
Everything currently live in production:
- Client-side AES-256-GCM encryption of temp wallet + note
- PBKDF2 250k rounds password derivation
- URL fragment payload (v2) — server never sees the blob
- Sender flow (/c/new) with balance, fee preview, strength meter
- Receiver flow (/c) with network mismatch warning, post-claim verification
- Local history (/c/mine) with claimed / active / unfunded status
- Phantom + Solflare wallet adapters, Wallet Standard discovery for others
- Devnet + mainnet-beta support via env flag
- Public docs: intro, quickstart, how-it-works, security, verify, URL spec, FAQ
- Terms & Conditions, Privacy Policy pages
Next up
What we're actively working on or actively planning. Order reflects rough priority.
[01]
SPL tokens (USDC first)
Support locking USDC and other SPL tokens by handling Associated Token Accounts on both create and claim flows. Enables non-volatile drops (USDC gifts, USD-denominated bounties).
[02]
Anchor on-chain program
Replace the ephemeral-keypair vault with a Program Derived Address controlled by an Anchor program. Enables sender-side reclaim without needing to remember the password, and cleaner audit trails.
[03]
Expiration timestamps
Links that automatically expire after a configurable window. After expiry the sender can reclaim without racing against unclaimed recipients.
[04]
Mobile Wallet Adapter
First-class support for Phantom mobile, Solflare mobile, and Backpack mobile via deep-link + universal-link flows. Currently the mobile browser experience depends on the wallet's in-app browser.
Later
Things we want to build once the "next up" block is shipped.
[01]
Multi-claim splits
One link, multiple sub-claims — e.g. a single URL shared with 10 recipients, each with their own sub-password. Useful for team payroll and airdrops.
[02]
SDK for embed
A small JS package (~15 KB) that lets other apps generate and consume CLAIMA links without pulling in the full site. Great for game studios and community-tool builders.
[03]
Verifiable-build attestation
Sigstore-style signed builds so anyone can verify the deployed bundle matches a specific commit hash — closes the gap between /docs/verify and "but how do I know what's really deployed."
[04]
Additional wallet integrations
Explicit adapters for hardware wallets (Ledger through the wallet's software) and less-common but active wallets (Glow, Magic Eden). Auto-discovery covers most, but explicit UX polish is worth the effort.
Not doing
A short list is the honest one. If any of these change we'll update this page loudly.
Custody, escrow, or arbitration
We won't hold funds, mediate disputes, or freeze links. CLAIMA is a peer-to-peer tool — if a sender and recipient disagree, that's outside our surface.
Off-chain analytics on your links
We won't add server-side counting of who opened what. The value of the URL-fragment design is that we can't see it. If you want private analytics, run your own client-side tracking.
KYC or identity gating
CLAIMA doesn't ask who you are. We are not planning to. Anyone with a Solana wallet, on-chain, can create and claim.
Influence the roadmap
The best way to move something up the queue is to describe a concrete use case where you'd rely on it. DM the X / Twitter account in the footer with:
- What you're trying to do (one paragraph).
- What's blocking you on the current shipped surface.
- Whether you're a builder, a community lead, or a user.
We won't promise to build anything, but real-world requests are the strongest signal we get.