Innovation Blockchain

Draft for review

GPU Collateral Inspection Standard

This standard sets out how Innovation Blockchain inspects GPU hardware that secures a loan, what evidence it keeps, and what it reports. It is written so that a lender, a borrower and a second inspector would each reach the same result from the same facility.

Numbers marked proposed are starting defaults. They are to be tested with lenders and fixed in version 0.2. This page is a summary of a working draft. The service is in pilot preparation and the standard has not yet been used on a client engagement.

1 Purpose

Purpose

A lender who finances GPUs needs to know five things, at funding and for the life of the loan.

  1. The hardware on the collateral schedule exists.
  2. It is the hardware that was paid for, unit by unit.
  3. It sits where the loan documents say it sits.
  4. It is powered, cooled and running.
  5. Nobody else has a competing claim that the lender has not been told about.

This standard turns those five questions into repeatable procedures.

2 Scope

What this standard is, and is not

It is a set of agreed procedures carried out by an independent inspector, with findings reported as facts and exceptions.

It is not a financial audit, a valuation or appraisal, a legal opinion on title or lien priority, or investment advice. Where a procedure touches a legal question, the inspector records what the documents and counterparties say and leaves the legal conclusion to the lender's counsel.

3 Independence

Independence

  • The inspector holds no interest in the borrower, the lender, the hardware or the loan.
  • Fees are fixed per engagement. They never depend on the result or on the loan closing.
  • The inspector does not arrange, broker or recommend financing.
  • Any relationship that a reasonable lender would want to know about is disclosed in the report.

4 Engagements

Engagement types

CodeTypeWhen
FFunding inspectionBefore the first draw, or before a loan is sold to a new holder
QPeriodic re-verificationEvery quarter proposed while the loan is outstanding
EEvent inspectionAfter a trigger listed in section 12

5 Inputs

Inputs required before fieldwork

From the lender

  • The collateral schedule, with a serial number for every GPU and every server chassis
  • The security filing schedule (in the US, the UCC-1 collateral description)
  • The loan or facility reference, and the site address the loan documents rely on
  • Any landlord waiver or access agreement for the site

From the borrower

  • Purchase invoices and the bill of materials
  • A rack elevation or asset map showing where each chassis sits
  • The key terms of the colocation agreement: suite or cage, contracted power, term, payment status
  • The insurance certificate for the hardware
  • Supervised access to the running systems, or read-only remote access

Fieldwork does not start until the schedule and the invoices are in hand. A schedule without serial numbers is a Red finding on its own.

6 Procedures

Procedures

  1. 6.1

    Document reconciliation

    • Match every serial on the collateral schedule to an invoice line and a bill-of-materials line.
    • Match the schedule to the security filing schedule.
    • Check for duplicate serials, serials in the wrong format for the stated model, and units invoiced but not scheduled.
    • Record the count at each step: scheduled, invoiced, filed.
  2. 6.2

    System-read identity

    • Read the GPU serial numbers from the running systems for every scheduled GPU, in a session the inspector controls or directly observes.
    • Where the hardware supports it, collect the manufacturer's hardware attestation for each GPU, which confirms a genuine device and its identity.
    • Record model, firmware and driver versions.
    • Save the raw output and compute its hash at the time of capture.
    • Match the system-read serials to the collateral schedule. Every unmatched serial, in either direction, is a finding.
  3. 6.3

    Physical inspection

    • Walk every rack that holds scheduled hardware.
    • Check chassis serials and asset tags against the schedule and the asset map, to the sample size in section 7.
    • Photograph each checked chassis: serial label, rack position, and the rack as a whole.
    • Look for units that are present but not working: no power draw, no network link, no response to a short test workload chosen by the inspector.
    • Note any labels, tags or notices on the equipment that name another owner or secured party.
  4. 6.4

    Location and custody

    • Confirm the site address, building, suite and cage against the loan documents and the landlord waiver.
    • Obtain a written confirmation directly from the facility operator, not through the borrower, that the borrower occupies that space.
    • Record who controls physical access and who is on the access list.
  5. 6.5

    Power and cooling

    • Compare contracted power for the space with the nameplate demand of the scheduled hardware.
    • Record measured power draw at the rack or circuit level during the inspection.
    • Record the cooling method and whether it matches what the hardware requires at the installed density.
    • Record any redundancy the colocation agreement promises and whether it is visibly in place.
  6. 6.6

    Competing claims

    • Ask the facility operator, in writing, whether the borrower's account is current and whether the operator asserts any lien or right of retention over the equipment.
    • Record the results of any lien or secured-party search the lender's counsel provides. The inspector records these. Counsel interprets them.
    • Record whether each unit is owned or leased, as the documents state.
  7. 6.7

    Operating evidence

    • Review utilisation and uptime records for the previous 30 days proposed.
    • Confirm that rental or service contracts exist for the capacity the borrower says is contracted, and record the coverage as a ratio. Customer names and prices stay private and are not reproduced in the report.
  8. 6.8

    Insurance

    • Confirm the certificate is current, covers the scheduled hardware at the inspected address, and names the lender as the loan documents require.

7 Sampling

Sampling

CheckCoverage
System-read serials (6.2)100% of scheduled GPUs
Rack walk (6.3)100% of racks
Chassis-level physical check (6.3)100% up to 50 chassis. Above that, 50 plus 10% of the remainder proposed
Test workload (6.3)5% of chassis, minimum 5 proposed

The inspector picks the sample on the day. The operator never picks it. Any mismatch in a sample moves that check to 100%.

8 Evidence

Evidence rules

  • Every material fact rests on two independent sources where two exist: for example, a system-read serial and a photographed label.
  • Photographs carry a timestamp. Raw system output is kept unedited and hashed.
  • Evidence supplied by the borrower is labelled as such. Evidence obtained directly from a third party is labelled as such.
  • The evidence bundle is retained for the loan term plus a period agreed with the lender.
  • Private data (customer names, prices, contract terms) is held under confidentiality and never published.

9 Findings

Findings

Each finding has a reference, a description, the evidence it rests on, a proposed correction, an owner and a due date.

RatingMeaningExamples
Red The collateral is not as represented, or cannot be verified Scheduled units missing. A serial mismatch that is not explained. The site differs from the loan documents. The operator asserts a lien. Access refused.
Amber Verified, but with a gap that needs correction by a date A warranty replacement not yet reflected in the schedule. An insurance certificate out of date. Power headroom below contract.
Green Verified with no exception

The overall result is Pass, Pass with exceptions (Amber only) or Fail (any open Red).

10 Report

The report

  1. Cover: facility, loan reference, engagement type, inspection dates, inspector
  2. Scope, and anything that could not be done and why
  3. Result, with a count table: scheduled, system-read matched, physically sighted, exceptions
  4. Findings register
  5. Evidence index
  6. Statement of independence
  7. SHA-256 hash of the report and of the evidence bundle, with a timestamp

11 Proof record

The proof record

Each report also produces a short machine-readable record, so that a lending contract can check it without reading the report.

FieldContent
Facility IDA pseudonym. No client or site name
Schedule hashHash of the collateral schedule inspected
Engagement typeF, Q or E
Inspection dateThe date of the inspection
CountsScheduled, matched, exceptions
ResultPass, Pass with exceptions, or Fail
Valid untilSee section 12
Report hashFrom section 10
Inspector signatureThe inspector's signature over the record

The record is chain-neutral. The first target is a Flare Confidential Compute extension that checks the private inputs and publishes only the result. No private data goes on any chain.

Status of that target: a prototype for Flare's Coston2 testnet, not deployed yet. Flare Confidential Compute is not on Flare mainnet and Flare has published no date. See current status.

12 Validity

Validity and triggers

  • A funding inspection is valid for 90 days proposed.
  • A periodic re-verification is valid until the next one is due, plus 14 days' grace proposed.
  • After that the proof record is stale, and a contract relying on it should treat stale the same as Fail.

Triggers for an event inspection

  • Hardware moved to another rack, suite or site
  • A warranty replacement or any change of serial
  • A missed colocation payment, or notice of one from the facility operator
  • A change of facility operator, or of the party operating the hardware
  • A system-read that no longer matches the schedule
  • A request from the lender

13 Limitations

Limitations

  • The inspection reports conditions on the inspection dates. It does not warrant them afterwards.
  • A sample can miss an exception outside it. The sampling in section 7 is disclosed in every report.
  • Hardware attestation confirms that a device is genuine and which device it is. It does not confirm who owns it or where it is.
  • The inspector relies on third-party confirmations as given and identifies their source.

This document is a working standard for a professional service. It is not legal advice, and the engagement terms that sit around it need review by counsel before first use.