AgroDex fights food fraud in Indonesian by pairing Hedera’s immutable ledger with Gemini AI for auditing in real-time food.
We are excited to announce that this project has been officially selected for Social Summer Of Code (SSOC) 2026.
This project proudly participates in the following open-source programs:
| Program | Program Name | Status |
|---|---|---|
| ♨️ | Social Summer of Code (SSOC) 2026 | Active |
💡 We warmly welcome contributors from all the above programs.
Please check open issues and follow the contribution guidelines before submitting a PR. P.S: Remember that you should be atleast knowing the basic of web3 blockchain using Hedera. If you're not an expert or understand this project, please do not open the issue / PR unless you know it.
The Problem
Food fraud and missing traceability drain billions from Indonesian agricultural sector. Farmers cannot prove premium quality (e.g., organic), and buyers cannot verify authenticity, hurting trust and revenue.
Our Hedera-Based Solution offer AgroDex to creates a digital twin (NFT) for every batch, audited by AI and anchored to Hedera for an immutable trail of evidence.
We chose Hedera because predictable, low fees are the only sustainable option for low-margin Indonesian logistics.
Hedera Services Utilized Hedera Consensus Service (HCS): Every “proof” event (planting, harvest, etc.) is submitted via TopicMessageSubmitTransaction to our topic ID, producing a low-cost (~$0.0001) immutable audit log. Hedera Token Service (HTS): We mint the final certificate as a unique NFT using TokenCreateTransaction.HCS transaction IDs are embedded in the NFT metadata, binding the asset to its evidence trail. Mirror Nodes: The Verify page queries Mirror Nodes (via the SDK) to replay the HCS history and demonstrate authenticity to judges and buyers. Economic Justification Adoption in Indonesia demands sub-$1 fees per transaction. Hedera’s fixed, negligible HCS pricing lets us log thousands of events for a few dollars, keeping the business model viable.
- HCS Logging: Capture every lifecycle event on Hedera Consensus Service.
- HTS Tokenization: Mint NFT certificates that reference the HCS history.
- Verification: Buyers validate authenticity by reading the full Mirror Node history.
- Audit & Trust Score: AI reviews the HCS timeline to produce a 0–100 trust score.
- Bilingual Summaries: Generates provenance summaries in English.
- Buyer Q&A Chatbot: Buyers “talk” to the batch history; AI answers with cited HCS transaction IDs.
- Dashboard Insight: AI provides real-time business insights that surface on the main dashboard.
[Farmer]
|
v
[Frontend (React)] ---- API ----> [Backend (Node.js/Express)]
| | |
| | v
| | [Gemini AI] (Audits & Q&A)
| |
| +---- HCS Submit / HTS Mint ----> [Hedera Network]
|
|
[Buyer]
|
v
[Frontend (React)] ---- API ----> [Backend (Node.js/Express)]
| |
| +---- Reads ----> [Hedera Mirror Node]
|
+---- Displays proofs <------------+
- Operator Account: 0.0.7147874
- Topic ID (HCS): 0.0.7206092
- Demo Token ID (HTS): 0.0.7245654 (serial #1)
This is the instruction about how to get work with this project:
- Clone the Repository
git clone https://github.com/daviddprtma/AgroDex
cd AgroDex- Install Dependencies
pnpm install
- Configure Environment Variables
cp backend/.env.example backend/.env // edit backend/.env and fill: // OPERATOR_ID, OPERATOR_KEY, GEMINI_API_KEY, SUPABASE_URL, SUPABASE_SERVICE_KEY
- Seed the demo data
cd backend node scripts/seedDemo.js - Run the application
# Terminal 1 (Backend)
cd backend
pnpm run dev
# Terminal 2 (Frontend)
cd ..
pnpm run dev-
Star ⭐ and Fork 🍴 this repository.
-
Code Contributions:
- Create a new branch based on the type of change (see Branch & Commit Conventions)
git checkout -b feature/new-section
- Make your code adjustments.
- Commit changes following the convention (see Branch & Commit Conventions).
- Open a Pull Request (PR).
- Create a new branch based on the type of change (see Branch & Commit Conventions)
-
Maintenance Contributions:
- Address issues like:
- Extracting embedded images or assets and adding them to
/assets/. - Moving CSS/JS into separate files.
- Updating README or file structure consistency.
- Extracting embedded images or assets and adding them to
- Submit your PR under the “maintenance” label.
- Address issues like:
| Type | Branch Prefix | Commit Prefix | Description |
|---|---|---|---|
| New Feature | feature/ |
feat: |
Adding new functionality or pages |
| Bug Fix | fix/ |
fix: |
Resolving issues or broken behavior |
| Maintenance | chore/ |
chore: |
Config updates, repo organization |
| Documentation | docs/ |
docs: |
Updating docs, README, or guides |
| UI/UX & Design | uiux/ |
design: |
Design mockups, page revamps, visual tweaks |
| Resources | resources/ |
resource: |
Adding educational content/resources |
| Refactor | refactor/ |
refactor: |
Code improvement without feature change |
| Style | style/ |
style: |
CSS fixes, spacing, or formatting changes |
Example:
# Branch
uiux/community-redesign
# Commit
design: revamp Community page layout for better clarity- [v] Q4 2025 - Testnet Prototype
- [] Q1 2026 - Pilot with Co-ops
- [] Q2 2026 - HashConnect Wallet Integration
- [] Q3 2026- Mainnet Launch & Scaling
Here's the demo video for this project:
For the pitch deck, see it in 👉AgroDex.
