deposit(amount), or use
depositWithPermit to do both in one transaction. A deposit below the contract's
MIN_DEPOSIT is refused. The exchange credits the deposit once its block is a
few seconds old (the confirmation depth, confirmationSeconds in
GET /v1/config). Your first deposit opens your account. See
Funding.owed(you).collect(you) sends what is owed to your own address. Anyone may call it,
and the exchange does for every payout it executes.requestForcedWithdrawal(amount) on the
contract. The exchange must answer: it cancels your resting orders and debits
up to that amount of free cash, as a forced payout record. The request is
answered when the contract executes that record, not before.FORCE_WINDOW, anyone may call freeze(you). Only your account freezes;
everyone else keeps trading.escapeWithdraw() once your cash is final, and the contract
pays it. Your cash is final when no fill of yours is left that the contract
could still execute: the contract has executed fills timed past your freeze
plus FREEZE_GRACE, or it has executed every fill committed to it and the
exchange's commitments reach past that instant (a quiet market). Your open
positions stay claimable at expiry.FORCE_WINDOW after the freeze, escapeWithdraw() pays you anyway, and in
doing so freezes the whole contract, not only your account. Reaching that
point means execution has stopped for everyone, so nothing trades or executes
after it. Every account then leaves at its last executed state, and fills the
exchange committed but the contract never executed are lost to both sides.FORCE_WINDOW,
FREEZE_GRACE, USER_ACTION_DELAY, ORACLE_TIMEOUT, ANCHOR_BEHIND and
ANCHOR_AHEAD, and so is MIN_DEPOSIT. Read them from the contract;
GET /v1/config also serves the first four.setSigningKey(key, expiry) registers a key that may sign your orders and
cancels and open your sessions, until expiry (unix seconds; 0 revokes).cancelUpTo(nonce) raises your nonce floor, so no order signed under a lower
nonce can ever execute.USER_ACTION_DELAY, but the exchange
cancels the orders they affect as soon as it reads them from the chain. To make
sure it has, the gateway refuses new orders from everyone while its chain reader
is too far behind (a 503, see Errors).