Bind the SLA
Provider, beneficiary and billing executor commit the coverage window, magnitude threshold and geographic bounding box.
QuakeSLAVerifiable service creditsTurn reviewed USGS earthquake evidence into a deterministic, one-time service-credit authorization, validated independently by GenLayer's consensus network.
Evidence authority
USGS GeoJSONNetwork
Studio Next · 61997Policies on-chain
LoadingExecution model
Explicit consumeThe contract never trusts a user-supplied verdict. Each validator independently fetches the same bounded USGS endpoint and recomputes the policy match.
Provider, beneficiary and billing executor commit the coverage window, magnitude threshold and geographic bounding box.
A party submits only a USGS event ID. Validators construct the fixed government endpoint; arbitrary URLs are rejected by design.
Reviewed status, timestamp, coordinates and magnitude are normalized into an exact canonical receipt under strict equivalence.
Validators fetch the event again after six hours. Material USGS corrections remain visible and can revoke eligibility before execution.
Only the bound execution authority can consume a twice-verified authorization, preventing replay and separating judgment from payment.
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.
What gets verified, who can act, and what an on-chain authorization actually means.
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.
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.
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.
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.
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.