m-Wallet: the simple, resilient, multi-device hot wallet
📱 Why I use m-Wallet as my main hot wallet
Let me be transparent: yes, this post is a bit self-promotional. But I want to do it properly:
- with verifiable facts,
- with real tradeoffs,
- and without magic promises.
I am not claiming m-Wallet is “the perfect wallet.” The goal is simpler: explain why, today, it is a strong option as a main hot wallet for most users.
Contents
- 🎯 The real hot wallet problem
- 🧱 What m-Wallet actually does (and what I stand behind)
- 1) Non-custodial, without forcing seed-phrase complexity on everyone
- 2) Social login + multiple identities = resilience
- 3) WalletConnect built for daily flow
- 4) QR scanner that is actually useful
- 5) Intent-based transaction history
- 6) Send: The On-Chain Swiss Army Knife
- 7) Buy: a simple on-ramp for beginners
- 🧪 Quick comparison with other approaches
- 🛠️ Real dogfooding: I use it every day
- 🌍 Multi-device: the practical advantage
- ⚠️ Limits (yes, there are some)
- 🗺️ Roadmap (not promises)
- 🧠 Why I think it is a strong choice as your main wallet
🎯 The real hot wallet problem
For many people, the choice looks like this:
- A classic seed-phrase wallet (powerful, but unforgiving when you make mistakes),
- A custodial exchange (simple, but not true self-custody),
- Or a stack of fragmented tools with messy UX.
The weak point is not just security.
The weak point is operational resilience.
What happens:
- when you switch phones?
- when one account is lost?
- when a dApp opens a broken deep link?
- when history becomes unreadable after 50 multi-step transactions?
m-Wallet was built for this middle ground:
- simple enough for daily use,
- serious enough to stay non-custodial,
- robust enough for real-world friction.
🧱 What m-Wallet actually does (and what I stand behind)
1) Non-custodial, without forcing seed-phrase complexity on everyone
m-Wallet is non-custodial by design: Yieldcraft does not hold your funds and cannot sign for you.
At the same time, access can use modern methods (passkey, Google, Apple, etc.), which reduces friction for everyday users.
In short:
- you are not tied to a custodial exchange,
- you do not have to live in fear of losing a 12- or 24-word phrase from day one.
And for advanced users: you can still export a backup key from your Daily Wallet.
2) Social login + multiple identities = resilience
The model is not “one secret or nothing.” You can link multiple access methods:
- passkey,
- Google,
- Apple,
- other supported providers.
Result: lower risk of lockout when one channel fails.
This is not “absolute security.” It is operational resilience, much closer to real life.
3) WalletConnect built for daily flow
m-Wallet treats WalletConnect as a first-class workflow:
- URI/deep-link connection,
- WalletConnect QR scan,
- approval dialog with method/address/params,
- warning when the active wallet does not match the requested address.
That last point matters.
It prevents “automatic” signatures on the wrong account, a common error when juggling multiple wallets.
4) QR scanner that is actually useful
The QR scanner is not only for WalletConnect. It also parses payment/address QR formats when the code is not a valid WC URI.
Result: less back-and-forth, less risky copy-paste, fewer destination mistakes.
5) Intent-based transaction history
This is probably one of the most underrated parts.
Instead of a raw list, history is grouped into readable cards:
TRANSFERSWAPBRIDGEAPPROVE → CALL
The app reconstructs user intent from on-chain legs. In real usage, that is huge: you understand what happened without decoding eight technical lines.
Important bonus for bridges:
- m-Wallet tries to resolve the final recipient,
- and can show “Final recipient” instead of only an intermediate contract address.
That greatly reduces “where did I actually send this?” confusion.
6) Send: The On-Chain Swiss Army Knife
The Send page has become a real execution engine:
- multi-chain,
- multi-wallet,
- multi-token.
The idea is simple: send assets from the context you have to the destination you need, without forcing the rigid model “one wallet = one chain = one token.”
I call it: The On-Chain Swiss Army Knife.
7) Buy: a simple on-ramp for beginners
The Buy page is an entry point for people getting started:
- buy crypto with a bank card,
- more guided flow for non-technical users,
- direct in-wallet integration, so beginners do not need five apps on day one.
For new users, this matters. It shortens the path from “I am curious” to “I made my first proper transaction.”
🧪 Quick comparison with other approaches
| Approach | Main advantage | Main limitation |
|---|---|---|
| Custodial exchange | Easy onboarding | Not true self-custody |
| Classic seed-phrase wallet | Maximum control | Low tolerance for user error |
| m-Wallet (in-app + non-custodial) | Better UX / sovereignty / resilience balance | Still a hot wallet (mobile/web attack surface) |
The right choice depends on your profile.
But for a “main daily wallet,” m-Wallet’s balance is, in my view, stronger than either extreme.
🛠️ Real dogfooding: I use it every day
I am not writing this as product theory. I use m-Wallet myself as my main hot wallet:
- connecting to dApps,
- trading platforms (ex: Hyperliquid, Aster),
- DEX usage like Uniswap.
Why this matters:
when your own main wallet is your product, every friction becomes a priority bug.
That is exactly the continuous-improvement loop I want to keep.
🌍 Multi-device: the practical advantage
I want a wallet that works:
- on mobile,
- on desktop,
- without breaking WalletConnect flow.
m-Wallet works on web and as an installable app (PWA).
There are dedicated flows for iOS, Android, and desktop.
In practice, this covers:
- iPhone / Android,
- desktop (macOS, Windows, Linux),
- through modern browsers or installed app mode.
On native Android, Yieldcraft m-Wallet is already on Google Play: Yieldcraft m-Wallet on Google Play
Native iOS is currently in final-stage development.
In any case, the app is already installable as a PWA and immediately usable through:
- Chrome,
- Safari,
- any other modern browser.
This is not a marketing detail.
It is what prevents broken sessions and unnecessary friction.
⚠️ Limits (yes, there are some)
Let’s be explicit:
- m-Wallet is a hot wallet, so device hygiene still matters.
- If you manage large capital, cold wallet / multisig remains essential.
- Social login improves accessibility, but it does not replace security discipline.
The right setup is not “one tool for everything.” The right setup is simple:
- m-Wallet for daily operations,
- cold wallet / vault for long-term storage.
🗺️ Roadmap (not promises)
What I am targeting next, incrementally:
Native Solana support
Goal: reduce workarounds and provide a truly native Solana experience. Why Solana:- smoother UX for mainstream users,
- fast confirmations,
- very low fees (often fractions of a cent).
Limit orders (swap at target price)
Goal: execute swaps at a desired price, not just at market.
One possible path is integrating building blocks like CoW Swap, but this is still exploratory.Family Vault (long-term m-Wallet vision)
The real long-term target is Family Vault. m-Wallet is only the tool. The destination is your own sovereign family bank: save together, pass wealth on together, and operate under your own rules, not an intermediary’s.
👉 If you want to understand why this is, in my view, the real product endgame, read now:
These are not marketing promises.
This is a transparent product direction.
🧠 Why I think it is a strong choice as your main wallet
Because m-Wallet checks what most users actually need:
- ✅ self-custody without punishing UX,
- ✅ WalletConnect that works in real daily flow,
- ✅ intent-based readable history,
- ✅ realistic multi-device access,
- ✅ explicit security model (no bullshit about fund custody).
If you want a hot wallet that gives you room to breathe without dumbing things down,
then yes: m-Wallet is a serious option.
Not perfect.
But clearly above “acceptable” for demanding daily use.