| Client-side encryption | Homomorphic encryption | Blockchain | |
|---|---|---|---|
| Technology | Mature - Uncommon | Mature - Obscure | Immature - Uncommon |
| Development | Difficult | Hard-core | Difficult |
| App | |||
| performance | All application data needs to be stored and processed on the client | All application data stored and processed on the server —> served to the client just-in-time on need-to basis | All application data stored and processed on the chain —> served to the client just-in-time on need-to basis |
| Client-side encrypted Cloud | Blockchain encrypted Cloud | |
|---|---|---|
| Examples | - ProtonMail |
| Client-side encrypted Cloud | Blockchain encrypted Cloud | |
|---|---|---|
| Pros | - Simpler UX (no need for wallet) |
Faster server-side services
Cheaper end-price | - 100% private by default
- Investment opportunities (hot) |
| Cons | - Encryption VS cloud services trade-offs
Open source or not trusted | - Complicated UX (wallet, etc.)
Application performance (sync)
Expensive end-price (trans. fees)
Negative branding (scams) |
Blockchain storage stack is probably too big of a technical risk and significantly narrows down market to users with wallets
Client-side encrypted SaaS (like ProtonMail) seems to be a safer bet offering a better UX from the get-go
Requires further research and and technical assessment of Web3 storage and dApp development solutions.
Tablerone - Suggestions for Tablerone 2.0