Problem Statements Brainstorming

🎯 The One-Liner Candidates

Technology Evolution Angle

“PHP powered Web 1.0, modern stacks enabled Web 2.0. Solidity powers Web3’s infancy - what will enable its maturity?”
“Assembly allowed experts to build calculators. C allowed thousands to build everything else. Ethereum is assembly.”

User Experience Angle

“Why does my iPhone have 50 apps, but my blockchain only has Bank.app?”
“It’s 2025, and we still can’t build a real forum, a wiki, or a to-do list on-chain.”
“Blockchain superpowers were confined to crypto and NFT ecosystems”

Developer Pain Angle

“Current Web3 doesn’t allow writing powerful apps easily”
“We don’t have powerful dApps yet because it’s too complex and limited”
“Web3 is at its pre-GitHub, assembly/PHP phase”

Trust & Verification Angle

“Blockchain is ‘trustless’ - but the code is too complex to verify, so nobody does”
“When I say ‘blockchain,’ you think ‘cryptocurrency’ (and probably crime)”

📊 Problem Deep Dive

The Assembly Analogy (Detailed)

Historical Context:

Assembly (1940s) → Spreadsheets, calculators
C with includes (1970s) → Operating systems, games, databases
Pattern: Better abstractions = More developers = Better apps

Blockchain Context:

Ethereum/Solidity = Assembly (financial calculators only)
Amigos = C with imports (any app imaginable)
Same pattern: Better abstractions = More developers = Better apps

The GitHub Effect

Before GitHub (2000s):

Open source existed (SourceForge, mailing lists)
High friction, low adoption
Mostly infrastructure projects

After GitHub (2008+):

Explosion of open source
Social coding
Every company uses OSS

The Parallel:

Before Amigos: dApps exist (complex, isolated, financial)
After Amigos: dApp explosion (simple, composable, everything)

💭 Pain Points by Stakeholder

For Developers

Learning Curve: New language (Solidity), new paradigm, new tools
Limited Composability: Can’t easily import and extend others’ work
Debugging Hell: Opaque execution, expensive mistakes
Audit Costs: $50K+ for simple contracts

For Users

App Desert: Only financial apps, where’s everything else?
Trust Issues: “How do I know this is safe?”
UX Nightmare: Wallets, gas, failed transactions
No Network Effects: Apps don’t build on each other

For Investors

Limited TAM: Only DeFi and NFTs
Speculation Focus: No real usage metrics
Developer Exodus: Builders leave for easier platforms
No Moat: Easy to copy financial primitives

🎨 Visual Problem Concepts

The App Icon Comparison

iPhone Home Screen          vs    Blockchain Home Screen
📱 Messages                       🏦 Uniswap
📷 Camera                         🏦 Compound  
🎮 Games                          🏦 Aave
📝 Notes                          🏦 MakerDAO
🎵 Music                          🏦 Curve
🗺️ Maps                          💎 OpenSea
📚 Books                          🏦 1inch
💬 Social                         🏦 SushiSwap

The Evolution Timeline

1970: Assembly → Only experts write basic programs
1980: C appears → Thousands can write complex programs
1990: C++ → Object-oriented revolution
2000: Java/Python → Millions writing web apps
2009: Bitcoin → Revolutionary but script-only (no real apps)
2010: JavaScript → Everyone can code
2015: Ethereum → Back to assembly (Solidity = new complexity)
2018: WASM chains → Rust/C++ support (still need blockchain expertise)
2020: Near/CosmWasm → Multiple languages (but foreign to most devs)
2025: Amigos → The next evolution (native Go, familiar patterns)

🔥 Provocative Framings

The Uncomfortable Truths

“Smart contracts aren’t smart - they’re dumb programs in a smart environment”
“We’ve built a $2 trillion sandcastle on assembly code”
“Blockchain’s killer app is still ‘number go up’”
“We democratized money but aristocratized development”

The Future History

“In 2035, we’ll look back at Solidity like we look at COBOL today - revolutionary for its time, but my god, why did we build everything on THAT?”

💡 Problem Validation Data

Metrics to Gather

Number of non-financial dApps with >10K users: ~0
Average cost to audit a smart contract: $50K+
Time to build a basic forum on-chain: Impossible
Number of Go developers: 5.8M
Number of Solidity developers: ~20K

Quotes to Collect

“I tried to build [X] on-chain but gave up because…”
“The hardest part about Web3 development is…”
“I would build on blockchain if only…”

🎯 The Winner (Recommended)

Short Version: “It’s 2025, and we still can’t build a real forum on-chain.”

Medium Version: “Blockchain promised to revolutionize everything, but after 10 years, we only have financial apps. Why? Because building on blockchain is like programming in assembly - only experts need apply.”

Long Version: “Before GitHub, open source existed but was inaccessible. GitHub unlocked it. Today, dApps exist but are impossibly complex. Amigos will unlock them by making Web3 development feel like Web2 - import, compose, ship.”

Questions for Pitch Refinement

Which problem resonates most with our target audience?
Do we lead with developer pain or user pain?
Is the assembly analogy too technical for VCs?
Should we be more provocative or more analytical?
Do we need blockchain-skeptic and blockchain-believer versions?

problem-statements