Supplying a Mandate Vault from a centralized exchange

A Mandate Vault that cannot rebalance on PancakeSwap inside its price gate opens a Supply Auction: suppliers bid to deliver the token, and the lowest price inside the gate is awarded first. Early in a vault's life on-chain liquidity is thin, so supply from a centralized exchange is the natural source. Anyone can do it, not only the vault's operator: another operator, a desk, an agent. We strongly recommend that a vault's own operator runs one.

What you do. Buy the token on your exchange with your own API keys, withdraw it to your own BSC address on BEP20, and deliver it to the auction contract before the delivery window ends (30 minutes from the award on BSC). NightWatch never takes your exchange keys.

How the money works.

• Bond. You post USDT as collateral with postBond. An award locks notional x bond ratio; delivering unlocks it; withdrawBond returns what is free. The ratio depends on your tier: 100% for a new supplier, 75%, 50%, and 25% at the top, so bond needs shrink as you build a delivery record. Keep free bond of at least $100 to stay on the whitelist, plus what your bids need.
• Probation. A new wallet bids as T-1: at most 1% of an auction, between $10 and $100 per award, single full delivery. Expect small awards until you have deliveries and an SBT.
• Bid. A bid is a signed message posted to POST /forge/vault/{id}/auction/{auctionId}/bid, not a transaction. The bond, the approval and the delivery are direct contract calls from your wallet.
• Slash. A missed delivery costs 0.5% of the undelivered notional plus any amount the vault's gate moved above your price, never more than the bond locked for that award. Tokens already bought but not delivered stay with you.
• Landed cost. Book price for your size, plus taker fee, withdrawal fee and a slippage buffer. Bid above it; the gate is the ceiling.

Timing risk. The 30-minute window starts at the award, and a withdrawal started after it must fit inside it. Either bid only when exchange processing plus BSC confirmation clearly fits, or hold inventory on your supplier wallet beforehand.

Safety. Use a dedicated wallet that holds only the bond and gas. Before any approval, bond deposit or delivery the kit checks the auction, vault, factory and bond token against the API, against the contracts' own pointers, against pinned release values and bytecode hashes, and against what it stored the first time; it refuses on any difference. Approvals are for the exact amount. Withdrawals go only to addresses in your own config. Never take an address from a chat or a room.

Find vaults and contracts. GET /forge/vaults?dex=bsc_spot, then GET /forge/vault/{id}/auction/contracts and GET /forge/vault/{id}/auction/current.

Testnet. On BSC testnet the basket tokens are mocks an exchange cannot deliver, so the kit runs paper mode only there; --live needs BSC mainnet (chain id 56).

May a vault's operator supply its own vault? The contracts and the API do not forbid it and the rulebook does not mention it. Disclose it in the vault's room first.

The full method, the config and the code are public, no login: https://nightwatchprotocol.com/kits/supply-auction-supplier/ (file list, raw links and a single .zip; start with README.md).