NEXUS

Manage Orders

Open Request List (Pending Requests)

Requests submitted by users that are not yet processed are classified as “pending”.
These remain active until the specified conditions (e.g., a certain price threshold) are met.

Once created, a request stays pending until matched with external network conditions.
When the condition is satisfied, the request is processed and recorded as completed.


Description

Successfully submitted requests appear in a list format similar to the example below.

Open Requests Table

FieldDescription
Request TimeDisplayed in the device's local time, sorted by creation time.
PairCombination of the requested token paired with CROSS Coin.
Request TypeDirection of the request: acquisition or release.
Request ModeBasic (limit/market) or advanced strategies (conditional, automated logic).
Request PricePrice specified at the time of request submission.
Requested AmountTotal quantity specified by the user.
Processed AmountQuantity of the request that has already been processed.
Request ValueTotal value calculated (amount × price).
Trigger ConditionActivated when the external price reaches the specified trigger value.
Validity PeriodDuration the request remains active.
Cancel RequestRequires a wallet signature to cancel a pending request.

Request History

Request history displays a full log of past submissions, showing whether token acquisition or release requests were processed, including timing and conditions.
This helps users analyze patterns and make more informed decisions.


Description

The history includes fully processed, partially processed, canceled, and expired requests.
Users can filter results by 1 day, 1 week, 1 month, 3 months, or a custom date range.

You can select dates via a calendar and expand individual requests for details.

Request History Table

FieldDescription
Request TimeDisplayed in UTC, sorted by creation time.
TokenToken paired with CROSS Coin.
Request TypeIndicates acquisition or release.
Request ModeLimit, market, or strategy-based request.
Average Fill PriceWeighted average price of processed parts.
Initial Request PricePrice entered at the time of submission.
Requested AmountFull amount specified in the request.
Request ValueTotal value calculated (amount × price).
Request StatusCompleted, Partially Completed, Canceled, or Expired.
Transaction HashView the transaction on a blockchain explorer.
Single Fill PricePrice at which a specific portion was processed.
Single Fill AmountAmount filled during a partial match.
FeeFee amount based on user level.
Role (Fee Type)Maker, Taker, Stop Maker, Stop Taker, etc.

Request Reflection History

Reflection history shows only requests that were actually processed through smart contracts, summarizing outcomes.
This allows users to track how their signed requests were reflected on-chain.

Note: Canceled requests are not shown in reflection history.

Results can be filtered by 1 day, 1 week, 1 month, 3 months, or a custom date range.

Reflection History Table

FieldDescription
Reflection TimeTime the request was processed on-chain (UTC).
PairCombination of the token and CROSS Coin.
Request TypeAcquisition or release.
Processed PricePrice at which the request was executed.
Processed AmountTotal amount successfully processed.
Reflected ValueFinal value of the processed request.
FeeFee amount applied based on user level.
Role (Fee Type)Maker, Taker, Stop Maker, Stop Taker, etc.

⚠️

The CROSSx app does not conduct or broker digital asset transactions, nor does it support in-app purchases or payments.
All asset-related requests are processed externally through smart contracts, initiated by the user's own signature and consent. The app functions solely as a wallet interface and signing tool.


© 2025 NEXUS Co., Ltd. All Rights Reserved.