QuakeSLAVerifiable service credits
PARAMETRIC SLA JUDGMENT ON GENLAYER

When the ground moves,
settlement shouldn't.

Turn reviewed USGS earthquake evidence into a deterministic, one-time service-credit authorization, validated independently by GenLayer's consensus network.

Authoritative evidence 5-validator consensus One-time execution

Evidence authority

USGS GeoJSON

Network

Studio Next · 61997

Policies on-chain

Loading

Execution model

Explicit consume
HOW IT WORKS

Evidence to authorization, without an oracle.

The contract never trusts a user-supplied verdict. Each validator independently fetches the same bounded USGS endpoint and recomputes the policy match.

01

Bind the SLA

Provider, beneficiary and billing executor commit the coverage window, magnitude threshold and geographic bounding box.

02

Fetch canonical evidence

A party submits only a USGS event ID. Validators construct the fixed government endpoint; arbitrary URLs are rejected by design.

03

Recompute the match

Reviewed status, timestamp, coordinates and magnitude are normalized into an exact canonical receipt under strict equivalence.

04

Revalidate after finality delay

Validators fetch the event again after six hours. Material USGS corrections remain visible and can revoke eligibility before execution.

05

Consume once

Only the bound execution authority can consume a twice-verified authorization, preventing replay and separating judgment from payment.

WHY DECENTRALIZED JUDGMENT?

A source can be public and still need consensus.

USGS supplies facts, not your SLA outcome. QuakeSLA makes every validator independently prove that the same reviewed event satisfies the exact policy window, magnitude and geographic scope before authorization can exist.

No arbitrary evidence URLsEvent IDs are constrained and expanded into a fixed USGS endpoint.
Fail closed under uncertaintyUnavailable, malformed or unreviewed evidence becomes UNRESOLVED, never approval.
Replay-resistant lifecycleRevisions protect stale calls and authorization can be consumed exactly once.
VALIDATOR AGREEMENT3 / 5 quorum
V1AGREE
V2AGREE
V3AGREE
V4IDLE
V5IDLE
FREQUENTLY ASKED QUESTIONS

Know the rules before you act.

What gets verified, who can act, and what an on-chain authorization actually means.

Does QuakeSLA transfer money or credits automatically?

No. The contract determines whether a policy qualifies and records a one-time authorization. A separate, bound execution authority must consume it; actual billing or payment happens outside this contract.

Where does the earthquake evidence come from?

Validators independently fetch the event from the fixed USGS earthquake detail endpoint using its event ID. The caller cannot supply a replacement evidence URL or a verdict.

What happens if USGS data is missing or not reviewed?

The assessment does not grant an authorization. Missing, malformed, or unreviewed evidence is marked unresolved so it can be retried when authoritative data is available.

Who can create, assess, and consume a policy?

A connected wallet creates a policy with its beneficiary and execution authority. The authorized participants can submit an event assessment; only the bound execution authority can consume an approved credit once.

What do I need to try the live console?

Connect a wallet to GenLayer Studio Next (chain ID 61997), hold test GEN for transaction fees, then use the separate console page to create a future coverage policy, assess a reviewed USGS event, and inspect the receipt.

Open live console