ACBU is a stablecoin backed by a basket of African currencies, designed to address currency stability, cross-border payments, and financial inclusion across the continent. Unlike USD-pegged stablecoins, ACBU's value is tied to a weighted basket of 10 African currencies, providing a "continental currency" for intra-African trade and remittances.
- MAIN.MD - Executive summary and entry point to all documentation
- Value Proposition - Core value proposition and target users
- Use Cases - Detailed use case scenarios
- Business Model - Fee structure and revenue model
- Revenue Streams - Detailed revenue breakdown
- MVP Phase - MVP phase documentation and transition strategy
- Architecture - System architecture and blockchain choice
- Pricing Mechanism - How ACBU value is calculated
- Reserve Management - Reserve structure and verification
- Rebalancing - Daily and quarterly rebalancing mechanisms
- Oracle System - Price feed architecture
- Fintech Partnerships - Partner strategy and relationships
- Country Strategy - 10-country rollout plan
- Regulatory - Legal framework and compliance
- Risk Management - Risk mitigation strategies
- User Flows - Detailed user journey scenarios
- Diaspora Remittances - Remittance flows and strategies
- Merchant Integration - Merchant onboarding and integration
- Development Stages - Technical development roadmap with dependencies and risks
- Gap Analysis - Document consistency analysis
- API Specification - Complete API documentation
- Architecture Diagrams - System architecture diagrams (Mermaid)
- Database Schema - Database structure and schema
- Smart Contract Spec - Smart contract interfaces and specifications
- Implementation Plan - Detailed phase-by-phase implementation plan
- Technical Roadmap - Technology stack and infrastructure roadmap
- Task Breakdown - Detailed task breakdown for all stages
- Milestones - Key project milestones with acceptance criteria
- Resource Plan - Team composition, budget, and resource allocation
- Known issues: Contracts, Backend, Frontend
- Catalog consolidations (durable long-form references — single source of truth per domain, discoverable when triaging):
issues/CONTRACTS_ISSUES.md— 60 canonical entries (C-001..C-060); 6 🔴 Critical / 21 🟠 High / 24 🟡 Medium / 9 🟢 Low. Consolidated in PR #22.issues/BACKEND_ISSUES.md— 75 canonical entries (B-001..B-075); 2 🔴 Critical / 21 🟠 High / 38 🟡 Medium / 14 🟢 Low. Consolidated in PR #23.issues/FRONTEND_ISSUES.md— 68 canonical entries (F-001..F-076); 5 🔴 Critical / 15 🟠 High / 25 🟡 Medium / 23 🟢 Low. Consolidated into the canonical format in PR #25; expanded to 68 canonical entries via follow-up canonical-ID migrations in PR #28 (F-066 Skeleton primitive, Medium), PR #29 (F-071 Toast-deletion delay, Medium), and PR #30 (F-076 Frontendrequest()no default timeout, High).
- Catalog consolidations (durable long-form references — single source of truth per domain, discoverable when triaging):
- Read Development Stages for technical roadmap
- Review Smart Contract Spec for contract details
- Check API Specification for integration
- See Technical Roadmap for technology stack
- Start with MAIN.MD for executive summary
- Review Value Proposition and Business Model
- Check Implementation Plan for phases
- Review Resource Plan for budget
- See Fintech Partnerships for partnership opportunities
- Review Country Strategy for market approach
- Check Regulatory for compliance framework
- Basket-Backed: 10 African currencies weighted by GDP, trade, and liquidity
- Low Fees: 0.6% total cost for cross-border transactions (vs 5-8% traditional)
- Fast Settlement: 3-5 seconds on Stellar network
- Transparent: Public reserve dashboard, regular audits, on-chain attestations
- Phased Approach: Start with 3 currencies (MVP), expand to 10
- Stage 0 (Months 1-2): Technical foundation and prototyping
- Stage 1 (Months 3-6): MVP build with 3 currencies
- Stage 2 (Months 7-9): Launch and initial operations
- Stage 3 (Months 10-18): Expansion to 10 currencies
- Stage 4 (Months 19-24): Ecosystem expansion and scaling
Apache License 2.0 - See LICENSE file for details.
Last Updated: June 20, 2026
Status: Planning & Development