Amigos Technical Vision

🔮 The Dream vs MVP Matrix

The Amigos VM

🌟 Long-Term Dream

• Modular VM: Connect to SQL databases, external APIs, any service
• Perfect Efficiency: Better performance than compiled Ethereum contracts
• Universal Runtime: Same code runs on blockchain, server, browser, IoT
• Hot-swappable Modules: Upgrade VM capabilities without hard forks
• Multi-language Support: Go today, Python/JS/Rust tomorrow

✅ Good V1/MVP

• Go Import System: import "hub.amigos.dev/contract" just works
• Persistent State: Global variables maintain state between calls
• Function-Level Calls: Call individual methods, not just contracts
• Deterministic Execution: Reproducible across all nodes
• Standard Gas System: Predictable costs, compatible with existing tools

🔬 Technical Innovations

// This is what we're enabling:
import (
    "hub.amigos.dev/social/forum"
    "hub.amigos.dev/identity/ens"
    "hub.amigos.dev/storage/ipfs"
)

func CreatePost(title string) error {
    author := ens.Resolve(msg.Sender)
    post := forum.NewPost(title, author)
    post.Storage = ipfs.Pin
    return post.Publish()
}

The Tooling Suite

🌟 Long-Term Dream

• Static Site Generation: amigos build --static ./ generates full website
• Universal Serialization: Auto-generate JSON/GraphQL APIs from any contract
• IPFS Integration: Seamless content addressing for large data
• AI-Assisted Development: Copilot for smart contract security
• Visual Programming: Drag-and-drop contract composition

✅ Good V1/MVP

• Amigos Hub: GitHub-like interface for browsing live contracts
• Smart Rendering: Contracts can define their own UI via Render()
• Live Documentation: Auto-generated docs from code + state
• One-Click Deploy: From local to testnet to mainnet
• Developer Portal: Tutorials, examples, best practices

🛠️ Developer Experience Goals

1. Zero to Deploy in 5 Minutes: Not 5 days
2. Readable URLs: hub.amigos.dev/social/twitter not 0xaBc123...
3. p/amigos/testable-documentation|Testable Documentation: Every snippet runs, every example works
4. Composable UI: Import UI components like logic

The Network Architecture

🌟 Long-Term Dream

• Horizontal Scaling: Spin up new chains for specific use cases
• P2P Mode: Run personal nodes at username.amigos.net
• Performance Clusters: AWS-hosted high-performance nodes
• Cross-Chain Native: Import contracts from other Amigos chains
• Rollup Everything: Deploy to Bitcoin, Ethereum, any chain

✅ Good V1/MVP

• Cosmos PoS Chain: CometBFT (Tendermint1), proven architecture
• Standard Stack: No custom consensus experiments
• Multi-Network Ready: V1 on Cosmos, future networks flexible
• Clear Upgrade Path: Start with proven tech, innovate later
• Testnet Paradise: Infinite free testnets for experimentation

The Apps Ecosystem

🌟 Long-Term Dream

Decentralized Knowledge:

• Wikipedia that can’t be censored
• Stack Overflow with cryptographic reputation
• Academic journals with transparent peer review

Decentralized Social:

• Forums with governance built-in
• Chat that owns its infrastructure
• Social networks with user-owned algorithms

Decentralized Gaming:

• Minecraft server registry on-chain
• Chess with provable fairness
• Achievement systems across games

Decentralized Business:

• Company incorporation and governance
• Supply chain transparency
• Collaborative document editing

✅ Good V1/MVP

Internal Dogfooding First:

• Team chat on-chain
• Project management dApp
• Proposal voting system
• Internal wiki/documentation

Then Public Basics:

• Simple forum implementation
• Basic social profiles
• Minimal viable DAO toolkit
• Token-gated communities

🏗️ Architecture Decisions

Why Go?

• 5.8M developers: Massive untapped market
• Familiar Syntax: No new language to learn
• Built for Services: Go was designed for networked applications
• Deterministic: Can be made deterministic unlike JS/Python
• Performance: Compiled language benefits

Why Blockchain-Optional?

• Progressive Decentralization: Start centralized, decentralize over time
• Use Case Flexibility: Not everything needs global consensus
• Cost Efficiency: Only pay for decentralization when needed
• Developer Freedom: Choose the right tool for the job

Why Import-Based Composition?

• Proven Model: NPM has 2M+ packages
• Network Effects: Each package increases platform value
• Reduced Complexity: Don’t reinvent the wheel
• Trust Through Transparency: Can audit imported code

🧪 Technical Challenges & Solutions

Challenge: State Management Across Imports

Solution: Copy-on-Write (COW) hierarchical state trees

// Each import gets its own state namespace
state := amigos.State()
forumState := state.For("hub.amigos.dev/forum")
userPosts := forumState.Get("users").Get(userID).Get("posts")

// COW ensures efficient storage - only deltas stored
// Every state change creates a lightweight snapshot
// Natural git-like versioning for all state

Challenge: Deterministic External Calls

Solution: Oracle system with consensus

// External data requires oracle consensus
price := oracle.Fetch("ETH/USD", 
    oracles.Chainlink,
    oracles.Band,
    oracles.Uma,
).Median()

Challenge: Upgrade Coordination

Solution: Semantic versioning with compatibility rules

import "hub.amigos.dev/token@v2"
// Automatically uses v2 if compatible, warns if breaking

💡 Unique Differentiators

1. Import Economy

Unlike Ethereum where you copy code, in Amigos you import live services. The original developer benefits from usage.

2. State Portability

Fork a service WITH its state. Users can migrate to better implementations without losing data.

3. Execution Transparency

Not just “view source” but “view execution”. See exactly how any result was computed.

4. Progressive Decentralization

Start with a simple hosted version, gradually add blockchain properties as needed.

🎯 Success Metrics

Technical Goals

• [ ] < 1 second block time
• [ ] < $0.01 average transaction cost
• [ ] 10K+ TPS on performance network
• [ ] 5-minute developer onboarding

Ecosystem Goals

• [ ] 1000+ packages in first year
• [ ] 10+ non-financial apps with real users
• [ ] 50+ companies building on platform
• [ ] 1M+ monthly active developers

🚧 Open Technical Questions

1. Import Security: How to sandbox imported code while maintaining performance?
2. State Migration: How to handle breaking changes in stateful services?
3. Cross-Chain Imports: Solved by p/amigos/internode-protocol|internode protocol
4. Privacy: How to enable private state in a transparent system?
5. Incentive Alignment: How to reward infrastructure providers fairly?
6. Governance: How to upgrade core protocol without hard forks?

🔬 Research Directions

• p/amigos/progressive-decentralization|Progressive Decentralization: Web2 to Web3 evolution
• p/amigos/edge-networking|Edge Computing: Weshnet integration for offline-first
• p/amigos/internode-protocol|Internode Protocol: Universal node communication with chat
• Transpiler Enhancement: Auto-convert standard Go to persistent state
• ZK Integration: Privacy-preserving execution proofs
• WASM Compilation: Browser-native execution
• AI Assistance: Code generation and audit assistance
• Formal Verification: Mathematical proofs of correctness
• Quantum Resistance: Future-proof cryptography

📚 Technical Inspirations

• Go Modules: Proven dependency management
• GitHub: Social coding and discovery
• NPM: Package ecosystem dynamics
• Docker: Container composition patterns
• Kubernetes: Orchestration concepts
• IPFS: Content addressing
• Ethereum: Smart contract pioneers
• Cosmos: Modular blockchain architecture

See also

• p/amigos/pitch-deck
• p/nt/gno