Bluemove use cases: tracing trades to on-chain results
BlueMove is an NFT marketplace project for Aptos and Sui, with a separate Sui token exchange. Checking an NFT trade means matching the recorded execution result to the exact asset and its payment movements on the relevant network. BlueMove's Sui DEX carries a suspension notice, so its swap and liquidity interfaces do not establish that those services have resumed.
Parameters that determine what a record means
| Parameter | Value or behavior | Use in checking an outcome | Applicable condition |
|---|---|---|---|
| Marketplace networks | Aptos and Sui | Locates the NFT and its trade within the correct blockchain. | Marketplace support for both chains does not itself establish an NFT transfer route between them. |
| Sui NFT identity |
A unique object
ID
|
Identifies the particular NFT involved. | The object model applies to Sui; a collection name or image is not the object's identifier. |
| Sui NFT ownership | Ownership recorded for each object | Connects an NFT transfer with a change in ownership. | Historical execution and present ownership answer different questions. |
| Sui NFT transferability | Custom transfer logic is possible. | Determines the conditions for moving an NFT. | Some NFTs can be non-transferable; possession alone does not establish unrestricted resale. |
| Bulk NFT operations | Bulk buying and bulk listing | Separates purchasing items from offering them for sale. | BlueMove described these as live in PancakeSwap's AMA published on February 9, 2023; that statement does not establish present availability. |
| Sui DEX availability | Temporary suspension announced | Limits plans for token swaps and liquidity deposits. | The Security Incident Notice announces suspension during an investigation, without confirming a resumption. |
Finding an NFT and establishing ownership
Collection discovery helps a collector identify items to investigate. A settlement check needs the specific asset and network behind the listing. An Aptos listing calls for Aptos asset and transaction records. Sui's NFT ownership model gives each NFT an identity and records its owner, while its metadata can include a name, description, and media reference. Those descriptive fields serve a different purpose from the object's unique identifier.
Transfer permissions also affect the available action. Sui allows custom transfer policies and non-transferable NFTs. An ownership record therefore needs to be read alongside the rules for that NFT before it can support a conclusion about resale or transfer.
Distinguishing a listing from a completed sale
A listing offers an NFT for sale; completion of the listing operation does not establish that a buyer acquired it. Bulk listing has the same distinction at the level of each item. For a completed purchase, the relevant evidence is successful execution of the sale and its resulting NFT and payment changes. Signing or submitting an action alone does not establish that outcome.
A transaction identifier provides a way to locate a record. The record's execution status and effects establish what happened. For a past trade, inspect the ownership change produced by that transaction: the NFT's current owner may reflect a later transfer. A blockchain record is therefore the appropriate view for settlement questions, while the marketplace view serves collection browsing and sale discovery.
Separating sale proceeds from MOVE staking outcomes
Sale proceeds and staking rewards arise from different activities. In BlueMove's February 9, 2023 AMA, the team described a staking design in which locked MOVE generated iMOVE according to the amount and staking period. Rewards depended on iMOVE holdings, which decreased monthly to zero over the staking period; iMOVE was described as non-tradable.
Under that design, the locked MOVE principal was due back after the staking period ended. Receipt of rewards and return of principal were separate outcomes, each requiring its own payment or release record. The historical design does not establish current pool availability, reward rates, or claim conditions.
Interpreting Sui DEX activity during suspension
BlueMove's token exchange and liquidity pools concern fungible tokens, separate from its NFT marketplace trades. A swap outcome concerns the tokens exchanged; a liquidity operation concerns the relevant pool position. Neither should be inferred from an NFT ownership change.
The DEX Security Incident Notice states that the protocol was temporarily suspended while the incident was investigated. Confirmation that the affected activity has resumed is a prerequisite to treating it as an available route for a new swap or liquidity deposit. Historical activity and interface controls do not provide that confirmation. The notice concerns the DEX and does not establish the operating status of every NFT marketplace function.
Checking a compensation outcome
BlueMove's notice announces a compensation process after the attacker's response window closed. Its updated wording says that the claimant amounts replace figures previously displayed. An amount allocated to a claimant and a completed payment are separate states: individual receipt requires a completed transfer with the intended recipient, asset, and amount. The compensation announcement alone does not establish that any particular wallet was paid.