Everything App
What's the first thing you trust with your money?
The wallet is the trust interface. Every transaction, every identity claim, every interaction with a decentralized application runs through it. Get it wrong and people lose money. Get it right and it becomes the surface through which everything else compounds.
The Job
The wallet has one job: make the user's next action safe and obvious.
| What users say | What users do | The real job |
|---|---|---|
| "I need a wallet" | Choose whichever has least friction | Find the shortest path to transact |
| "Security matters" | Skip seed phrase backup | Avoid thinking about loss |
| "I want self-custody" | Panic when something goes wrong | Feel in control without bearing all the risk |
The stated need and actual behavior diverge. The wallet that wins aligns safety with the path of least resistance — a pit of success where doing the safe thing is easier than doing the unsafe thing.
The Safety Gap
On January 2, 2026, an official Solana Mobile notification deleted a seed phrase without warning. ~$10K gone. No confirmation dialog, no balance check, no recovery path.
In a factory, that's a near-miss report. It becomes a procedure. The procedure becomes a standard. The standard prevents it from happening to anyone else.
Crypto wallets don't have shared safety standards. Each team navigates the tension between security and usability independently. The same failure modes get rediscovered by every team.
| What factories have | What wallets don't |
|---|---|
| Near-miss reporting | Incidents buried in support tickets |
| Safety procedures | Each team invents their own |
| Cross-site standards | Patterns locked inside companies |
| Commissioning gates | Ship and hope |
Safety is an architectural constraint, not a feature. The best safety code is code that doesn't need to exist because the platform prevents the failure.
The Path
Wallet evolves into identity hub evolves into everything app. Each stage compounds on the last.
| Stage | What It Does | What Compounds |
|---|---|---|
| Wallet | Safe transactions, key management | Trust — users prove the interface works |
| Identity | Verifiable credentials, reputation | Portability — your history follows you |
| Everything | Discovery, commerce, governance, play | Network effects — each app strengthens the surface |
zkLogin points where this goes. Sign in with Google. No wallet install, no seed phrase, no network switching. The wallet disappears as a user-facing concept — what remains is the trust layer underneath.
Engineering
Three methodologies drive the build:
| Method | What It Ensures |
|---|---|
| Flow Engineering | Every map produces a code artifact — P&IDs for software |
| Type-First | Domain drives architecture — the compiler is the methodology |
| Product Design | Measurable thresholds for every decision — not opinions |
Safety patterns emerge from the intersection. Flow maps identify where destructive operations live. Types enforce that resources can't be silently destroyed. Design thresholds verify the user actually sees what they need to see.
Dig Deeper
🗃️ Crypto Toolkit
2 items
📄️ Wallet Specs
How do make your wallet fool proof?
🗃️ Abstraction
4 items
🗃️ JTBD Function Superset
3 items
📄️ Crypto Wallets
What use is a Crypto Wallet? Can you trust it?
Context
- Jobs to Be Done — The job is safe progress, not features
- Standards — Where safety patterns graduate to
- The Incident — The near-miss report that revealed the gap
- DePIN — Physical devices need wallet interfaces
- Onboarding — First impressions determine trust
- Sui Technical — Object model that prevents failure classes at the language level