Mvua Protocol
Parametric climate insurance for the people who feed us.
When the weather data says the season failed, the payout is already on its way.
The problem
A failed season does not wait for paperwork.
When rain does not come, a smallholder farmer can lose a whole year of income in a few weeks. Traditional crop insurance was never built for them: premiums are out of reach, adjusters must reach fields that may be hours from a road and a claim can take months to settle. By the time a payout arrives, the planting window is gone.
Index insurance removes the whole apparatus. Instead of inspecting a field after the fact, it pays on a number that anyone can check: the rainfall record for that place and that season. The farmer and the fund both know the rule before the season starts.
Premiums exclude the poor
Assessing each small field individually costs more than the field is worth to insure. The economics never close.
Adjusters cannot get there
Rural roads, dispersed plots, no records. Verification is slow, expensive and easy to dispute.
Payouts arrive too late
Months of delay turns relief into history. The money lands after the next season has already been decided.
What Mvua is
Micro insurance that settles itself
A farmer buys a small policy in USDC at the start of a season. The protocol watches an on chain rainfall index for that region. If the season fails by the rule written into the policy, the payout vault releases automatically, with no claim to file and no one to convince.
Buy cover
A farmer picks a region and a season and pays a premium in USDC into a risk pool. The policy records the rainfall index, the payout trigger and the payout amount before the season begins.
Watch the season
For the length of the season, the oracle adapter collects signed rainfall readings from independent publishers. Anyone can read the same numbers; there is nothing to dispute about the weather.
Get paid automatically
At the end of the season the trigger engine reads the index. If it crossed the trigger, the payout vault releases funds to every affected policy. No claim, no adjuster, no wait.
Architecture
Five contracts, one job each
The on chain core is split so that a failure in one part cannot quietly corrupt another. Funds, policy terms, data intake, the index decision and payout are separate.
risk-poolHolds the capitalpolicyRecords the termsoracle-adapterBrings in the weathertrigger-engineDecides the seasonpayout-vaultReleases the moneyWhy it holds
Rules you can read, not promises you have to trust
Every decision the protocol makes is a function of public inputs: the signed rainfall readings, the index definition and the policy terms. The same inputs produce the same outcome for everyone.
The oracle is deliberately boring. Readings come from more than one publisher, the adapter takes the median rather than any single submission; a challenge window gives honest parties time to object before a bad reading settles.
Funds are never held by the app
The interface reads state and submits transactions. Capital lives in the on chain pool and vault, under the rules the contracts enforce.
Terms are fixed before the season
The trigger and payout are written at purchase. Nobody can move the goalposts after the weather is known.
The on chain core has settled its first full season on Stellar testnet.
A farmer bought cover, the drought index triggered and the payout was released and claimed on chain, matching the golden vector. Mainnet is gated behind an external audit and a full beta season operated like production.
Where the code lives
Split on purpose
mvua-contractThe on chain core
Risk pools, policies, the oracle adapter, the trigger engine and the payout vault. Rust, on Soroban. This is where funds are held and payouts are decided.
Mvua Protocolmvua-appThe interface
Pool dashboards, policy purchase and a payout explorer. Built with Next.js. It reads state and submits transactions and never holds funds.
Mvua Appmvua-publisherThe oracle feed
Turns public rainfall archives into signed observations the oracle verifies on chain. One independent publisher in the quorum, built with Node and TypeScript. It holds no funds. Its signing keys never leave the operator.
Mvua PublisherWhy Stellar
Built on rails made for small money
Mvua pays small amounts to people the traditional system priced out, so the rails underneath have to be cheap, fast and reachable without a bank. Stellar was built for exactly that.
Fees a farmer can ignore
A premium can be a few dollars and a payout smaller still. Stellar settles in about five seconds for a tiny fraction of a cent, so the network cost never eats the cover.
Stablecoin, not speculation
The protocol works in USDC on Stellar. Premiums, reserves and payouts are denominated in a currency that does not swing, so a policy is worth what it says.
No wallet gymnastics to get paid
A Stellar Asset Contract transfer reaches a farmer without XLM, a trustline or a signature from them. The people the protocol serves should not have to learn gas to receive money they are owed.
Contracts you can check
Soroban runs the five contracts with integer only maths and deterministic execution, so the same inputs always produce the same payout. Nothing about the decision is hidden.