Clause

Cover that pays itself.

Protect your home, your harvest or your trip. If the thing you insured against happens, the money arrives on its own. There is no claim to file and nobody to convince.

TRIGGER M5.5 M7.2, 09:41:04 ATTESTED CLAUSE PAID TO YOU 25,000 no claim was filed settled in block 412,388
No claim form No wallet needed Price before you decide

What would you like to protect?

Nobody decides whether you get paid.

Ordinary insurance pays after a person agrees that it should. This pays when a measurement crosses a number that was written into your policy the day you bought it.

01

You choose the number

A magnitude, a rainfall total, a delay in minutes. It goes into the policy in plain sight.

02

It is registered on chain

As a predicate: a condition the network itself watches. No bot, no keeper, no company.

03

The measurement arrives

Read from the official source and attested by validators, so it is the figure the world sees.

04

You are paid, that block

Settlement runs in the same block the reading lands. You may not have heard about the event yet.

Seismic network publishes max magnitude Edge reading, validator attested BLOCKS, 50 ms APART 412,386 0 evaluated 412,387 0 evaluated 412,388 0 evaluated 412,389 1 evaluated, 1 paid 412,390 0 evaluated Your predicate, armed and dormant not evaluated in any of these blocks, because the key it reads did not move the key moved, so it is evaluated Paid to your account same block, no claim
A predicate costs nothing to hold. Validators re-evaluate only the ones whose inputs changed in that block, which is why a book of ten thousand policies costs the same to watch as one, and why the payout lands in the block the reading arrives rather than whenever someone gets round to it.

A farmer in Konya should not need a seed phrase.

The hard part of using a chain is not holding a key, it is being asked to approve something over and over. This asks once, at purchase. So there are two doors, and the protocol cannot tell them apart.

Sign in with a phone

  • Works like a banking app: your number, then the face or finger your phone already uses
  • A key is made on your device and never leaves it. The word wallet never appears
  • Pay by card. The payout comes back the same way
  • Your number derives the account and is not stored anywhere

Connect a wallet

  • Your address is your identity. Nothing is registered
  • Policies are objects on chain, readable without this site
  • get_workflow_lineage shows exactly why a payment fired
  • Same address, same objects, same protocol as the door on the left
1
signature, at purchase
0
signatures after that, ever
0
claim forms or assessors
0
user records held by this protocol

What it will not do

This pays on a measurement, not on your actual loss. If the ground shakes hard at your house but the nearest station records less, you are not paid. That gap is real, it is called basis risk, and being onchain does not close it. What we do instead is show you the index, the source and the odds before you pay, and let you move the radius until the cover matches the risk you actually have.

If the source publishes nothing at all by the deadline, the policy is unwound and your premium is returned in full. Not a payout, not a lapse. The contract could not be judged, so it does not stand.

What is real here, and what is simulated

Real

  • The pricing mathematics, written out by hand rather than imported, so every number can be traced
  • The hazard models: truncated Gutenberg and Richter with a characteristic fault term, gamma rainfall, lognormal delay
  • The capital standard, the pool accounting and a ledger that replays and reconciles
  • The price you are quoted on the previous page, computed in your browser

Simulated

  • The chain: Rialo shaped, 50 ms blocks, with a world clock running about 40,000 times real time
  • Readings, generated by the hazard models rather than fetched from live APIs
  • Station normals, route statistics and zone seismicity: plausible figures of the right shape, not a hazard assessment
  • The RPC client speaks the published Rialo methods and is what a devnet deployment would use

Someone has to be able to pay.

Behind every policy is a pool of capital and a rule that stops it writing more than it can stand behind. This is that side of the protocol.

412,000
Block
1,284
Policies armed
3,500,000
Capital in the pool
99.5%
Solvency standard

One earthquake does not settle one policy.

It settles every policy inside its radius, in the same block, from a single reading. That is the event the capital model prices. Set one off and watch.

Book, by location block —
Paid in one block
0
no event yet

The same cover, two prices.

Identical limit, identical term, quoted against a book that already holds eight Istanbul policies. The ninth Istanbul policy is not the same risk as the first, and a protocol that prices them alike is the one that runs out of money.

Istanbul, ninth14.27%
Ankara, same book0.18%

Eighty times the price for a risk whose expected loss differs by a factor of fourteen. The rest is concentration.

The rules that bind it

SOLVENCY

Survive the worst half percent

Capital is sized as the average loss across the worst 0.5% of twenty thousand simulated years.

CONCENTRATION

No single event over 35%

A pool can be solvent on average and one earthquake away from nothing.

LOCKED

Capital cannot run

A provider may withdraw only what is not standing behind live policies.

AUDITED

The ledger replays

Every movement is recorded, so the whole book can be rebuilt from entries and checked.

Sign in to buy

Your phone number derives your account and is not stored. There is no password and no seed phrase.