EthGlobal Open Agents May 2026

Disaster Response
Allocator

Autonomous agents monitor real disasters, verify ground-truth
with location proofs, and allocate emergency funds onchain.

0G Chain + Compute + Storage Gensyn AXL Mesh ENS Identity Astral Proofs
Patrick Rawson
Ecofrontiers · responsesurface.vercel.app

The Problem

  • Emergency procurement is slow. Weeks to allocate, months to verify.
  • Ground truth is missing. Who's actually in the burn zone? No one checks.
  • Bad actors exploit opacity. Inflated claims, phantom zones, no accountability.
  • No reputation memory. Each disaster starts from zero trust.
$417B
Global disaster losses in 2024
Source: Gallagher Re, 2025
63% of losses uninsured. Fund distribution
still measured in audit cycles, not seconds.

How It Works

Every allocation cycle runs a 7-phase pipeline. Real government data in, verified fund distribution out.

1Collect
NASA, USGS, EPA
2Relay
AXL mesh
3Gate
ENS identity
4Score
0G Compute TEE
5Allocate
0G Chain
6Audit
0G Storage
7Update
ENS records

8 Regional Agents

Each monitors a US region using 5+ government APIs. Real wildfire, flood, storm, and earthquake data.

1 Coordinator

Aggregates assessments, runs credibility scoring, executes allocation onchain via ResponseFund contract.

2 Adversarial Agents

Rogue + Phantom. Inflated severity, no field presence. Exist to prove the proof gate actually works.

Tech Stack

0G (Chain + Compute + Storage)

Chain: ResponseFund contract holds fUSD, executes weighted allocations per cycle.

Compute: TEE sealed inference produces verifiable allocation plans no agent can manipulate.

Storage: Merkle-root audit log of every cycle committed to 0G Storage. Fully auditable.

Gensyn AXL

11 AXL nodes, each with unique Ed25519 keys. Agents relay disaster assessments through an encrypted P2P mesh. Cryptographic identity feeds directly into credibility scoring.

ENS (Sepolia)

Identity: ENSIP-25 gasless subnames under responsesurface.eth. Agents must have ENS to participate.

Reputation: credibility.score + credibility.proofs written as text records after each cycle. Reputation persists across rounds.

Astral Protocol (Base Sepolia)

Location proof verification via spatial containment. "Is this geotagged photo actually inside the reported burn zone?" Ground truth, not self-reported claims.

The Proof Gate

Two adversarial agents try to steal funds every cycle. They fail.

weight = credibility × severity × disasterDensity × proofMultiplier

proofMultiplier = proofs == 0 ? 0 : min(0.15 + verifiedProofs × 0.28, 1.0)
// 0 proofs = 0 weight = 0 allocation. Hard zero, no exceptions.

rogue.responsesurface.eth

Reports severity 10 for disasters it's nowhere near. No geotagged photos, no field presence. The proof gate catches it: 0.00 fUSD allocated.

phantom.responsesurface.eth

Claims to monitor a real region but submits fabricated data. Astral containment check fails: coordinates don't match any burn zone. 0.00 fUSD allocated.

You can't submit a geotagged photo from inside a burn zone if you're not there.
Now showing

Live Demo

responsesurface.vercel.app

11
agents
6
gov't APIs
7
pipeline phases
Dashboard → Run Cycle → Feed → Proof Panel → AXL Mesh → ENS Registry

What if disaster response
ran on a response surface?

A dynamic allocation surface where every agent, every proof, and every fund movement is verifiable, adversarial-resistant, and permanent.

0G Autonomous Agents Gensyn AXL ENS Best AI Agent ENS Most Creative
Repo
github.com/Ecofrontiers/response-surface
Live
responsesurface.vercel.app
ENS
responsesurface.eth (Sepolia)