Deposit and Escrow Terms

Every bid on GPU SLAX is backed by a deposit equal to 20 percent of the bid's notional. Notional is price multiplied by quantity multiplied by 8,760 hours per contract year. The 20 percent rule is a platform-wide constant in this version.

Worked example: a bid at $10.00 per GPU-hour for one NVL72 rack (72 GPUs) on a one-year ticker has a notional of $6,307,200 and a deposit of $1,261,440.

When a bid is placed the deposit moves from the available balance to the locked balance of the bidder's wallet. If the available balance is insufficient the order is rejected with a clear message and nothing moves.

Cancelling an unfilled bid returns the locked amount to available. A partial fill escrows the deposit for the filled quantity and keeps the remainder locked.

On fill the deposit for the filled quantity, computed at the trade price, moves from locked into escrow. Any excess locked at a higher limit price is returned to available at the same moment. The exchange fee is charged separately from the taker's available balance.

Escrowed funds are held by the Exchange for the benefit of the two sides of the SLA. They are not available for other orders and cannot be withdrawn while the SLA is outstanding.

When a held SLA is resold before activation, the new holder's deposit is escrowed at fill and the previous holder's escrowed deposit is returned to their available balance. The transfer is written to the ledger as a single settled sequence so the escrow backing the SLA is never interrupted.

Escrow is released to the Provider's available balance when the Exchange records proof of SSH access under the SLA activation flow. The release writes an ESCROW_RELEASE row naming both organisations.

If the SLA is terminated for Provider default before activation, escrow returns to the holder in full. If the holder abandons activation after the Provider has deployed, the Exchange may release escrow to the Provider as liquidated damages after the notice period in the SLA.

Funds enter and leave the exchange wallet through a bank partner rail. In this version the rail is a development mock that credits instantly and records the movement. When the real rail is connected, deposits settle on bank confirmation and withdrawals settle on payout confirmation.

Custody structure, segregation of client funds and any money transmission licensing are open items for counsel and the bank partner. Until they are settled the exchange holds only development balances.

Every deposit, lock, unlock, escrow, fee, trade, transfer and release is one row in an append-only ledger. Each row's hash is the SHA-256 of the previous row's hash and the canonical JSON of the row. Anyone can verify the chain at /ledger. Publishing the chain head to a public network is planned and is not yet live.

These terms are read together with the SLA and the MSA. This is a draft template for discussion. It has not been reviewed by counsel and is not legal advice.