Skip to content

Commit 6d8c584

Browse files
shawnmuggleclaude
andcommitted
Add FAQ and rename Product Design to What's Missing
- Add FAQ with 4 questions (stablecoins, Bitcoin payments, wallet storage) - Rename Product Design to What's Missing, focus on current problems - Add examples: wrong chain transfers, Lightning Network privacy - Remove em dashes, more natural writing style - All changes in en/zh/es Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent 385f4b9 commit 6d8c584

13 files changed

Lines changed: 674 additions & 577 deletions

SUMMARY.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,4 +51,5 @@
5151

5252
* [Blog](blogs/en/README.md)
5353
* [Why We Build](blogs/en/20260101-why-we-build.md)
54-
* [Product Design](blogs/en/20260114-product-design.md)
54+
* [What's Missing](blogs/en/20260114-whats-missing.md)
55+
* [FAQ](blogs/en/faq.md)

blogs/en/20260114-product-design.md

Lines changed: 0 additions & 191 deletions
This file was deleted.

blogs/en/20260114-whats-missing.md

Lines changed: 139 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,139 @@
1+
# What's Missing
2+
## Why Crypto Is Still Too Hard, Too Risky, and Too Far From Daily Life
3+
4+
*January 14, 2026*
5+
6+
> This is not a feature list.
7+
> This is an honest look at **what's broken** in the current crypto experience, and why it's keeping most people out.
8+
9+
---
10+
11+
## 1. The Core Problem: Sovereignty Exists, But It's Not Usable
12+
13+
We believe the world is entering an era of individual sovereignty.
14+
15+
But today, that sovereignty is only accessible to a few:
16+
- Self-custody is too hard
17+
- Operations are too complex
18+
- The cost of mistakes is too high
19+
- It can't be used in daily life
20+
21+
The result? Sovereignty becomes "looks free, but actually impossible to use."
22+
23+
---
24+
25+
## 2. What's Missing: The Problems That Shouldn't Exist
26+
27+
### Problem 1: Send to the wrong chain, lose everything
28+
29+
This happens every day:
30+
31+
> "Don't send to Base chain, or your funds will be lost forever."
32+
33+
A user sends USDC to the wrong network. The money is gone. No way to recover it. No customer support. No undo button.
34+
35+
**This should not exist.**
36+
37+
In any reasonable system, sending money to a slightly wrong address shouldn't mean permanent loss. But in crypto today, it does.
38+
39+
### Problem 2: One mistake, total loss
40+
41+
Forgot your seed phrase? Lost your hardware wallet? Clicked a phishing link?
42+
43+
**Your entire net worth, gone.**
44+
45+
There's no recovery. No second chance. No insurance.
46+
47+
This level of risk is not acceptable for mainstream adoption. People shouldn't need to be security experts just to hold their own money.
48+
49+
### Problem 3: Too many chains, too many tokens, too much confusion
50+
51+
- Which chain should I use?
52+
- What's gas?
53+
- Why do I need ETH to send USDC?
54+
- What's a bridge? Why did it take 20 minutes?
55+
- Why is my balance showing on one app but not another?
56+
57+
**Users shouldn't need to understand infrastructure to use money.**
58+
59+
### Problem 4: Can't be used in real life
60+
61+
Even if you successfully hold crypto:
62+
- You can't pay rent with it
63+
- You can't buy coffee with it
64+
- You can't subscribe to Netflix with it
65+
- You can't split a dinner bill with it
66+
67+
Crypto exists on-chain. Life exists off-chain. The two worlds don't connect.
68+
69+
**Sovereignty that can't be used in daily life is not real sovereignty.**
70+
71+
### Problem 5: Security means stress
72+
73+
"Write down these 24 words. Never lose them. Never show them to anyone. If you do, everything is gone."
74+
75+
This is the onboarding experience for self-custody.
76+
77+
**Security shouldn't require constant anxiety.**
78+
79+
Real security should be structural, built into the system, not dependent on users never making mistakes.
80+
81+
---
82+
83+
## 3. What Needs to Change
84+
85+
The correct approach is not to ask users to learn more.
86+
87+
It's to **hide complexity** while **preserving control**.
88+
89+
### Users should only think about:
90+
- How much do I want to send?
91+
- Who do I want to send it to?
92+
- Do I confirm?
93+
94+
### The system should handle:
95+
- Chain selection
96+
- Gas fees
97+
- Bridging
98+
- Error prevention
99+
- Recovery options
100+
101+
### Mistakes should be recoverable:
102+
- Wrong address? Recoverable.
103+
- Wrong chain? Auto-corrected.
104+
- Suspicious transaction? Blocked and reviewed.
105+
106+
### Daily life should just work:
107+
- Pay anywhere
108+
- Any token
109+
- No friction
110+
- No learning curve
111+
112+
---
113+
114+
## 4. The Standard We're Aiming For
115+
116+
| Today's Reality | What Should Exist |
117+
|-----------------|-------------------|
118+
| Send to wrong chain = funds lost | System prevents or auto-corrects |
119+
| Lose seed phrase = total loss | Multiple recovery options |
120+
| Need to understand gas, bridges, chains | User just sees "send money" |
121+
| Can't use in daily life | Works like Apple Pay |
122+
| Security requires expertise | Security is structural |
123+
124+
---
125+
126+
## 5. This Is Not a Technical Problem
127+
128+
All of these problems are solvable.
129+
130+
The technology exists. The solutions exist.
131+
132+
What's missing is **someone building it the right way**, putting user experience first, not blockchain ideology.
133+
134+
> **Sovereignty shouldn't require a PhD in cryptography.**
135+
> **It should just work.**
136+
137+
---
138+
139+
**Other Languages:** [中文](../zh/20260114-whats-missing.md) | [Español](../es/20260114-whats-missing.md)

blogs/en/README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,5 @@ Welcome to the ROZO Blog. Here you'll find our latest thoughts on individual sov
99
## Articles
1010

1111
* [Why We Build](20260101-why-we-build.md) - January 1, 2026
12-
* [Product Design](20260114-product-design.md) - January 14, 2026
12+
* [What's Missing](20260114-whats-missing.md) - January 14, 2026
13+
* [FAQ](faq.md)

0 commit comments

Comments
 (0)