Skip to content
AEGIS Smart Protocol

AEGIS Smart Protocol

AI Agents Powering Trustless Disaster Relief

Created on 28th December 2025

AEGIS Smart Protocol

AEGIS Smart Protocol

AI Agents Powering Trustless Disaster Relief

The problem AEGIS Smart Protocol solves

The Problem It Solves

Disaster response systems today are slow, opaque, and unreliable.

Damage assessment depends heavily on manual reports, relief funding is delayed by bureaucracy, and there is little transparency in how emergency funds are distributed. In critical situations, this lack of speed and accountability can cost lives, resources, and trust.


How AEGIS Makes It Better

AEGIS automates disaster response end-to-end using AI agents and blockchain technology.

  • AI-powered detection rapidly analyzes satellite or drone imagery to identify disasters within seconds
  • Autonomous verification reduces false reports and misinformation before any action is taken
  • On-chain fund disbursement ensures relief funds are released transparently and only after verification
  • Real-time dashboards present complex AI and blockchain activity in a clear, human-readable format

Why It’s Safer and More Reliable

  • Eliminates manual and delayed decision-making
  • Prevents fund leakage through verifiable blockchain transactions
  • Creates an immutable public audit trail for every relief action
  • Combines AI speed with verification for responsible automation

Who Can Use AEGIS

  • Governments for faster and accountable emergency response
  • NGOs for transparent and efficient aid distribution
  • Donors for verifiable proof of impact
  • Disaster response teams for real-time situational awareness

In One Line

AEGIS transforms disaster response into a fast, verifiable, and trust-minimized system powered by AI agents and secured by blockchain.

image

Challenges we ran into

Challenges I Ran Into

Building AEGIS involved integrating AI, multi-agent systems, blockchain, and frontend visualization—each of which introduced unique challenges. Some of the most impactful hurdles are outlined below.


Blockchain Transaction Failures

The Issue:
Even after successful disaster detection and verification, Ethereum transactions were failing with errors such as underpriced replacement transactions or silent funding failures.

Root Cause:
The funding logic depended on values that were not always set correctly by upstream agents, causing invalid or zero-value transactions.

How I Solved It:
I traced the entire pipeline end-to-end, identified the missing fallback logic, and implemented defensive checks to guarantee safe transaction execution. I also resolved Web3.py version mismatches that affected raw transaction handling.


AI Confidence vs Real-World Accuracy

The Issue:
Initial computer vision detections produced inconsistent confidence scores, making it difficult to determine when an event should trigger funding.

Root Cause:
Different disaster types required different detection strategies and thresholds, which were not initially calibrated.

How I Solved It:
I separated detection pipelines by disaster category (fire, flood, structural damage, casualties) and tuned confidence thresholds individually to balance sensitivity and false positives.


Agent Coordination & State Flow

The Issue:
Synchronizing multiple agents caused race conditions where one agent acted before another completed its task.

Root Cause:
A lack of clear execution boundaries between detection, verification, and execution stages.

How I Solved It:
I introduced a message-queue-based workflow and enforced strict state transitions, ensuring that each agent only acted once the previous stage was fully completed.


Image Processing Pipeline Errors

The Issue:
Image format mismatches (bytes, PIL, OpenCV arrays) caused crashes and inconsistent results during analysis.

Root Cause:
Different libraries required different formats, and error handling was missing during conversions.

How I Solved It:
I standardized the image processing pipeline, added validation checks at each stage, and implemented graceful fallbacks to prevent system-wide failures.


Rapid Frontend Prototyping vs System Complexity

The Issue:
Displaying real-time AI decisions and blockchain transactions without overwhelming users.

Root Cause:
Complex backend processes needed to be simplified for human understanding.

How I Solved It:
I focused on clarity-first UI design—showing only essential states, using real-time status indicators, and progressively revealing technical details when needed.


Tracks Applied (6)

Ethereum Track

AEGIS leverages Ethereum to enable transparent and trust-minimized disaster relief funding. After AI agents detect and v...Read More
ETHIndia

ETHIndia

Build for Axicov

Basic agent prototypes were created and deployed on Axicov to explore autonomous agent execution. These agents were desi...Read More

Axicov

Side Quest

Bolt.now was used to rapidly scaffold the core frontend structure of AEGIS. It enabled quick generation of the base layo...Read More

Bolt.new

All Participants

Beceptor was used during development to mock external API endpoints and simulate agent responses. This allowed rapid tes...Read More

Beeceptor

Winner

AEGIS uses Magic UI to deliver a clean, high-impact user experience for a complex autonomous system. Magic UI components...Read More

Magic UI

AWS

Kiro AI was used as a core development partner throughout AEGIS. It enabled spec-driven development by helping define sy...Read More

AWS

Discussion

Builders also viewed

See more projects on Devfolio