Deepcoin supports spot and perpetual trading with separate order, position, and withdrawal records
Deepcoin runs a crypto exchange with spot trading, perpetual contracts, and tools for managing orders and withdrawals. Spot trades change asset balances, while perpetual trades open or close positions backed by margin. Completing either task requires more than submitting an order: execution records show what traded, and withdrawal records track funds leaving the exchange.
A filled purchase can leave assets in an exchange account. A filled closing order can reduce a derivatives position. Neither action, by itself, transfers funds to an external destination. The relevant balance and transaction records establish what happened next.
An accepted order, a completed trade, and a credited withdrawal represent different outcomes, each with its own confirmation record.
Spot balances and perpetual positions
Spot trading exchanges the base asset of a market against its quote asset, while perpetual trading creates price exposure through a derivatives position. An ordinary spot purchase leaves an asset balance. A perpetual position instead has a direction, contract quantity, margin requirement, and unrealized profit or loss.
Contract details matter before order placement. Product information distinguishes linear and inverse contracts and provides contract value, quantity increments, minimum size, and trading status. Those fields describe the selected instrument; an exchange-wide leverage claim cannot replace its actual limits. A listed instrument can also have a suspended or pre-launch status.
Deepcoin also supports merged and split position modes. These determine how positions are organized and identified for subsequent actions. In split mode, closing a particular position requires its position identifier. That distinction matters when several positions share an instrument and direction.
Deposits and transfers between accounts
Crypto deposits depend on the selected asset, supported network, deposit address, and any required memo. Deposit configuration also carries network availability and confirmation information. Matching the asset name alone does not establish that the sending network matches the receiving account. A memo, where required, helps assign the payment to its intended account.
Deposit records distinguish a confirming transaction from a successful deposit. They include the asset, amount, network, and transaction hash. A sender's completed transaction and the exchange's credited balance describe different parts of the transfer. The account balance remains the relevant starting amount for a subsequent trade.
Internal transfers move funds between supported exchange accounts. Deepcoin's transfer API also distinguishes transfers to another user account and transfers involving subaccounts. Each operation has a transfer identifier and status. Moving funds between exchange accounts does not establish receipt at an external blockchain address.
Market, limit, and conditional orders
Market orders seek execution against available liquidity, while limit orders specify an acceptable price. A limit order can remain open when matching liquidity is unavailable. Market execution can involve several fills at different prices, so the eventual average price can differ from the price visible before submission.
Deepcoin supports market, limit, post-only, and immediate-or-cancel orders through its V2 trading API. Price precision and minimum quantity come from the selected instrument. These constraints apply before matching begins; submitting a quantity outside the permitted increment does not create a smaller valid trade automatically.
Conditional orders add a trigger before ordinary execution. The trigger can use the last traded price, index price, or mark price. Once its condition occurs, the system attempts to place the configured market or limit order. A trigger price therefore identifies an activation condition rather than a guaranteed fill price. Take-profit and stop-loss instructions also require attention to the chosen trigger basis and execution type.
When is a Deepcoin order actually complete?
An order has fully executed when its final record shows a filled state. Reconcile the accumulated fills with the requested size using consistent quantity units and the order's quantity setting.
An order identifier establishes which request to inspect. It does not establish that the matching engine has executed the entire quantity.
Order details distinguish live, partially filled, filled, and canceled states. They also separate accumulated fill size, latest fill size, latest fill price, and average execution price. The latest fill describes only the most recent execution. Treating it as the whole order can misstate both quantity and price.
Cancellation applies to a pending order. Any quantity already executed remains a trade, even when cancellation removes the unfilled remainder. Reversing that exposure requires another transaction, with its own execution conditions and costs. A cancellation request can also race with matching, so the final order record matters more than the moment the request left the device.
Execution records and account balances should agree. For derivatives, the corresponding position must also reflect the intended increase, reduction, or closure.
Margin exposure and position closure
Perpetual positions remain exposed to market movement after their opening orders finish. Position records include direction, size, margin used, leverage, liquidation price, and unrealized profit. Unrealized profit describes an open position's valuation; it does not prove that a closing trade has secured that amount.
Cross and isolated margin modes define different boundaries for collateral supporting a position. Cross margin draws on the relevant shared margin balance. Isolated margin assigns collateral to the position. Leverage magnifies exposure relative to margin, and insufficient margin can lead to liquidation. Position mode and margin mode answer different questions: grouping positions does not remove their market exposure.
Closing requires the correct instrument, direction, quantity, and position selection. A filled order for less than the outstanding position leaves residual exposure. Historical positions record opening and closing prices, closed quantity, trading fees, and funding fees. These details support reconciliation after the position ends.
Balance reconciliation after trading
Account bills explain balance changes through entries for trading profit or loss, transaction fees, funding, transfers, and other supported adjustments. Reconcile entries in the same currency and account rather than comparing unrelated totals. A profitable price move can coexist with a smaller net balance change after charges. Withdrawable assets also have account-level availability, which can differ from a headline balance.
Withdrawal checks before authorization
A planned withdrawal can remain unsubmitted while its destination and available amount are checked. Consider funds already available in the relevant account after trading. Record the intended asset, network, destination, and amount before authorizing the transfer. The receiving account must support the asset and network; network availability, fees, and withdrawal limits can change.
- Proceed only when withdrawals are enabled for the selected asset and network.
- Match the receiving address and any required memo to the destination's deposit instructions.
- Meet the minimum withdrawal amount, stay within the withdrawable balance and any remaining quota, and use the permitted precision.
- For an API withdrawal, use an eligible whitelist address and the intended debit account.
- Leave the request unsubmitted if any required condition remains unresolved.
Withdrawal configuration provides those exchange-side limits and requirements before submission. A saved destination does not establish that its receiving service currently accepts deposits.
After authorization, retain the withdrawal identifier and inspect its processing state. Pending or under review means the transfer has not reached its successful terminal state. Deepcoin's withdrawal record includes a canCancel flag indicating whether cancellation remains available. A cancelling state still requires a later terminal result; it does not establish that cancellation finished.
For an on-chain transfer, the transaction hash connects the exchange record to the network transaction. Compare its destination with the intended recipient and confirm the receiving balance or deposit credit. Exchange success alone does not establish that a receiving service has credited the account. Once cancellation is unavailable, a new request cannot undo the original transfer.
Copy trading and chart-based controls
Copy trading provides another way to participate in trading, while chart-based controls support order placement through indicators and drawing tools. Deepcoin also offers position merging and API access. These features change how orders originate or how positions are managed; execution still produces orders, fills, and account changes.
Pending strategy records distinguish conditional orders, indicator orders, line-drawing orders, and tracking exits. An ordinary open-order list therefore does not describe every instruction awaiting a future condition. Trigger history separately records activation details and errors. That separation matters when reviewing an automated setup or ending a trading session.
Copy-trading records include leader position details such as direction, size, margin, and liquidation price. A displayed leader result does not establish the outcome of a follower's account. The relevant evidence remains the positions and balance changes belonging to that account.
Outstanding instructions at exit
Ending a session leaves any outstanding exchange instructions subject to their existing conditions. Review ordinary orders, conditional orders, remaining positions, and transfers separately. Preserve identifiers and final records for completed activity. An empty order list does not prove a flat derivatives position, and a flat position does not prove that a withdrawal arrived.
Deepcoin questions worth asking
Can I use Deepcoin on a mobile device?
Deepcoin provides mobile applications for iOS and Android, alongside web access. Its download page lists the available distribution options.
How should an API client handle an order lookup that briefly returns no result?
An empty lookup immediately after execution can reflect a short delay between pending and historical order records. Query the existing order identifier again rather than assuming failure and submitting a duplicate. Deepcoin identifies its private WebSocket order and trade channels as faster sources of status changes.
What quantity does a spot market order specify?
A spot market order can express its quantity in the base asset or the quote asset, depending on the quantity setting. The distinction changes what the submitted amount means. Confirm that setting before interpreting the order size as either the asset quantity to trade or the quote amount to spend.
Is it possible to amend a conditional order before activation?
Deepcoin supports amendments to incomplete conditional trigger orders. Supported changes include quantity, trigger price, trigger price type, and the order price after activation. The conditional-order amendment operation does not handle tracking exit orders, so those instructions require their applicable controls.
Where can I find the reason a conditional order failed?
Triggered-order history includes error codes and error messages alongside trigger details. An entry in that history does not establish successful execution because the history includes failed activations. Its error information helps distinguish an unsuccessful trigger operation from an ordinary order still waiting for matching liquidity.
Does an API withdrawal accept an arbitrary destination address?
Deepcoin restricts API withdrawals to whitelist addresses. The request uses a whitelist address identifier, and an optional address value checks consistency with that saved destination. A required memo must also match the whitelist entry when it contains one. These requirements apply specifically to the API withdrawal operation.
Why can a historical position show an estimated trading fee?
Deepcoin estimates the historical position fee from finished-order fees when the historical position fee is unavailable. That fallback concerns the position-history field. For detailed reconciliation, retain the underlying completed orders and account entries rather than treating every position summary as an independently calculated fee record.
Updated on