Project Info
The Spark:
Inspiration
& Problem The core inspiration for Project Trinetra emerged from what we call the “Trust Gap” in autonomous decision-making. While AI is exceptional at reasoning and executing complex actions, and blockchain provides a foundation for immutable trust, there exists a crucial disconnection: How can an AI-driven financial transaction be verifiably tied to an authentic, untampered, real-world condition? Most existing systems rely on centralized data sources or human confirmation, both of which create single points of failure, fraud potential, and transparency gaps. If an AI books a service or executes a high-value transaction based on inaccurate data, who is accountable? Trinetra was conceived to address this question — to enable AI decisions anchored in verifiable real-world truth, authenticated without human input. Our driving principle became: “Did the AI’s action truly reflect the real world — and can we prove it?” The Foundations: What We Learned Building Trinetra meant bringing together three distinct technological pillars: 1. AI / Multi-Agent Systems We discovered that reliable automation requires a decentralized, multi-agent AI architecture rather than a single monolithic model. Trinetra employs multiple intelligent agents such as: Context Analyzer: Decomposes user intent into verifiable sub-tasks. Execution Bot: Executes validated actions once proof is logged on-chain. These agents communicate asynchronously, ensuring scalability and fault-tolerant decision-making. 2. Sui Blockchain for Verifiability The Sui blockchain became our backbone for trustless, immutable audit trails. Rather than merely executing transactions, Sui provides an object-based ledger for recording the rationale behind every AI action — ensuring accountability and transparency. Logged data includes: User intent hash CV analysis result (e.g., "Dry: True") Cryptographic hash of the proof snapshot Execution request metadata Through Sui smart contracts written in Move, every AI decision gains a verifiable provenance that cannot be altered or disputed. 3. Real-World Data Interfacing (The Oracle Problem) One of the hardest challenges was building a tamper-proof interface between the physical world and AI systems — what we termed the “CCTV Oracle Problem.” To solve this, we engineered a Data Ingestion Gateway that: Validates incoming CCTV/IoT feeds, Performs integrity checks, Runs real-time CV analysis, and Hashes results before writing them to the Sui blockchain. This ensures that any data driving an AI decision is verifiable and immutable. The Blueprint: How We Built Trinetra Trinetra’s architecture is layered for security, accountability, and autonomy. 1. User Interface & Intent Layer Action: User issues a natural-language command, e.g., “Book an Uber if the nearest tennis court is dry.” Component: Front-end app or chat interface. Output: Structured intent passed to the AI Core. 2. Cognitive & Data Verification Layer (AI Core) 🧠 AI Context Analyzer (The Brain) Breaks down the command into verifiable actions: 🧩 Data Ingestion Gateway Acquires real-time video stream. Runs Computer Vision (CV) model (YOLO/ResNet). Classifies scene (e.g., dry or wet). Generates cryptographic hashes of both image frame and classification result. Submits proof hash to Sui blockchain for verification. 3. Trust & Security Layer (Sui Blockchain) 🔐 Smart Contract Rationale Logging When the CV model confirms a condition, the Execution Bot initiates a Sui transaction. On-chain, the Sui Move contract records: UserCommand_Hash CV_Result Snapshot_Hash Execution_Request Each record becomes a verifiable on-chain object, creating an immutable trail of the AI’s decision logic. 4. Execution & Feedback Layer 🤖 Execution Bot (The Hand) Once the rationale is confirmed on-chain, this agent executes the external API call (e.g., Uber API). ✅ Settlement: The final booking transaction ID is stored on Sui, closing the verifiable transaction loop. The user receives real-time confirmation through the app. The Gauntlet: Challenges Faced Live Oracle Verification: Ensuring that live video data hasn’t been tampered with required a cryptographic chain-of-trust validated through Proof-of-Authority (PoA) consensus nodes on Sui. Live Oracle Verification: Ensuring that live video data hasn’t been tampered with required a cryptographic chain-of-trust validated through Proof-of-Authority (PoA) consensus nodes on Sui. Computational Efficiency: Running multiple CV analyses in real-time was resource-intensive. We implemented edge-optimized models and tiered data processing to scale efficiently. Computational Efficiency: Running multiple CV analyses in real-time was resource-intensive. We implemented edge-optimized models and tiered data processing to scale efficiently. Privacy Compliance: No personal or raw visual data is ever stored on-chain. Only SHA-256 hashes of snapshots are recorded, ensuring privacy and regulatory compliance. Privacy Compliance: No personal or raw visual data is ever stored on-chain. Only SHA-256 hashes of snapshots are recorded, ensuring privacy and regulatory compliance. Conclusion Project Trinetra is not just a technological prototype — it’s an Accountability Framework for the age of autonomous AI. By combining: The adaptive intelligence of multi-agent AI systems, The object-oriented verifiability of the Sui blockchain, and The authenticity of real-world oracles, Trinetra lays the groundwork for transparent, trustworthy, and self-verifying AI ecosystems. 🏗️ Architectural Foundations (Powered by Sui) A. Core Components and Technologies B. Design Principles 1. Decoupling Separate the concerns of Intent (AI), Proof (Gateway), and Trust (Sui Blockchain) — ensuring that one layer’s failure does not compromise another. Future updates will use ZKPs to verify conclusions (e.g., “court is dry”) without revealing any underlying image data, maximizing privacy and trust. 4. Consortium/Federated Design Trusted data providers (CCTV networks, IoT systems) will participate in a Proof-of-Authority (PoA) or Delegated Proof-of-Stake (DPoS) model on Sui, guaranteeing data validity and reducing oracle manipulation risks. ✨ Final Thought Project Trinetra represents a fusion of cognition and verifiability — where AI thinks, Sui verifies, and the world trusts. Would you like me to add diagrams (Mermaid/PlantUML) next — e.g., a flowchart of the architecture or agent interaction with the Sui blockchain?
💡 Project Trinetra: The Autonomous Verification System
The Spark: Inspiration & Problem
The core inspiration for Project Trinetra emerged from what we call the “Trust Gap” in autonomous decision-making.
While AI is exceptional at reasoning and executing complex actions, and blockchain provides a foundation for immutable trust, there exists a crucial disconnection:
How can an AI-driven financial transaction be verifiably tied to an authentic, untampered, real-world condition?
Most existing systems rely on centralized data sources or human confirmation, both of which create single points of failure, fraud potential, and transparency gaps.
If an AI books a service or executes a high-value transaction based on inaccurate data, who is accountable?
Trinetra was conceived to address this question — to enable AI decisions anchored in verifiable real-world truth, authenticated without human input.
Our driving principle became:
“Did the AI’s action truly reflect the real world — and can we prove it?”
The Foundations: What We Learned
Building Trinetra meant bringing together three distinct technological pillars:
1. AI / Multi-Agent Systems
We discovered that reliable automation requires a decentralized, multi-agent AI architecture rather than a single monolithic model.
Trinetra employs multiple intelligent agents such as:
- Context Analyzer: Decomposes user intent into verifiable sub-tasks.
- Execution Bot: Executes validated actions once proof is logged on-chain.
These agents communicate asynchronously, ensuring scalability and fault-tolerant decision-making.
2. Sui Blockchain for Verifiability
The Sui blockchain became our backbone for trustless, immutable audit trails. Rather than merely executing transactions, Sui provides an object-based ledger for recording the rationale behind every AI action — ensuring accountability and transparency.
Logged data includes:
- User intent hash
- CV analysis result (e.g.,
"Dry: True") - Cryptographic hash of the proof snapshot
- Execution request metadata
Through Sui smart contracts written in Move, every AI decision gains a verifiable provenance that cannot be altered or disputed.
3. Real-World Data Interfacing (The Oracle Problem)
One of the hardest challenges was building a tamper-proof interface between the physical world and AI systems — what we termed the “CCTV Oracle Problem.”
To solve this, we engineered a Data Ingestion Gateway that:
- Validates incoming CCTV/IoT feeds,
- Performs integrity checks,
- Runs real-time CV analysis, and
- Hashes results before writing them to the Sui blockchain.
This ensures that any data driving an AI decision is verifiable and immutable.
The Blueprint: How We Built Trinetra
Trinetra’s architecture is layered for security, accountability, and autonomy.
1. User Interface & Intent Layer
-
Action: User issues a natural-language command, e.g.,
“Book an Uber if the nearest tennis court is dry.”
-
Component: Front-end app or chat interface.
-
Output: Structured intent passed to the AI Core.
2. Cognitive & Data Verification Layer (AI Core)
🧠 AI Context Analyzer (The Brain)
Breaks down the command into verifiable actions:
Find nearest tennis court → Locate CCTV → Analyze dryness
🧩 Data Ingestion Gateway
- Acquires real-time video stream.
- Runs Computer Vision (CV) model (YOLO/ResNet).
- Classifies scene (e.g.,
dryorwet). - Generates cryptographic hashes of both image frame and classification result.
- Submits proof hash to Sui blockchain for verification.
3. Trust & Security Layer (Sui Blockchain)
🔐 Smart Contract Rationale Logging
When the CV model confirms a condition, the Execution Bot initiates a Sui transaction.
On-chain, the Sui Move contract records:
UserCommand_HashCV_ResultSnapshot_HashExecution_Request
Each record becomes a verifiable on-chain object, creating an immutable trail of the AI’s decision logic.
4. Execution & Feedback Layer
🤖 Execution Bot (The Hand)
Once the rationale is confirmed on-chain, this agent executes the external API call (e.g., Uber API).
✅ Settlement:
The final booking transaction ID is stored on Sui, closing the verifiable transaction loop. The user receives real-time confirmation through the app.
The Gauntlet: Challenges Faced
-
Live Oracle Verification: Ensuring that live video data hasn’t been tampered with required a cryptographic chain-of-trust validated through Proof-of-Authority (PoA) consensus nodes on Sui.
-
Computational Efficiency: Running multiple CV analyses in real-time was resource-intensive. We implemented edge-optimized models and tiered data processing to scale efficiently.
-
Privacy Compliance: No personal or raw visual data is ever stored on-chain. Only SHA-256 hashes of snapshots are recorded, ensuring privacy and regulatory compliance.
Conclusion
Project Trinetra is not just a technological prototype — it’s an Accountability Framework for the age of autonomous AI.
By combining:
- The adaptive intelligence of multi-agent AI systems,
- The object-oriented verifiability of the Sui blockchain, and
- The authenticity of real-world oracles,
Trinetra lays the groundwork for transparent, trustworthy, and self-verifying AI ecosystems.
🏗️ Architectural Foundations (Powered by Sui)
A. Core Components and Technologies
| Component | Function / Role | Technology Stack |
|---|---|---|
| Sui Blockchain Layer | Immutable audit logs and secure settlements for AI actions. | Sui Move smart contracts, PoA/DPoS consensus, object-based proof storage. |
| AI / ML Layer | Natural-language intent parsing, CV analysis, and execution logic. | Python (PyTorch / TensorFlow), LangChain, uAgent. |
| Data Ingestion Gateway | Real-world data validation, hashing, and verification. | Rust / Go, IPFS / Arweave, SHA-256 hashing for proofs. |
| API Gateway / Execution Layer | Handles third-party APIs and notifications. | REST / GraphQL, Kafka / RabbitMQ. |
B. Design Principles
1. Decoupling
Separate the concerns of Intent (AI), Proof (Gateway), and Trust (Sui Blockchain) — ensuring that one layer’s failure does not compromise another.
Future updates will use ZKPs to verify conclusions (e.g., “court is dry”) without revealing any underlying image data, maximizing privacy and trust.
4. Consortium/Federated Design
Trusted data providers (CCTV networks, IoT systems) will participate in a Proof-of-Authority (PoA) or Delegated Proof-of-Stake (DPoS) model on Sui, guaranteeing data validity and reducing oracle manipulation risks.
✨ Final Thought
Project Trinetra represents a fusion of cognition and verifiability — where AI thinks, Sui verifies, and the world trusts.
Would you like me to add diagrams (Mermaid/PlantUML) next — e.g., a flowchart of the architecture or agent interaction with the Sui blockchain?
Analysis
View
Metric
- 1
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- ExpressIn code
- FlaskIn code
- HTMLIn code
- JavaScriptIn code
- Next.jsIn code
- PythonIn code
- ReactIn code
- SolidityIn code
- SupabaseIn code
- Tailwind CSSIn code
- TypeScriptIn code
12 of 12 appear in the indexed code.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
984 KB
Source files
193
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
Shanthan2307/Trinetra_1
273 files · 9.7 MB · @ 35e4374
Structure
Interface
84 files · 31%Screens, components and styles rendered to the user.
Application logic
73 files · 27%Domain rules, services and shared utilities.
+9 more
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- Markdown37%
- TypeScript25%
- Python16%
- JavaScript15%
- HTML4%
- CSS2%
- Other (3)1%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
frontend_landing/src/package.json
npm · 74- @eslint/eslintrc
- @hookform/resolvers
- @radix-ui/react-accordion
- @radix-ui/react-alert-dialog
- @radix-ui/react-aspect-ratio
- @radix-ui/react-avatar
- @radix-ui/react-checkbox
- @radix-ui/react-collapsible
- @radix-ui/react-context-menu
- @radix-ui/react-dialog
- @radix-ui/react-dropdown-menu
- @radix-ui/react-hover-card
- @radix-ui/react-label
- @radix-ui/react-menubar
- @radix-ui/react-navigation-menu
- @radix-ui/react-popover
- @radix-ui/react-progress
- @radix-ui/react-radio-group
- +56 more
frontend/package.json
npm · 40- @dynamic-labs/ethereum
- @dynamic-labs/sdk-react-core
- @dynamic-labs/wagmi-connector
- @ipld/dag-pb
- @mysten/dapp-kit
- @mysten/sui.js
- @story-protocol/core-sdk
- @tanstack/react-query
- @testing-library/dom
- @testing-library/jest-dom
- @testing-library/react
- @testing-library/user-event
- dotenv
- ethers
- framer-motion
- fs
- hls.js
- multiformats
- +22 more
frontend_landing/package.json
npm · 30- @radix-ui/react-dialog
- @react-three/drei
- @react-three/fiber
- @types/three
- class-variance-authority
- clsx
- leva
- lucide-react
- ogl
- react
- react-dom
- tailwind-merge
- tailwindcss-animate
- three
- +16 more
backend/requirements.txt
pypi · 13- beautifulsoup4
- face-recognition
- Flask
- flask-cors
- flask-socketio
- google-generativeai
- lxml
- opencv-python
- Pillow
- python-dotenv
- python-socketio
- requests
- supabase
avs-2/Execution_Service/package.json
npm · 10- @pinata/sdk
- @types/axios
- axios
- cors
- dotenv
- ethers
- express
- express-session
- fs
- nodemon
avs-2/Validation_Service/package.json
npm · 8- @types/axios
- axios
- cors
- dotenv
- express
- express-session
- fs
- nodemon
backend/CCTV/requirements.txt
pypi · 3- beautifulsoup4
- opencv-python
- requests
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.