GitiNext Wallet Backend Documentation

Version: 1.0.0
Last Updated: October 6, 2025
Status: Migration in Progress (Phase 0)

🚀 Quick Navigation

👋 New to the Project?

  1. Start with Introduction
  2. Follow Getting Started
  3. Understand Architecture

🔨 Ready to Code?

  1. Check Migration Overview
  2. Pick a task from Task Breakdown
  3. Follow the Development Guide

📚 Looking for Specific Info?

📖 Documentation Sections

Overview

Get familiar with the project, architecture, and technology stack.

Architecture

Deep dive into system architecture and design decisions.

Migration Guide

Complete guide for migrating from Node.js to Go.

Guides

Step-by-step guides for common tasks.

API Reference

Complete API documentation for all services.

Tutorials

Hands-on tutorials for learning by doing.

🎯 Current Focus: Phase 0 - Foundation

We’re currently in Phase 0 of the migration, focusing on critical infrastructure:

Active Tasks:

  • Task 0.1: Fix TON Signer (IN PROGRESS) 🔵
  • Task 0.2: Fix TRON Signer (PENDING)
  • Task 0.3: Complete TON Watcher (PENDING)
  • Task 0.4: Complete TRON Watcher (PENDING)
  • Task 0.5: Create Balance Service (PENDING)

Progress: 0/5 tasks completed

See Migration Progress for real-time updates.

📊 Project Statistics

  • Total Services: 11 microservices (3 exist, 7 to create, 1 to extend)
  • Migration Tasks: 24 major tasks across 6 phases
  • Estimated Duration: 8 weeks
  • External APIs: 7 integrations
  • Supported Blockchains: 4+ (TON, TRON, ETH, BSC)

Internal Resources:

External Resources:

Code Repositories:

  • Backend (Go): /opt/cryptotel/enterprise/stacks/gitinext/gitinext-golang
  • Frontend (TMA): /opt/cryptotel/enterprise/stacks/gitinext/gitinext-telegram
  • Legacy (Node.js): /opt/cryptotel/enterprise/stacks/gitinext/gitinext-golang/gitibot-back-main

💬 Support & Communication

Getting Help:

  • Documentation Issues: Create GitHub issue with docs label
  • Technical Questions: Ask in #gitinext-backend Slack channel
  • Bug Reports: Create GitHub issue with reproduction steps
  • Feature Requests: Discuss in team meetings first

Contributing:

  • Code: Submit PRs with tests and documentation updates
  • Documentation: Submit PRs for docs improvements
  • Testing: Help with integration testing
  • Review: Participate in code reviews

🎓 Learning Path

For Backend Developers:

  1. Read Introduction (5 min)
  2. Set up Development Environment (30 min)
  3. Understand Microservices Architecture (20 min)
  4. Review Database Schema (15 min)
  5. Pick a Migration Task (start coding!)

For Frontend Developers:

  1. Read API Reference
  2. Check TMA Integration Guide
  3. Follow frontend development workflow

For DevOps:

  1. Review Architecture
  2. Read Deployment Guide
  3. Set up Monitoring

📝 Documentation Standards

Writing Documentation:

  • Use clear, concise language
  • Include code examples
  • Add diagrams where helpful
  • Keep up-to-date with code changes
  • Use markdown formatting consistently

Code Comments:

  • Explain WHY, not just WHAT
  • Document all exported functions
  • Include usage examples
  • Note any gotchas or edge cases

Updating Docs:

  • Update docs in the same PR as code changes
  • Add migration notes for breaking changes
  • Update API reference when endpoints change
  • Keep progress tracker current

🔄 Recent Updates

2025-10-06:

  • 📝 Created complete documentation structure
  • 📋 Documented all 24 migration tasks
  • 🏗️ Documented microservices architecture
  • 🔐 Documented security architecture
  • 🗄️ Documented database schema
  • 📊 Created progress tracking system

📞 Contact

  • Project Lead: [Name]
  • Backend Team: #gitinext-backend (Slack)
  • Documentation: docs@nextgiti.cloud
  • Support: support@nextgiti.cloud

Happy Coding! 🚀

For the latest updates, see Migration Progress

© 2025 GitiNext - Enterprise Crypto Infrastructure | GitHub | Website