How rohitguddin/carbonchain-decarbon-byquantumnodes works
DeCarbon lets cultivators submit plantation evidence for plant identification and approval, then earn and price credits; companies browse and purchase credits. Transactions, wallet balances, invoices, and public carbon-impact views support that lifecycle. The graph includes the documented web and mobile clients, backend domain modules, and persistent state. Backend routing and several screens are only documented or partially sampled, so uncertain call-level links are omitted; optional Gemini and Razorpay integrations are dashed.
Main entry points: app.py Backend API · api.js Web API client · App.jsx Web application · models.py Domain records
Components 20
User clients
- Web application
frontend/src/App.jsx - Mobile application
mobile/src/screens - Web API client
frontend/src/utils/api.js - Mobile API client
mobile/src/utils/api.js
Plantation verification
- Plantation submission
frontend/src/pages/Cultivator.jsx - Mobile upload
mobile/src/screens/UploadScreen.js - Plant analysis
nccr-backend/ai.py - Plantation approval
nccr-backend/app.py
Credit trading
- Credit marketplace
frontend/src/pages/Marketplace.jsx - Credit payment
nccr-backend/app.py
Records and impact
- Backend API
nccr-backend/app.py - Domain records
nccr-backend/models.py - Application database
nccr-backend/config.py - Wallet and history
mobile/src/screens/WalletScreen.js - Transaction explorer
frontend/src/pages/Explorer.jsx - CO2 profile
frontend/src/pages/Explorer.jsx - Invoice generation
nccr-backend/invoice.py
Other components
- Cultivators
- Companies
- Razorpay
Connections 27
- Cultivators → Web application: use
- Companies → Web application: use
- Cultivators → Mobile application: use
- Web application → Plantation submission: route to
- Plantation submission → Web API client: submit via
- Mobile application → Mobile upload: route to
- Mobile upload → Mobile API client: submit via
- Web API client → Backend API: request
- Mobile API client → Backend API: request
- Backend API → Plant analysis: analyze image
- Plant analysis → Razorpay
- Backend API → Plantation approval: process request
- Backend API → Domain records: read and write
- Plantation approval → Domain records: create credits
- Credit marketplace → Web API client: request data
- Companies → Credit marketplace: browse and buy
- Credit marketplace → Backend API: purchase request
- Backend API → Credit payment: handle purchase
- Credit payment → Razorpay: create and verify
- Credit payment → Domain records: record transfer
- Domain records → Application database: persist
- Mobile application → Wallet and history: show balances
- Wallet and history → Mobile API client: fetch credits
- Web application → Transaction explorer: route to
- Transaction explorer → Web API client: fetch transactions
- Web API client → CO2 profile: request profile
- Backend API → Invoice generation: generate PDF