CVIN CONTRACT CLAUSE TEMPLATES (free to use, no attribution required) These clauses are general drafting references only and do not constitute legal advice, nor any warranty or undertaking by this service. Have them reviewed by a licensed attorney under the applicable jurisdiction before signing. CVIN is an equipment identification and history registry; it does not rate, advise on investments, or appraise value. ———————————————————————————————————————————————————————————— [po-01] Equipment Identification (mandatory PO field) · Purchase Order Where: Purchase Order, "Equipment Schedule" table, one row per unit Prior to delivery, Seller shall declare the Compute Asset Verification & Identification Number ("CVIN", format cvin:..
.:) for each unit of the Equipment and enter it in the "CVIN" column of the Equipment Schedule. Buyer may reject any unit for which no CVIN is declared, and such unit shall not count toward acceptance. Seller warrants that each declared CVIN is accurate, corresponds to one and only one physical unit, and has not been declared differently to any third party for the same unit. Why: Turns "which unit is this" from an acceptance dispute into a mandatory PO field. No CVIN, no acceptance — the one enforcement scenario a buyer can establish unilaterally. ———————————————————————————————————————————————————————————— [po-02] Serial evidence and verification authorisation · Purchase Order Where: Purchase Order, "Delivery and Acceptance" clause Seller shall deliver verifiable serial evidence (any one of: supplier invoice, packing list, OEM console export, or RMA ticket) and authorises Buyer or its agent to record the corresponding observation against that CVIN in the public registry. The serial number itself need not be disclosed in clear text — the registry accepts a one-way hash only, and the clear text never leaves Seller systems. Why: Removes the seller's most common objection: identity evidence is required, but the asset inventory is not surrendered. One-way hash; clear text never leaves the seller. ———————————————————————————————————————————————————————————— [lease-01] Leased asset and return verification · Lease / Rental Where: Lease Agreement, "Subject Matter" and "Return" clauses The subject of this Lease is the specific physical unit identified by CVIN {{CVIN}} ({{ASSET_LABEL}}), and not a substitute unit of equivalent specification. Lessor shall keep that CVIN continuously observable throughout the term (30 consecutive days without observation shall be deemed loss of contact, and Lessee may deduct rent pro rata per day). On return, both parties shall rely on the registry history of that CVIN as the common basis for equipment condition and time on rent. Why: Closes off "equivalent substitute" — the lease is for this unit, not this class. Loss of contact becomes a quantified rent-deduction trigger. ———————————————————————————————————————————————————————————— [lien-01] Identification of collateral and prohibition of double pledge · Security / Collateral Where: Security Agreement, "Description of Collateral" and "Representations and Warranties" The Collateral is identified by Compute Asset Verification & Identification Number ("CVIN"), as listed in Schedule 1. Pledgor represents and warrants that no other valid security interest is registered against any CVIN listed herein under this Agreement; where the registry shows two or more distinct secured parties for the same CVIN, a double pledge shall be deemed to have occurred and shall constitute an Event of Default, entitling the Pledgee to accelerate the obligations. Pledgor shall register the security interest in the registry, and completion of such registration is a condition precedent to drawdown. Why: The whole clause turns on one sentence: two secured parties on the registry equals default. Double pledge moves from a diligence finding to an automatic contractual trigger — the strongest single reason to pay for a CVIN lookup. ———————————————————————————————————————————————————————————— [insurance-01] Insured subject and continuous history as underwriting basis · Insurance Where: Proposal Form, "Subject Description" and Policy, "Basis of Claims" The insured subject is identified by CVIN (see Schedule of Cover). The Applicant authorises the Insurer to query the registry history of that CVIN as the common basis for underwriting and claims, and agrees that the continuous history from first observation (including power-on hours, ECC error counts, temperature variation, and changes of location) constitutes a written record of equipment condition. The Applicant warrants that no undisclosed encumbrance is registered against that CVIN at inception. Why: Moves "equipment condition" from a post-loss argument to a pre-loss continuous record. That is precisely what an insurer is buying. ———————————————————————————————————————————————————————————— [rwa-01] Pool asset identification and ongoing disclosure · RWA Pool Where: Pool Admission Agreement / Offering Memorandum, "Underlying Assets" section Each underlying asset admitted to the Pool shall be identified by CVIN, and CVIN coverage of pool assets shall be 100% (i.e. no asset that cannot be traced to a specific physical unit). The Issuer shall disclose monthly: the liveness distribution of pool assets (active / stale / dormant), the number of double-pledge alerts, and the identity level distribution (L0 / L1 / L2). Any monthly disclosure in which L0 assets exceed 10% shall trigger an interim disclosure. Why: "L0 share above threshold triggers interim disclosure" turns identity level into a single number investors can read — and gives the issuer a reason to upgrade L0 to L1. ———————————————————————————————————————————————————————————— [audit-01] Independent re-verification right of the diligence party · Audit / Diligence Where: Diligence Agreement / Facility Letter, "Information Verification" clause The diligence party may, without reliance on any summary or screenshot supplied by the counterparty, independently re-verify against the public registry: the completeness of the observation history for any CVIN (whether the hash chain is intact), the validity of signed telemetry, and the status of security registrations. Registry output is replayable (hash = sha256(canon({cvin,obs_type,source_url,observed_at,attrs,prev_hash}))), and the parties agree that the independently replayed result shall govern. Why: "Independently replayed result shall govern" moves verification cost from trusting the counterparty to running a script.