Nimo: Decentralized Youth Identity & Proof of Contribution Network

🚀 Production-Ready | 💳 Cardano-Powered | 🤖 AI-Driven | 🌐 Multi-Chain

Overview

Nimo is a decentralized reputation system built on Cardano blockchain and MeTTa language that enables African youth to create persistent digital identities, earn reputation tokens for real-world contributions, and use their identity and reputation to unlock access to opportunities like internships, grants, gigs, and DAO proposals.

✨ Key Features

🏗️ Decentralized Identity & NFTs

Unique, transferable NFT identities on Cardano

*Persistent digital identity with cryptographic proof of ownership*

🎯 Smart Contract Integration

Immutable contribution records with automated token awards

*Transparent, tamper-proof contribution verification system*

💰 Native Token Economy

NIMO tokens for reputation rewards and opportunity access

*Economic incentives for meaningful community contributions*

🌍 Impact Bond Marketplace

Decentralized funding for local projects

*Community-driven investment in African youth initiatives*

🤖 MeTTa Autonomous Agents

AI-powered contribution verification and reward calculation

*Intelligent automation with transparent reasoning*

🔐 Multi-Chain Support

Cardano primary with Base Network compatibility

*Cross-platform interoperability and future-proof architecture*

<style> .feature-card:hover { transform: translateY(-5px) !important; box-shadow: 0 20px 40px rgba(0,0,0,0.3) !important; } </style>

🚀 Quick Start

Prerequisites

• Python 3.9+ with pip
• Node.js 18+ with npm
• Cardano wallet (Yoroi, Daedalus, or Eternl)
• Blockfrost API account

Setup (3 minutes)

# Clone repository
git clone <repository-url>
cd Nimo

# Backend setup
cd backend
python -m venv venv
source venv/bin/activate  # or venv\Scripts\activate on Windows
pip install -r requirements.txt
flask run

# Frontend setup (new terminal)
cd ../frontend
npm install
npm run dev

# Smart contract setup
cd ../contracts/cardano
python mock_deploy.py preview

Access the application:

• Frontend: http://localhost:5173
• Backend API: http://localhost:5000

📁 Project Structure

Nimo/
├── README.md                    # This file - Project overview
├── LICENSE                      # MIT License
├── package.json                 # Frontend dependencies
├── contracts/                   # Cardano smart contracts (Aiken/Plutus)
├── backend/                     # Flask REST API (92 endpoints)
├── frontend/                    # React 18 + TypeScript + Vite + Tailwind
├── docs/                        # Comprehensive documentation
├── hyperon-experimental/        # MeTTa AI reasoning files
└── scripts/                     # Development and deployment tools

🛠 Technology Stack

Frontend	Backend	Blockchain	AI & Logic
React 18.3.1 Modern UI framework	Flask 3.0.3 RESTful API server	Cardano Sustainable blockchain	MeTTa Language Autonomous reasoning
TypeScript 5.8.3 Type-safe development	SQLAlchemy 2.0.32 Database ORM	Plutus v2 Smart contracts	Hyperon Runtime AI processing
Vite 5.4.19 Lightning-fast builds	MeTTa AI (PyMeTTa 0.1.1) Intelligent verification	Blockfrost API Network access	Fraud Detection 96% accuracy
Tailwind CSS 3.4.17 Utility-first styling	Redis Caching Performance optimization	Native Tokens Built-in multi-asset	Confidence Scoring Multi-factor analysis

📚 Detailed Documentation

For comprehensive technical details, implementation guides, API documentation, and development resources, see the docs/ directory:

• 🏗️ Technical Architecture - System design and components
• 🔌 API Documentation - Complete API reference
• 🛠️ Development Guides - Setup, deployment, and contribution guides
• 🔒 Security Documentation - Security measures and compliance
• ⛓️ Blockchain Integration - Cardano and smart contract details

🤝 Contributing

We welcome contributions! See docs/development/README.md for:

• Development workflow and testing requirements
• Code standards and TDD approach
• Areas for contribution (MeTTa rules, smart contracts, frontend components)

📄 License

MIT License - see LICENSE for details.

💬 Support

For questions, issues, or contributions, please refer to the appropriate documentation in the docs/ directory or create an issue in the GitHub repository.