Mvua Protocol
A software project by Emmanuel Itighise (Emeditweb)

Project overview
Parametric weather insurance for smallholder farmers on Stellar. Five Soroban contracts manage pooled capital, seasonal policies, signed rainfall observations, deterministic triggers, and payouts. A full season has settled on testnet, while 34 years of rainfall backtests guide regional index design and pricing. Pre-alpha; testnet only.
Insurance that pays on the weather
Traditional crop insurance can cost too much to assess for a small farm. Mvua Protocol explores a different approach: a farmer or cooperative buys seasonal cover, and an agreed rainfall index determines the payout without a farm inspection. Mvua means rain in Swahili.
Five contracts and signed rainfall
The Rust and Soroban core separates capital reserves, policy issuance, weather observations, index evaluation, and payouts into five contracts. The risk pool enforces solvency constraints, while the oracle adapter verifies publisher signatures and aggregates a median.
A Node.js and TypeScript publisher compares two independent rainfall sources and refuses to submit when they disagree. The trigger engine applies the index rules, followed by a 24 hour challenge window. The payout vault records claim balances that anyone can push to the farmer’s address, without requiring the farmer to sign or hold tokens for the transfer.
The Next.js application is the interface for reading state and submitting transactions; the contracts hold the funds and decide outcomes. A separate public site documents the architecture, methodology, and deployed contracts.
A season settled on testnet
The first complete season ran against real wall clock time on Stellar testnet. With rainfall at 65% of the expected amount, one test token of cover produced a severity of 28.57% and a payout of 0.2857 test tokens. The result matched the test suite’s prediction, and the deployment documentation links the public transactions.
The live run exposed a contract type alias that the Stellar CLI could not resolve. The affected contracts were redeployed without moving the pool’s money, and a CI check was added to catch the same class of failure.
Pricing from 34 years of weather
Daily rainfall from 1991 to 2024 was replayed through the actual trigger engine for Nakuru, Kano, Dodoma, and Mbeya. The default index would have paid in one of 34 Kano seasons and 12 of 34 Nakuru seasons. The provisional 1.1% premium was too low across the candidate regions, showing why each region needs its own index calibration and sustainable pricing.
Vegetation greenness was also explored as a check on rainfall results. Differences between the two measures help identify basis risk: an index can diverge from the loss experienced by an individual farm.
Status and next steps
Mvua is pre-alpha and testnet only. The contracts have not been externally audited; mainnet depends on an audit and a full beta season operated like production.
Next comes region-specific index methodology and premium calibration, followed by the application for investors, farmers, and cooperatives. A simple phone menu in local languages is also planned for farmers without smartphones.
Technologies and tools
- Stellar
- Soroban
- Rust
- TypeScript
- Node.js
- Next.js
Explore the project
Emmanuel Itighise, known online as Emeditweb, is a full-stack and AI-native developer based in Lagos, Nigeria. This entry is part of his project portfolio and open-source work.