GPU-backed lending: from on-chain leads to legal perfection
The bottom line first: what makes a GPU loan legally enforceable is the UCC-1 filing (US) or the PBOC movable-property registry (mainland China) — not any on-chain record. What device history gives you is the work on both sides of that step: before funding, find out whether the device is already pledged elsewhere; after funding, leave a timestamped trail nobody can rewrite. This page is a procedure your credit team can execute as written, or print and hand to risk.
What this SOP cannot do for you
① On-chain lien records do not create a security interest and are not effective against third parties. The filings that count are the PBOC unified movable-property registry in mainland China and the Secretary of State UCC-1 in the United States.
② We do not perform statutory filings, and we do not replace them. That step can only be done by the secured party itself, in the official system.
③ An on-chain record proves only that someone claimed a lien on this device at a point in time — it does not prove the claim is valid. Validity comes from the contract and the statutory filing.
This boundary is not humility — it is the product. What a lender fears most is not a limited tool, but a tool that makes uncovered risk look covered. A pledge checked only on CVIN and never perfected may be worth close to nothing in a bankruptcy waterfall. That loss should never be attributed to a due-diligence report.
Three steps at a glance: who, where, what it costs to skip
| Step | What | Where | Who | Output | Skippable? |
|---|---|---|---|---|---|
| 0 | Confirm this is a device, not a model | This protocol /v1/resolve | Credit / risk | Identity level L0/L1/L2 | No — an L0 pledge is a pledge of a listing |
| 1 | Check duplicate-pledge leads | This protocol (free) | Credit / risk | Active liens / risk flags / collateral schedule | Skippable, but you give up the only real-time cross-check |
| 2 | Statutory perfection | UCC-1 / PBOC registry | The lender itself | Priority against third parties | Absolutely not — the only step that creates legal effect |
| 3 | Evidence trail | This protocol + timestamp anchoring | Risk / legal | Evidence chain for disputes | Skippable, but in a dispute you rely on everyone's own story |
Steps 0 + 1: check the leads (~40 minutes, all free)
Step 0 is the level gate. A device must be at L1 (serial-observable) or L2 (device-signed) to enter a collateral workflow. L0 is a listing fingerprint — it proves a quote appeared on the market, not that one physical machine exists behind it; M is model-level market data and points at a model, not a machine. Pledging on L0/M is pledging a sentence, not an asset.
# ① What level is this device, how many liens, any real duplicate-pledge risk
curl -s 'https://cvin.org/v1/resolve/cvin%3Anv.h100.sxm.80g%3A3ij511ie1hb8e1r6' | jq '{
identity_level, # L0 / L1 / L2 — reject L0 outright
active_liens, # lien count (free tier shows this)
duplicate_pledge_risk_real, # duplicate-pledge signal from real lenders only
data_quality # real / declared / synthetic split
}'
# ② Is it eligible for pledge registration
curl -s 'https://cvin.org/v1/permits?cvin=<CVIN>&use=collateral' | jq '.check'
# ③ A whole batch, one schedule (use it directly as contract exhibit 1)
curl -s -X POST 'https://cvin.org/v1/schedule' \
-H 'content-type: application/json' \
-d '{"cvins":["cvin:...","cvin:..."]}' | jq '.items[] | {cvin, can_pledge, reason}'Reading rules (follow this table; you don't need to understand the protocol):
| Signal | Meaning | Action |
|---|---|---|
| identity_level = L0 or M | Not an identifiable physical device | Decline the pledge; require the borrower to register serials first (upgrades to L1) |
| duplicate_pledge_risk_real = true | A real lender has recorded a lien | Pause funding; obtain a written release or payoff confirmation from the prior lienholder |
| data_quality.real = 0 | No real external observations — records are declared or synthetic | Not underwriting evidence; either collect observations or price as a no-history device |
| permits.check.allowed = false | The protocol governance layer bars this level for pledges | No exceptions — this gate is set by the governance charter, not by sales |
| Long gaps in the timeline | Device went offline / changed hands | Require an explanation; the longer the gap, the harder the recovery |
Step 2: statutory perfection (the only step that creates priority)
Filed by the lender itselfOne rule of law is enough to remember: in the US, Article 9 of the UCC — a security interest is not effective against third parties until perfected, and for equipment collateral perfection means filing. In risk language: an unperfected security interest is not "nothing", it is "discounted" — the borrower sells the device to an unsuspecting buyer, and you cannot claw it back.
UCC-1 financing statement
Who files: the secured party, with the Secretary of State of the debtor's jurisdiction (state of organization for entities — not necessarily where the GPUs physically sit).
Term: 5 years.
Continuation: a continuation statement is only effective if filed within the 6 months before expiry — filing 7 months early is invalid; the most common and most expensive error there is.
Collateral description: may be broad ("all equipment now owned or hereafter acquired"), but the narrower it is, the easier later-acquired devices slip outside the secured scope.
Fee: varies by state, typically tens of dollars.
PBOC unified movable-property registry (中登网)
Who files: the secured party registers an account, fills and submits the filing itself; the registry performs no substantive review — a wrong description is your responsibility, and outsiders cannot see it is wrong.
What is filed: debtor identity and license number, the collateral description, the secured claim amount and term, the filing period.
Term: parties set start and end dates; extendable; file a termination when the debt is repaid early.
Financial leases file separately: a lessor registers ownership, not a security interest.
Fees and rules: per the registry's published schedule (zhongdengwang.org.cn).
The collateral consists of N (___) GPU compute devices owned by the debtor, itemized in Exhibit 1 (Collateral Schedule), each device uniquely identified by its Compute Asset Verification & Identification Number (CVIN: maker-model-form-memory + first 16 hex of SHA-256 of serial) — including NVIDIA H100 SXM 80G (serial hash xxxx…, N1 units), NVIDIA A100 SXM4 80G (serial hash yyyy…, N2 units), …
Why write it this way: "a batch of GPUs" cannot be particularized against a third party — the debtor can always argue "you pledged those fifty, not these fifty." Model + serial hash + count locks the description to the physical assets. Exhibit 1 is the schedule exported from
/v1/schedule — it carries per-device CVIN, level, lien conflicts and data quality, in a format that matches filing requirements.Step 3: the evidence trail (five exhibits)
This step creates no rights; it decides who can tell the story straight when something goes wrong. Archive the five exhibits in order; mark whatever is missing — an honest gap beats a fake completeness, because opposing counsel will ask either way.
| # | Exhibit | Where to get it | It proves | It does not prove |
|---|---|---|---|---|
| 1 | Device identity resolution | GET /v1/resolve/{cvin} | The device's identity, level and lien state at the time of filing | That the device still exists right now |
| 2 | Observation continuity proof | GET /v1/history/{cvin} + /v1/verify/{cvin} | When the device was listed, whether the observation chain has gaps, whether signatures are continuous | That the condition is good (that takes telemetry and inspection records) |
| 3 | Collateral schedule | POST /v1/schedule | Batch eligibility conclusions; usable directly as contract Exhibit 1 | A statutory filing |
| 4 | Timestamp anchoring certificate | The .ots files on /anchors | That the above materials existed before a given Bitcoin block (10 / 11 ledger records confirmed in-block; highest block 975,481) | That the content is correct — only that it existed at a time |
| 5 | Data-quality disclosure | The data_quality field in any response | How much is real observation vs declared vs synthetic | Nothing about quality — it only labels provenance honestly |
How the other side (a judge, or opposing counsel) verifies exhibit 4: run ots info on the .ots file and read the BitcoinBlockHeaderAttestation(block height); open that height in any block explorer and compare the merkle root with the one in the file. None of this requires cvin.org to be alive — the proof stands even if this site disappears tomorrow. Full procedure on /anchors (three-layer self-verification).
Eight common mistakes (each one has really happened)
| # | Mistake | Consequence | How to avoid it |
|---|---|---|---|
| 1 | Checked liens only on a commercial platform, never perfected | Security interest unperfected; priority may vanish in bankruptcy | Make the statutory filing a condition precedent to disbursement |
| 2 | Filed first, checked for duplicates later | Rival lien discovered after filing; unwinding a filing is worse than not filing | Follow this page's order strictly: check → file → evidence |
| 3 | Collateral description says "a batch of GPUs" | Cannot be particularized; loses against third parties | Model + serial hash + count; attach the /v1/schedule output |
| 4 | UCC-1 continuation filed 7 months early | Continuation invalid; at 5 years the interest unperfects and priority resets | Put the expiry date plus the "last 6 months" window in the calendar, with two reminders |
| 5 | Underwriting on model-level market data | You pledged a market price, not a machine; nothing to execute against on default | Collateral schedules accept only L1/L2 device-level records |
| 6 | Accepting an L0 device as collateral | The "device" is somebody's listing page; it may not physically exist | Hard gate: reject anything not L1/L2 — no exceptions |
| 7 | Looking only at current state, not continuity | A device dark for six months is far riskier than the same model continuously listed | Make gap length a pricing factor; put it on the approval sheet |
| 8 | Forgetting to terminate after payoff | Stale lien records pollute your ledger and block the borrower's next financing | Fixed step in the payoff flow: registry termination + on-chain release |
One-page checklist (printable)
Ctrl/⌘ + P → A4☐ Every device has a CVIN and
/v1/resolve shows L1 or L2 (L0/M excluded, no exceptions)☐ Device count matches the contract; serial hashes cross-checked
☐ No device with
data_quality.real = 0 (or priced as no-history)B. Before funding · duplicate check
☐
duplicate_pledge_risk_real is false for every device☐
/v1/permits?use=collateral returns allowed for every device☐
/v1/schedule generated and archived as Exhibit 1☐ Statutory registry also searched by debtor name (on-chain by device, registry by party — you need both)
C. Funding day · perfection
☐ UCC-1 / registry filing submitted; filing number obtained: ______________
☐ Collateral description includes model + serial hash + count (not "a batch of GPUs")
☐ Term recorded; expiry reminder set (UCC-1: continuation only within the last 6 months)
☐ If a financial lease, ownership registration filed separately
D. After funding · archive
☐ Exhibit 1: device identity resolution (same-day snapshot)
☐ Exhibit 2: observation continuity proof + signature verification result
☐ Exhibit 3: collateral schedule (same batch as Exhibit 1)
☐ Exhibit 4: timestamp anchoring
.ots files and block height: ______________☐ Exhibit 5: data-quality disclosure
E. At payoff
☐ Statutory termination filed (termination number obtained)
☐ On-chain
release written, so stale liens don't block the borrower's next financing
FAQ
Do on-chain lien records have legal effect?
No security interest is created. Under US law, a security interest attaches by contract but is not effective against third parties until perfected — perfection for equipment collateral means filing a UCC-1 with the Secretary of State (in mainland China, the statutory registry is zhongdengwang.org.cn, the PBOC Credit Reference Center's unified movable-property filing system). CVIN lien records are diligence leads and evidence, not title instruments. Any claim that "on-chain registration = perfected" is wrong, including when we say it.
Then what is the CVIN lien record good for?
Two things statutory registries cannot do: ① real-time cross-checking — UCC-1 filings are indexed by debtor name, so you cannot see "these 200 devices are also pledged to someone else" as a device-level cross-party view; on-chain records are indexed by device identity, one call returns every active lien. It cannot catch re-pledges that were already perfected, but it catches the ones privately re-pledged and not yet filed — which is exactly the most common window for fraud. ② timestamped evidence — the device state at the moment of registration (listed, model, serial-hash) is anchored into Bitcoin; in a later dispute you don't depend on either party's own records.
How long does a UCC-1 filing take? Can we do it on funding day?
E-filing with most Secretaries of State confirms within minutes to hours. The real work is preparing the collateral description — "a batch of GPUs" is close to worthless against a good-faith purchaser; it must particularize down to model + serial number (or its hash) + count. Section 03 below has a template you can copy. Also verify you are filing in the debtor's state of organization, not the equipment's location.
What are the classic UCC-1 traps?
The worst is the continuation window: a UCC-1 lapses after 5 years, and a continuation statement is only effective if filed within the 6 months before expiry — filing 7 months early is invalid, and a lapsed filing means the security interest is unperfected and priority is lost. Second: filing in the wrong state (use the debtor's state of organization, not where the GPUs sit). Third: a collateral description so narrow that later-acquired equipment falls outside the secured scope.
What if the equipment is leased, not pledged?
Different filing: the lessor registers its ownership of the leased property, not a security interest. In mainland China, under Civil Code Article 745, a lessor may register its ownership of the leased asset — and without registration cannot assert it against a good-faith third party. For GPU lessors this means the equipment must be registered even while it sits in a customer's rack, or a good-faith buyer can keep it. On the CVIN side, operator changes are recorded as events, complementary to the statutory filing.
Where is the one-page checklist? Can I print it?
Section 06 — print directly with Ctrl/⌘+P to A4 (print styles included; navigation and footers hide automatically). The order of the list is the order of execution, and every line is tickable.
This page is not legal advice. Filing requirements, fees and timing follow the current rules of the relevant Secretary of State / the PBOC registry.