Picture this

Who it is for

A rooftop concert in Lagos sells tickets with Rain Refund. If agreed weather sites report heavy rain, holders are refunded half.

Two ways to own it

What you get

Base$159

$40 deposit to reserve

Ticket sale, refund rule, weather reader, refund payout.

You choose: refund share
You choose: accent color

Customfrom $1,200

Built around you

Reshape it entirely: new features, your flows, your brand end to end, integrations you need. We scope it with you.

Everything in Base
Custom features and design
Priority build

Why it is new

What exists today, and what this does differently

What is new

Parametric weather cover exists (Etherisc); event ticket refunds judged from web weather by LLM consensus were not found.

Closest things out there

Etherisc parametric cover.

Checked with web searches in October 2026. A search is not proof that nothing similar exists, and the market moves fast, so we recheck before every build.

What it unlocks

The human in it

Buy the ticket, not the risk.

The Regatta Board

Races it can enter

grant · GenLayer · rolling

GenLayer builder program

unknown

Official page ↗

Ecosystem program for shipped apps; check current terms.

Their rule on existing code: unknown

What you own

The whole app, not a starter kit.

The complete Rain Refund app: outdoor event tickets carry a rain rule that is locked with a reserve before the first sale, and validators read observed weather after the show to refund holders automatically.

Base price · $159

The user app, complete

Every buyer gets the same finished app. Basic branding and copy changes come through a quick form.

Three step onboardingHome

Shown once: write a rain rule, lock the reserve, validators read the weather.

Show status and next actionHome

Reserve, tickets sold, the rule, and one clear next step.

Weekly forecast digestHome

Rain odds for each show this week. Gated behind Season.

Rain rule editorRule

Threshold in mm, refund share, ticket price, ticket count, show window and observed weather sites.

Reserve lockRule

Enough to pay every refund is locked before sales; the rule is final after that.

Ticket sale with checkoutTickets

Fans buy through the USDC checkout with the rule printed on the ticket; sales stop at the reserve cap.

Branded pages and back to back showsTickets

Gated behind Season.

Post show verdictVerdict

Clear night, downpour and disagreeing sites; median of observed readings against the rule.

Batch refunds and receiptsVerdict

Every reading, refunded total, reserve returned and the verdict transaction.

Refund credit and share cardVerdict

Fans can use their refund toward the next show and share the moment.

Plans and settingsMe

Single show fee, Season through the USDC checkout, or a venue network request.

Open the full app demo

Add-on

Owner console

Your admin side: revenue, paywall editor, users, rules and the agent log.

Revenue and paywall editorRevenue

Ticket fees, Season plans, USDC payments, payment methods, live fee and price editing, gates.

RulesRules

Validators per verdict, readable sites needed, max refund share, reruns when sites are down.

Validator log and roadmapAgent

What failed and the fix, running costs, and priced v2 and v3 builds.

Top-up

Growth and referrals

Referral and growth mechanics, switched on when you are ready to grow.

Growth loopsGrowth

Rainy season pitches, refund moments, competitor pull, refund credit and promoter referrals.

The money path, built in

How it earns for you

Promoters pay a small share of ticket sales per show, or a monthly Season plan for every show at one venue. Networks of venues are quoted.

Single show1.5% of ticket salesRain rule, reserve lock, verdict and refunds for one event

Season$79 a monthUnlimited shows for one venue, weekly forecast digest, branded ticket pages

Venue networkCustomSeveral venues or festivals, custom site lists and areas, exports for accounting

Ticket fee set by the owner (default 1.5 percent). A verdict costs cents to under a dollar; refunds are batched.

Prices are yours to set. Illustrative, not a promise of income.

Growth loops, built in

How it spreads

Every refund is a moment fans share, showing the rule and the venue
Promoters see rivals fill rooftops in rainy season and ask for the same rule
Refund credit brings fans back for the next ticket
Promoter referrals worth a free Season month

Roadmap · build the next phase with us

Where it goes next

v1 included

The full promoter app

Rain rule editor and reserve lock
Ticket sale with embedded wallets
Post show verdict from three sites
Batch refunds and reserve return
Plans and checkout

Included

Heat, wind and power cuts

Heat and wind rules
Power cut rule from grid status pages
Hourly refund curves
Forecast planner

Add-on from $500

Festival network

Many venues, one dashboard
Refund credit wallet for fans
Ticketing integrations
Accounting exports

Add-on from $1,200

For investors and grant reviewers

The pitch, ready

Outdoor event tickets that refund automatically if it rained, judged from observed weather reports.

Problem: In rainy season fans hesitate to buy outdoor tickets, and promoters lose sales or face angry refund requests with no fair rule.

Solution: A rain rule and a reserve are locked before sales; after the show, validators read observed rain from agreed sites, must agree, and refunds are paid in a batch.

Why now: Intelligent contracts can read web pages with consensus, and stablecoin tickets with embedded wallets make automatic refunds practical.

Market: Outdoor promoters, rooftop venues and festivals in rainy climates.

The ask: Pilot with three Lagos rooftop venues through one rainy season.

Funding is never guaranteed. Check each program's rules.

For hackathons and demo days

Your 2 minute demo

Home: meet Kemi, who runs rooftop concerts in Victoria Island.
Rule: set 15 mm and 50 percent back, then lock the $4,000 reserve.
Tickets: buy a ticket as Chidi through the USDC checkout and see the rule on the stub.
Verdict: play the downpour and watch refunds pay; then a clear night that returns the reserve.
Verdict: try the night when sites disagree and see the median decide.
Owner Agent: read how a daily total and a forecast page were rejected.
Owner Revenue: change the ticket fee and Season price, and preview the Plans sheet.
Owner Growth and Roadmap: run a rainy season pitch, then request heat and power cut rules.

Many hackathons require code written at the event. See the Regatta Boardfor each race's rule.

Make it entirely yours

Custom work from $1,200: your weather sources and areas, a ticketing integration, a festival branded deployment, or accounting exports. Scoped on a call.

Custom from $1,200

BLUEPRINT

Why it matters and how it really works

The need

Outdoor events in rainy seasons lose sales because fans wait to see the weather, and when it pours, refunds are slow, discretionary and argued over by email. Promoters have no simple way to make a credible, automatic rain promise.

What exists and what is new

Parametric weather cover exists: Etherisc has run weather-triggered parametric products onchain, and event cancellation insurance exists off chain. Those are insurance products priced by an underwriter. What is new here is narrower: a promoter-funded refund rule printed on the ticket, judged after the show by GenLayer validators reading agreed public weather sites with LLM consensus, with no claim step. Research found no event ticket refund judged this way. It is a promise backed by the promoter's own locked reserve, not insurance.

The data it runs on

The rain rule (refund share, millimetre threshold, show window, area, quorum), the list of agreed weather sites, ticket ownership, the locked reserve, and after the show the readings each validator extracted from those sites plus the final verdict. Holder names and contact details stay off chain.

1.The mission

Let anyone running an outdoor event sell tickets with a rain promise fans can read before they pay and trust after it pours.

2.Why people can't resist it

Buy early without the gamble The rule is on the ticket. Fans stop waiting for the forecast and buy when they decide to go.

Refund before the bus home No form or email. If the sites agree it poured, money lands minutes after the show.

Readings anyone can check Every verdict shows what each site reported, so a no-refund night is explainable, not suspicious.

3.How it works for real

Rule and reserve: The promoter writes the rule and locks share x price x tickets in USDC in a GenLayer intelligent contract before sales open.

Tickets: Tickets are sold in the app with an embedded wallet for each fan; each ticket records which rule it carries.

After the show: At the end of the window the contract asks validators to read the agreed sites. Each one uses web access plus an LLM to extract observed rainfall for the window and area, rejecting forecasts and daily totals.

Consensus: GenLayer's Optimistic Democracy compares validator results under an equivalence principle; disagreement triggers an appeal round with more validators.

Payout or return: If the quorum of sites is over the threshold, refunds go to every ticket holder. If not, the reserve returns to the promoter. If too few sites are readable, the check reruns at set times.

4.Cost per use and pricing

Per show: one verdict call with five validators each reading three pages is a handful of LLM calls, roughly a few cents to under a dollar depending on models and GenLayer fees at the time. Refund transfers for 400 holders can be batched. Hosting and ticket pages about $20 to $40 a month. The real cost is the refund itself: at $20 tickets and 50%, a rainy night with 400 holders returns $4,000 of the promoter's reserve.

Single show 1.5% of ticket sales

Rain rule, reserve lock, verdict and refunds for one event.

Season $79 a month

Unlimited shows for one venue, weekly forecast digest, branded ticket pages.

Venue network Custom

Several venues or festivals, custom site lists and areas, exports for accounting.

5.Growth loop

Every refund is a moment fans share, and every share shows the rule and the venue. Promoters see competitors fill rooftops in rainy season and ask for the same rule. Fans who got a refund return to buy the next ticket with the credit.

6.Risks and guardrails

Bad or changed weather pages: Use several agreed sites, a quorum, and accept only observed readings timestamped after the window. Publish every reading.

Validators disagree: Appeals add validators. If still unresolved, the rule's fallback applies, set before sales.

Mistaken for insurance: Copy says plainly it is a promoter-funded refund promise, not insurance. Local consumer and insurance rules should be checked before launch in each country.

Reserve too small: Sales stop at the number of tickets the reserve covers.

7.Build order

Rule editor and reserve lock contract on GenLayer testnet
Ticket sale with embedded wallets
Post-show verdict reading three sites with quorum
Batch refunds and reserve return
Public verdict page with every reading
Weekly forecast digest for promoters

8.Where this is going

Now
One rooftop in Lagos with a rain rule on every ticket.
Next
Other conditions in the same shape: heat, wind, air quality, a flight that did not land.
Later
Shared reserves across venues so small promoters can offer the promise too.
The world it builds
Promises about the real world that settle themselves, read from public sources anyone can check.

Costs and tools are estimates at the time of writing. General information only, not legal or financial advice.

OWNER PLAYBOOK

Own it, then chart your voyage

Nine routes from one vessel. Tap a port to open its chart.

Why own Rain Refund

Rain Refund: Outdoor event tickets that refund automatically if it rained on the day, judged from weather reports. Using someone else's version means their rules, their brand and their revenue. Owning Rain Refund means it is deployed under your wallet, carries your name, and every customer, partner and result builds your track record instead of theirs.