WarrantyLock
Project · GenLayer Studionet

WarrantyLock

Escrow the coverage. Register an issuer. AI classifies coverage — the contract decides the money.

How WarrantyLock works

  1. STEP 1

    Registry lists issuers

    An independent registry admin registers issuer wallets per evidence class (manufacturer, repairer, invoice, telemetry, or inspection) plus a credential hash. Sellers cannot write this list.

  2. STEP 2

    Seller escrows coverage

    Create names one buyer, a registered issuer, an evidence class, a serial hash, locked terms, and the exact coverage amount. The issuer cannot be the seller.

  3. STEP 3

    Buyer files a claim

    The buyer files the serial and the exact 0.01 GEN stake. Reason text is narrative only. A public web page cannot release coverage by itself.

  4. STEP 4

    Issuer commits an artifact

    The locked issuer attests this claim with type, serial, amount, and an artifact hash. Validators fetch the HTTPS artifact and require the hash to match. No attest, no payout.

  5. STEP 5

    AI eligibility, contract money

    Anyone may judge after a reply or after the response deadline. COVERED without a valid registered attest becomes INCONCLUSIVE. Timeout returns the stake.

Offer a warranty

You send exactly the coverage amount. The named buyer must accept before the activation deadline. Claim stake later is exactly 0.01 GEN. The issuer must already be registered by the independent registry admin for that evidence class. The issuer cannot be you. A COVERED payout later requires that wallet to attest a specific artifact hash. That authenticates the registered key and the committed bytes, not a manufacturer login or signed invoice.

Loading warranties…