CraysSovran Money
Sovran Money is not only another wallet. It is a Cashu-first mobile app that treats Bitcoin, Nostr identity, social contact, offline handoff and small everyday payment rituals as one product surface.
The wallet that wants money to feel local again
Sovran Money belongs in the Apps shelf because it is trying to solve a very specific Nostr-and-Bitcoin problem: the user does not want a protocol diagram. The user wants money that can move, contacts that are portable, messages that are not trapped in a platform account, and a phone that can hand value to someone nearby without turning every payment into a tiny banking ceremony.
The official site frames it simply: Sovran is a free, open Bitcoin app for paying anyone, posting freely, messaging friends and handing cash to people nearby. That is a broad promise, but the interesting part is the stack underneath it. The documentation describes a mobile Bitcoin wallet with Cashu ecash, Lightning payments, Nostr messaging and NFC support. The GitHub README goes even further, naming Cashu ecash, Lightning, offline payments, Coco wallet state, Nostr identity, NFC tag handoffs, BitChat BLE mesh, White Noise MLS groups and Routstr AI payments.
That combination makes Sovran feel different from a normal Lightning wallet. A normal wallet starts with balances and invoices. Sovran starts closer to the physical-cash metaphor: tokens live on the device, nearby exchange matters, QR codes and NFC still matter, and a Nostr identity can sit beside the wallet instead of being bolted on later. The product question is not only "can it pay an invoice?" It is "can money, identity and proximity live inside the same everyday app without handing the whole experience to one platform?"
For Crays, that makes Sovran useful even before it becomes a mainstream wallet. It shows where the Nostr app market is moving: not only feeds and signers, but social money surfaces where contacts, payments, groups, mints, messages and AI access begin to share one account-shaped space. That is exciting. It is also risky, because every extra surface adds another trust question.
One app for wallet, social and nearby payments
The easiest mistake is to read Sovran as "a Cashu wallet with a few social features." The public docs point to something wider. The introduction says Sovran combines Cashu ecash, Lightning Network support, Nostr integration, NFC payments and multi-mint support. The architecture page describes a React Native mobile wallet built on Expo, designed around Cashu with deep Nostr integration. The main app routes include feed, wallet, payments and explore surfaces.
That tells you how the product wants to be used. A user can hold spendable ecash, pay or receive through Lightning, post publicly, message friends, manage contacts and use nearby handoff patterns from one mobile shell. The eSIM page repeats the same public positioning in shorter language: Sovran is a free, open Bitcoin app to pay anyone, post freely, message friends and hand cash to nearby people. It is not pitching itself as a developer library. It is pitching an everyday app.
The social side matters because Bitcoin wallets often treat people as invoice endpoints. Nostr gives Sovran a way to turn people back into portable identities. A Nostr contact can be more than a phonebook entry. It can carry a pubkey, profile metadata, followers, relay hints, payment requests, messaging state and reputation clues. That does not make the experience automatically safe, but it changes the shape of the wallet. The address book can become a social graph instead of a static list of recipients.
That also explains why Sovran belongs under Apps, not only Wallets. Wallets are part of the story, but the app is also a Nostr client surface. It cares about feed, messaging, identity, contact discovery and social payment flow. In the Nostr map, it sits near Cashu, Alby, Minibits, White Noise, Routstr and the broader question of what a mobile identity wallet can become.
Cashu is the money layer
Sovran's money design starts with Cashu. The documentation describes Cashu as open-source ecash for instant, private, near-zero-fee Bitcoin transactions, implemented in Sovran through the Coco Cashu libraries. In normal language, Cashu tokens are bearer instruments: whoever holds the proofs can spend them. Mints issue and redeem those proofs against Lightning. The user gains cash-like transfer properties, while taking on mint trust.
That is the central trade. Cashu can make small payments feel fast, private and lightweight. It can also make the user dependent on mints. Sovran's docs are unusually clear about this point: mints have custody of the Bitcoin backing the ecash, so users need to trust the mints they use and spread balances across more than one mint to reduce risk. The app's multi-mint architecture is therefore not a decoration. It is part of the risk model.
The docs say Sovran supports multiple mints simultaneously through Coco state. Balances can be distributed by mint URL, and each mint can carry context such as status and KYM, or Know Your Mint, information. That matters for readers because an ecash wallet can look simple while hiding a hard custody question. If all funds sit at one mint, the user has one big trust dependency. If funds are spread across several mints, the user reduces single-mint exposure but adds operational complexity.
Cashu also explains why Sovran can speak seriously about offline and nearby payments. Ecash proofs can be moved through QR codes, text or NFC because the token itself is the thing being handed around. That is different from a Lightning invoice flow where both sides often need online settlement at the moment of exchange. It does not remove the need to redeem or check tokens later, and double-spend prevention still depends on mint interaction. But it gives mobile product designers a very different material to work with.
Nostr gives the wallet a social spine
Sovran uses Nostr for identity, messaging, contacts, social features and payment requests. The architecture docs say the app uses NDK Mobile, derives wallet identity from a BIP-39 seed through NIP-06, uses NIP-17 gift-wrapped direct messages, keeps contact and follower data, handles profiles and verification, and can send payment requests over Nostr with Cashu NUT-18. That is a lot of protocol surface for a wallet.
The most important detail is the key story. Sovran derives Nostr keys from the wallet seed. The key derivation docs describe a 12-word BIP-39 mnemonic, BIP-32 hierarchical derivation, NIP-06 for Nostr keys and Cashu wallet derivation. The Nostr docs list the Nostr path as m/44'/1237'/account/0/0 in its user-facing form, while the architecture page shows the implementation details around account indexes and secure storage. Keys are cached in platform secure storage to avoid repeated expensive derivation.
That gives Sovran a clean onboarding story: one seed can generate the wallet identity and the Nostr identity. It also raises the stakes. If a wallet seed controls the social key, losing that seed can mean losing both money recovery and identity continuity. If a user uses one Nostr identity across wallet payments, public posting and private messages, that identity can accumulate more correlation than the user expected. A simple onboarding path can become a privacy bundle.
Nostr direct messaging also deserves sober reading. Sovran documents NIP-17 gift-wrapped DMs and NIP-44 encrypted payloads in its architecture. Gift wrapping improves on older NIP-04 style messaging by hiding more metadata and using a better encryption model, but it does not make relays disappear. Relays still move events. Device security still matters. Contact discovery still leaves traces in social behavior. Sovran is right to build on Nostr's modern messaging path; readers still need to understand what it protects and what it cannot hide.
Offline handoffs, NFC and nearby payments
The most distinctive user story in Sovran is not posting. It is nearby money. The official materials repeatedly point at cash-like exchange: NFC payments, handoff to people nearby, and offline payments. The README names NFC tag handoffs and BitChat BLE mesh alongside Cashu, Lightning and Nostr identity. The architecture page lists NFC with the NDEF Type 4 Tag protocol, UR codes, Lightning addresses and LNURL-pay as part of the broader technical environment.
That product direction is worth attention because most Bitcoin wallets still feel internet-first. They are good at invoices, QR codes and remote payments. They are weaker at the ordinary human moment where someone is standing in front of you and you want to hand over a small amount without registering an account, exchanging a phone number or waiting for an app-to-app ceremony. Sovran is trying to make that moment feel more like cash.
NFC handoff is not magic. The receiving side still needs to protect token handling, avoid replay confusion and redeem or swap ecash when appropriate. If the payment moves while one party is offline, final confidence arrives later. That is the nature of bearer tokens. But product design matters here. A wallet that makes the user understand "I handed over a token" can create better expectations than a wallet that pretends every offline gesture is final bank settlement.
The BitChat and White Noise references point to an even more ambitious local-social direction. Sovran is not only imagining one-to-one wallet transfers. It is exploring nearby communication, group messaging and private coordination as adjacent surfaces. That is very Nostr: once identity and signed messages exist, many product flows begin to converge. The hard part is making the convergence understandable instead of turning the app into a basement full of switches.
The code trail and current status
The public code trail is concrete. The main repository is SovranBitcoin/Sovran, created in December 2024, public under the Mozilla Public License 2.0, and listed by GitHub as TypeScript. On June 18, 2026, the GitHub API showed the repository updated on June 17, 2026, with the public description "A mobile Cashu wallet", the homepage set to sovran.money, 23 stars, one fork and ten open issues. Those numbers are not a quality score. They show a young, active project rather than a settled wallet with years of production usage.
The README describes the current app as Expo and React Native, iOS-first, with Android configuration and fallbacks present but not the production target. It lists iOS 16.4 as the primary minimum target and version 0.1.0 in app.json. It also notes that on-chain Bitcoin inputs are recognized by the parser and BIP-321 option ranking, but on-chain send and receive are not shipped yet. That is exactly the sort of status line a reader needs. Sovran can parse the wider Bitcoin world, but its current product center is Cashu, Lightning and mobile app flow.
The docs confirm the mobile architecture: React Native 0.83, Expo SDK 55, Expo Router, TypeScript, HeroUI Native, Uniwind, Reanimated, Zustand, AsyncStorage and expo-secure-store. Protocol support includes Cashu NUTs, Nostr NIPs, Lightning BOLT11, BIP-39 and BIP-32. This is not a thin landing page wrapped around a closed backend. There is a public codebase and a documentation set that lets a technical reader trace the major claims.
The docs also point to a built-in Routstr AI chat integration. Sovran can use wallet sats for pay-per-message access to AI models through Routstr. That is not the core wallet function, but it reveals the product's larger thesis: once the app holds spendable ecash and Nostr identity, other services can become small paid actions inside the wallet. AI prompts, eSIMs, messages, payment requests and local handoffs can all become app tabs around one identity-money core.
Where the trust model bites
Sovran has a strong idea, but the trust model has teeth. Cashu gives privacy and speed by using mints. Mints can fail, disappear, censor, lose backing or run policies the user dislikes. Multi-mint support helps, but it does not remove mint risk. A careful reader keeps only the amount they are comfortable holding as ecash, chooses mints deliberately and treats mint diversification as real work.
The seed model is another sharp edge. A single BIP-39 seed can give a simple recovery story, but if that seed connects wallet recovery and Nostr identity, the user must protect it like both money and public reputation. A compromised seed is not only a lost balance risk. It can also become an identity compromise. A lost seed can cut off future recovery. That is not a reason to reject Sovran. It is a reason to treat setup and backup as part of the product.
The social side adds correlation. Posting publicly, following people, messaging friends, requesting payments and paying through ecash can create patterns. Nostr makes identity portable, not invisible. Cashu can improve payment privacy, especially against observers who would otherwise see direct Lightning flows, but app-level behavior still creates a picture. If a user wants separate lives, they need separate account practices and careful mint choices.
Finally, Sovran is young. The repo status, version number and iOS-first posture matter. It may be exactly the kind of app early Nostr users need to study, test and help improve. It is not yet something to treat as boring financial infrastructure for large balances. The honest path is to test it with small amounts, read the repository, follow the docs and watch how releases handle bugs, recovery and mint failures.
How to test Sovran without romance
Begin with a tiny balance and a fresh mental model. Create or restore a wallet, write down how the seed is protected, then derive or view the Nostr identity connected to that wallet. Ask one simple question: if this phone disappears tonight, what exactly can be recovered and what cannot?
Next, test Cashu without touching large funds. Add more than one mint if the app flow allows it. Receive a tiny amount, send a tiny amount, swap or redeem if available, and observe how the balance is represented by mint. If a mint is unreachable, check how the app explains that state. A good ecash wallet makes mint risk visible without frightening the user into paralysis.
Then test the Nostr layer. Post something harmless, follow a contact, send a small message and check whether another Nostr client can recognize the same public identity. If Sovran creates a payment request over Nostr, inspect how that request appears and whether it remains understandable outside the app. Portability is the whole point of choosing Nostr here.
Only after that, test the nearby payment story. Use NFC or QR flows with tiny tokens. Try a handoff with one device offline if the current app path supports it. Then bring the receiver online and redeem or settle the token. That test teaches the user what "cash-like" really means in practice. The goal is not to fall in love with the metaphor. The goal is to understand exactly where finality, privacy and custody enter the flow.
Sovran sources worth opening
Open the official site first for the product promise, then move through the docs and repository to see the actual wallet, Nostr, key and Cashu architecture.
- Sovran Money official site
- Sovran eSIMs page
- Sovran documentation introduction
- Sovran architecture overview
- Sovran Nostr integration architecture
- Sovran Nostr overview
- Sovran key derivation documentation
- Sovran Cashu protocol overview
- Sovran Routstr AI integration
- Sovran GitHub organization
- Sovran GitHub repository
- Sovran repository README
- Awesome Cashu wallet index
