Most people who sign a forward contract assume they are locked in until delivery. On a bilateral OEM purchase order, that is roughly true. You committed to a specific configuration, on a specific date, for a specific dollar figure, and unwinding it means a phone call, a credit memo, and a favor you would rather not spend. The contract was built for two parties and it dies with those two parties.
A Rillor forward is different in one structural way that turns out to matter more than any single price. Before the delivery date, the buyer of record can transfer the contract to another verified, KYC'd buyer, with Rillor and the OEM approving the move. That single feature, pre-delivery assignment, is what makes a standardized forward behave like a position in a market rather than a line item in a procurement file. It is also, for a buyer whose plans have changed, the practical way to exit.
Why transferability is the whole point
In any standardized forward or futures market, the vast majority of positions are never held to physical delivery. They are closed out earlier by an offsetting trade, a participant buying back a short or selling a long before the delivery date arrives. The CFTC makes this plain in its own description of how these markets function: most contracts by volume are liquidated rather than delivered, because standardization lets a large number of participants trade the same fungible instrument and step in and out of it as their needs change.
Rillor takes that same economic logic and grounds it in physical hardware. We do not offer an offsetting paper trade, because a Rillor forward always ends in delivery of complete OEM GPU systems and is never cash-settled. What we offer instead is assignment. If you no longer want to take delivery yourself, you transfer the contract to someone who does. The obligation to take the hardware does not vanish, it moves. That is the physical-market equivalent of closing your position, and it is the reason a forward you bought in January is not a trap if your world looks different in June.
If you want the framing behind why we settle in steel and not in dollars, read why Rillor settles physically and never cash-settles. This article is the operational companion to that one. It covers the mechanics.
Standardization is the enabler
You cannot transfer what is not fungible. A bespoke supply agreement, the kind the CFTC describes as a commercial, physically delivered contract with personalized terms negotiated between two specific counterparties, is unique by construction. Its delivery windows, its acceptance criteria, its custom integration clauses, all of that was written for one buyer. Hand it to a stranger and almost nothing fits. Standardization buys liquidity, but it does so by giving up the ability to be a bespoke merchandising vehicle. That tradeoff is exactly the one Rillor makes on purpose.
Every Rillor forward reduces to the same six fields: SKU, quantity, forward price, delivery date, delivery location class, and counterparty obligations. Two contracts with the same six fields are interchangeable. That is only credible because the underlying systems are genuinely identical across the channel. An HGX B200 board is the same engineered object whether it ships inside a Supermicro SYS-A22GA-NBRT, a Gigabyte G894-AD1-AAX5, a Dell PowerEdge XE9680L, or a Lenovo SR680a V3. Lenovo's own product guide for the HGX B200 spells out the spec that every OEM inherits: an 8-GPU SXM6 baseboard, 180 GB of HBM3e per GPU, 7.7 TB/s of memory bandwidth, 900 GB/s of NVLink GPU-to-GPU bandwidth, and 1000W per GPU. NVIDIA's DGX B200 datasheet describes the same 8-GPU Blackwell platform from the other end: 1,440 GB of total GPU memory, 14.4 TB/s of aggregate NVLink bandwidth, roughly 14.3 kW of system power, and 144 PFLOPS of FP4 compute.
When the thing being delivered is that tightly specified, a contract on RIL-GX-B200-2T means the same thing to every buyer. That is what makes one buyer's position acceptable collateral for another buyer's buildout. We unpack this contrast in full in standardized forwards versus bespoke supply agreements, and the deeper finance distinction in forward contracts versus futures for GPU systems.
The transfer, step by step
Assignment on Rillor is a controlled novation. In legal terms, a novation moves both the rights and the obligations of a contract from the original party to a new one, and it is only valid with the consent of every governing party to the original agreement. That last clause is the reason a Rillor transfer is not a one-click resale. It is the reason it is trustworthy.
Step 1. The current buyer requests the transfer
The buyer of record opens the contract in the marketplace and initiates a transfer. At this stage you are signaling intent, not committing to a counterparty. You can transfer the whole contract or, where the contract covers multiple units, a defined slice of it, so a buyer releasing two of six RIL-GX-B200-2T systems keeps the rest.
Step 2. A new verified buyer is identified and matched
The incoming party must already be a verified, KYC'd Rillor buyer in good standing. There is no path for an unvetted entity to inherit a position. You can name a specific counterparty you have already lined up, or you can list the contract for assignment and let Rillor match it against the verified buyer book at the prevailing forward price. The price the new buyer pays is set by where that SKU's forward is trading now, not the price you originally paid, which is precisely how you realize a gain or eat a loss. More on that below.
Step 3. Rillor approves
Rillor, as the neutral operator and escrow coordinator, confirms the incoming buyer's standing, confirms the contract is in good standing with deposit posted and no default flags, and confirms the assignment terms. We are one of the consenting parties to the novation. Our approval is the check that the position being handed over is clean and that the new holder can perform.
Step 4. The OEM approves and re-captures the end-customer-of-record
This is the step that is unique to GPU systems, and it is non-negotiable. The OEM that sold the original forward must approve the new buyer, primarily for NVIDIA channel compliance. NVIDIA-channel hardware is governed by the NVIDIA Partner Network terms, and channel partners ship to specific, approved end customers, not to whoever shows up with a purchase order. This is not a theoretical control. Export licensing for advanced accelerators is routinely granted against a defined, named set of approved end customers, which is a public demonstration of how tightly channel shipments are gated to the end customer of record.
So on transfer, the OEM re-captures the end-customer-of-record for its NVIDIA business unit. The new buyer is the new end customer, and the OEM logs them as such before the assignment can complete. The forward did not just change whose name is on it. It re-established, with the OEM and through it with NVIDIA, who is actually going to operate the hardware. This is the heart of NVIDIA channel compliance inside a forward contract, and it is why a Rillor transfer can never become an anonymous secondary market.
Step 5. The novation closes and the contract is reissued
With all three consenting parties aligned, the original buyer is released, the new buyer is bound, and the contract is reissued in the new buyer's name on the original economic terms for delivery. The delivery date, the SKU, the quantity, the seller's obligations, all of that is unchanged. Only the holder and the end-customer-of-record are new.
How the deposit and the performance bond travel
A buyer thinking about assignment usually asks the same first question. What happens to my 10% deposit, and what happens to the seller's performance bond.
Start with the deposit. The 10% posted at execution is not a down payment on the GPUs in the sense of equity already spent. It functions as a security deposit against performance, the same role margin plays in any futures or commodity position, where the deposit secures the obligation rather than paying down the asset. Because it is a security tied to the contract and not to the person, it travels with the contract. On assignment, the deposit is credited to the incoming buyer's side of the ledger, and the economics are squared in the transfer price. If you bought at a forward of $310,000 per RIL-GX-B200-2T and posted $31,000, and the contract now changes hands at a forward of $340,000, the incoming buyer is stepping into a position with that deposit already in place, and the $30,000 of appreciation per unit is settled between the two buyers as part of the assignment. You are made whole on what you put up, and your gain or loss is the difference between your strike and the current forward.
The seller performance bond travels too, and it has to. The bond is the seller's posted assurance that the systems will be delivered, on spec, on time, and it is attached to the contract, not to the original buyer. When the contract is reissued to the new buyer, the same bond continues to secure the same delivery obligation. The incoming buyer inherits a fully secured position from day one, with both sides of the contract still bonded exactly as they were at execution. Nothing about the seller's exposure changes, which is why the seller's only practical interest in the transfer is the OEM channel-compliance approval, not the economics. For the full scope of what that bond does and does not cover, see what a seller performance bond covers.
The 2% all-in fee and the escrow fee apply to the transaction the same way they apply to any execution. The independent escrow agent coordinates the movement of the deposit and the reissue of the contract, which is the same agent and the same mechanics described in how independent escrow works in a Rillor forward contract.
Two buyers who need this
The abstraction gets concrete fast once you put it against real situations.
The buildout that slipped
You are a tier-2 cloud. Last quarter you locked four RIL-GX-B300-2T systems for delivery this fall, because your colocation provider promised power and cooling on a schedule. The schedule moved. The hall is now landing in the first quarter of next year, and four Blackwell systems arriving into a site that cannot energize them is dead capital plus support costs. You do not want to default, you do not want to renegotiate four delivery dates, and you certainly do not want to pay for racks you cannot turn on.
Assignment is the clean exit. You transfer two of the four systems to another verified buyer whose hall is ready now, and you keep two for a later phase. You are not penalized for a problem that was never about the hardware. The buyer who takes the assignment gets RIL-GX-B300-2T capacity at the current forward, which may be exactly the position they were trying to source on the marketplace anyway.
The buyer who over-committed
You are a model lab that sized capacity against an aggressive training roadmap. The roadmap got sharper. You consolidated two runs into one and you no longer need three of the eight RIL-NVL72-GB200 racks you forwarded. Holding them to delivery means taking metal you will not load. Defaulting means forfeiting deposit and burning your standing with the OEM.
Instead you release the three racks at the current forward price. If NVL72 GB200 forwards have firmed since you locked yours, you exit at a gain. If they have softened, you exit at a managed loss that is almost always smaller than the cost of operating idle rack-scale hardware. Either way you have converted a fixed, illiquid commitment into a position you could actively manage. That is the difference between a procurement contract and a market instrument, and it is the same logic that lets a buyer avoid being stranded by a single decision made many months out. We walk through the planning side of this in how to lock GPU capacity with forward contracts.
Why this is your exit, and not cash settlement
It is worth being precise about the financial mechanism, because the temptation is to compare a Rillor transfer to closing a futures position for cash. They are cousins, not twins.
In a cash-settled market, you realize a gain by selling an offsetting contract and pocketing the difference in dollars, and no commodity ever moves. Rillor does not do that. We are physical-delivery forward, always, and we never cash-settle our own contracts. The Rillor Compute Index, our 30-day rolling-blend forward price per SKU, is what makes cash settlement possible for other people. We own and control that index and license it as a settlement feed to exchanges, funds, and researchers who build cash-settled products against it on their own venues. Rillor does not operate those venues. On Rillor itself, every contract ends in hardware. If you want the index story, that is for markets and the index is the moat.
So how does a buyer realize a gain on Rillor without cash settlement. Through assignment at the prevailing forward. When you transfer a contract whose strike is below today's forward, the appreciation is captured in the transfer price the incoming buyer pays, and it accrues to you. You did not sell paper and walk away from the underlying. You sold your right and obligation to take real systems, to a real buyer who will take them, at a real price set by where that SKU is trading right now. The gain is economically identical to a closed-out long. The settlement is physical for the market as a whole, because someone still takes the hardware. That is the entire design. Transferability is how a standardized physical forward gives buyers a true exit without ever pretending the steel does not have to arrive.
If you are weighing this against your other options, the comparison that matters is laid out in the forward curve, the spot price, and the obsolescence delta. The short version is that allocation is a queue, spot is a gamble on timing, and a forward is the only one of the three you can hand to someone else.
Before you list a contract for transfer
A few practical points worth holding in mind.
| Question | Answer |
|---|---|
| Who can receive a transfer? | Any verified, KYC'd Rillor buyer in good standing. No unvetted parties. |
| Who must approve? | Rillor and the originating OEM. The seller's bond carries over automatically. |
| What gets re-captured? | The end-customer-of-record, logged with the OEM for its NVIDIA business unit. |
| What happens to my deposit? | It travels with the contract and is squared in the transfer price. |
| When can I transfer? | Any time before the contract's delivery date. |
| Do the original terms change? | No. SKU, quantity, delivery date, and seller obligations are preserved. |
Assignment is a feature you should price into a forward before you sign it, not one you reach for only in a crisis. The knowledge that you can move the position is part of what makes committing capacity twelve months out a reasonable thing to do at all. You are not betting that nothing will change. You are buying a standardized instrument that you can pass on if it does.
Lock capacity before you need it.
Tier-2 clouds, sovereign AI programs, and enterprise buildouts use Rillor to commit forward delivery at a transparent price instead of negotiating one-off with each OEM.
See how buyers use Rillor →That is the practical case for the forward market as a market. Browse current SKUs and indicative forwards on the catalog, and if you want the buyer-side mechanics start to finish, for buyers is the place to begin.
- Economic Purpose of Futures Markets and How They Work | CFTC
- Forward Contract definition / TM 97-01 interpretive letter | CFTC
- Futures contract | Wikipedia
- Novation | Wikipedia
- DGX B200: The Foundation for Your AI Factory | NVIDIA
- ThinkSystem NVIDIA HGX B200 180GB 1000W GPU Product Guide | Lenovo Press
- NVIDIA Partner Network (NPN) Terms and Conditions | NVIDIA