Hackathon submission
Nimbus
parametric drought insurance.
Submitted to Boundless × Trustless Work · May 13–16, 2026 · virtual build + in-person Demo Day at The Block Hive, Nsukka.
Project name
Nimbus
Project category
Core Trustless Work Applications · Microfinance & transparent capital allocation
Project description
Parametric drought insurance for African smallholder farmers. Every farmer is covered by a Trustless Work Single-Release escrow on Stellar. A daily oracle fetches rainfall from Open-Meteo for the farmer's GPS coordinates; if cumulative seasonal rainfall stays below threshold, the oracle signs the approve-milestone and release-funds calls server-side and USDC moves to the farmer's custodial wallet in seconds — no claim form, no adjuster, no paperwork.
Integration path
React + Next.js 14 frontend talking directly to the Trustless Work REST API. Server-side XDR signing via @stellar/stellar-sdk. No SDK wrappers.
Repository
(add your GitHub URL when you push)
Demo video
(add your Loom or YouTube URL)
Live demo
(Vercel deployment URL)
Trust questions
- What trust problem are we solving?Smallholder farmers across the Sahel lose entire seasons to drought with no financial safety net. Traditional insurance is too slow, too expensive, and never reaches the last mile. Climate funds want faster, auditable relief.
- Who are the parties?Receiver: the farmer's custodial Stellar wallet. Approver / Service Provider / Release Signer / Dispute Resolver: the Nimbus platform wallet, controlled by the oracle. Funder: a coverage-pool sponsor (NGO, climate fund, or DeFi protocol).
- What condition unlocks the funds?Cumulative rainfall at the farmer's exact GPS coordinates falling below the contracted threshold (default 50mm/season), as measured by Open-Meteo's historical weather archive. Deterministic, satellite-grade, no API key required.
- Who resolves disputes?The platform wallet holds Dispute Resolver as a last resort, but the parametric design means there is rarely anything to dispute — rainfall either crossed the threshold or it didn't, and the on-chain record is the source of truth.
Trustless Work integration
- Single-Release escrow per policy · one milestone, deployed via
/deployer/single-release. - approve-milestone + release-funds · called server-side by the oracle, XDR signed by the platform wallet, submitted directly to Stellar Soroban.
- Live escrow inspection · every contract links out to viewer.trustlesswork.com so judges can see escrow state at any moment.
- Receiver-locked design · the Receiver role is the only one held by the farmer, guaranteeing funds can only land with the covered farmer regardless of what the platform does.