OpenViSTAI · Agents · Blockchain · Crypto
Menu
Exchanges & Trading

Ocean.one

Ocean ONE is a decentralized exchange built on Mixin Network. It accepts Mixin Network assets as base currencies and documents XIN, Bitcoin and USDT-ERC20 as quote currencies. Orders are submitted through asset transfers carrying base64-encoded MessagePack instructions in Mixin snapshot memos; market snapshots and a WebSocket event stream expose trading data.

Independent OpenViST project profile, based on linked sources.

Ocean.one — OpenViST project profile in Exchanges & Trading.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Ocean ONE when the task involves trading Mixin Network assets against its documented quote currencies, or consuming its market snapshots and live order-book events.

Who it is for

  • Traders using Mixin Network assets who need to place or cancel exchange orders.
  • Developers building clients or analysis tools for Ocean ONE order books and trade events.

Documented uses

  • Place buy or sell orders by sending an asset transfer with an encoded order instruction.
  • Cancel an order by sending an instruction containing its order ID.
  • Retrieve ticker and order-book snapshots or subscribe to market events.
  • List a user's orders through the authenticated HTTP interface.
  • Inspect order and trade records encoded in snapshot memo fields.
Before you choose

Requirements & limits

  • Supported quote currencies are XIN, Bitcoin and USDT-ERC20; base currencies are Mixin Network assets.
  • Bid orders transfer quote funds to the matching engine, which matches all transferred funds; a limit bid can therefore fill more than the expected size.
  • The order-book HTTP response is a snapshot rather than a real-time feed; the WebSocket stream is the documented option for current events.
  • Order listing requires registering an ECDSA public key and authenticating with a JWT signed by its corresponding private key.
  • The public repository specifies Apache-2.0 and Go.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Subscribe to a market’s Ocean ONE order-book events

Receive order-book and trade-related events for a specified market through Ocean ONE’s WebSocket interface.

Before you start

  • A WebSocket client that can connect to wss://events.ocean.one and send and receive gzip-compressed messages.
  • A supported market represented by its base-asset and quote-asset IDs.

Steps

  1. Connect to wss://events.ocean.one.

  2. Send a gzip-compressed SUBSCRIBE_BOOK message with a unique id and the market ID in params.market.

  3. Read gzip-compressed server messages; the initial BOOK-T0 event contains the market’s full order book, and subsequent events may report order opens, matches, or cancellations.

  4. To stop receiving that market’s events, send a corresponding UNSUBSCRIBE_BOOK message.

Expected outcome

The client is subscribed to events for the selected market, beginning with a full order-book snapshot.

Guide limitations

  • The documentation does not specify a client library or provide runnable client code.
  • The order-open event is sent only for orders that are not filled immediately.
  • All messages sent and received must be gzip-compressed.
Source-based practical guide

Create a limit order by transferring an asset to Ocean ONE

Submit a buy or sell limit order using a transfer memo encoded as base64 MessagePack.

Before you start

  • A Mixin Network transfer capability and the asset to transfer.
  • A supported quote currency: Mixin XIN, Bitcoin BTC, or USDT-ERC20.
  • A way to encode the documented OrderAction fields as MessagePack and then base64.

Steps

  1. Choose a supported market and set the OrderAction type to L, the price, side (A for sell or B for buy), and asset ID as shown in the repository examples.

  2. For a sell, transfer the amount of the asset being sold; for a buy, transfer the desired amount of the quote asset to Ocean ONE.

  3. Attach the base64-encoded MessagePack OrderAction as the transfer memo.

  4. Set the transfer trace_id when possible; Ocean ONE uses it as the order ID.

Expected outcome

The transfer carries the information Ocean ONE documents for creating a limit order.

Guide limitations

  • The documentation does not provide a complete encoder or transfer-client implementation.
  • For bid orders, the matching engine matches all transferred quote funds; a limit bid may therefore fill a larger order size than expected.
  • The repository gives an example for XIN/BTC, not a tested procedure for every supported asset pair.
Evidence and transparency

Sources & review

Source record details
Source availability
Active
Sources checked
15 October 2026
Original website title
MixinNetwork/ocean.one · Official homepage title · retained in its source language