Release Details

Release Date: February 18th, 2026

Release Type

Informational, no action required from platforms

Summary

zerohash has launched its new Recovery SDK - an embeddable component that empowers end users to self-serve recovery withdrawals. Platforms can integrate this SDK with minimal dev effort and by following the full, end-to-end integration guide

Use Case

For platforms using the Auth Standalone product, if transfers to non-Auth destinations are restricted, users can be seamlessly routed into the Recovery flow.

Powered by the Recovery SDK, this embedded experience allows users to complete a compliant self-serve recovery withdrawal, without requiring manual support intervention.

Please reach out to your zerohash contact if you have any questions.

Relevant Documentation

• Recovery SDK integration guide
• Auth Validate
• Auth - Home Page

Release Details

Release Date: February 19, 2026

Release Type

Informational, no action required from platforms.

Summary

This release marks the official expansion of our Central Limit Order Book (CLOB) functionality into the European (EU) region. This infrastructure update allows institutional brokers and European participants to trade USD-denominated crypto pairs with optimized liquidity routing and a new flexible funding architecture.

To accommodate various institutional needs, we have introduced a dual-model system for the EU:

• Float Model: Mirrors the existing U.S. framework where trades settle directly against available balances.
• Order-Based Suspense Model (New): Designed specifically for Institutional Brokers (IBs). This enables suspense-based trade orchestration and post-trade reconciliation, allowing for more complex settlement workflows.

Relevant Documentation

For details on CLOB integration and supported instruments, please use the links below.

CLOB Documentation

• CLOB API Docs
• CLOB Account Creation

Supported Instruments

• CLOB Instrument List

FIX Order Gateway

zerohash is happy to announce a new optional feature to allow CLOB participants to reliably identify NewOrderSingle and OrderCancelReplaceRequest rejections stemming from insufficient balance on the given account.

NewOrderSingles

If enabled, NewOrderSingles rejected due to insufficient buying power now have an OrdRejReason (Tag <103>) of "Insufficient credit limit" with value 25, instead of “Exchange option” with the value 0.

OrderCancelReplaceRequest

Similarly, if enabled, OrderCancelReplaceRequests rejected due to insufficient buying power now have a CxlRejReason (Tag <102>) of “Insufficient credit limit” with value 25, instead of “Exchange option” with value of 2.

Release Details

Release Date: January 8, 2026

Release Type

Informational, no action required from platforms

Summary

zerohash is pleased to announce the addition of the following new asset on CLOB, expanding your trading and platform capabilities:

Availability

• Environments: Asset is live in both CERT and PROD environments.
• Geographic Restrictions: Asset is not enabled in New York at this time.
• Effective Date: Immediately available using the symbols listed above.

CLOB Endpoints Impacted

The following executable endpoints now support the above asset:

• Create account: POST /clob/accounts
• Get accounts: GET /clob/accounts
• Update CLOB account: PATCH /clob/accounts
• Search orders: POST /orders/v1/search_orders
• Get open orders: POST /orders/v1/get_open_orders
• Search executions: POST /orders/v1/search_executions
• Create order subscriptions: POST /orders/v1/create_order_subscription
• Submit order: POST /orders/v1/insert_order
• Cancel order: POST /orders/v1/cancel_order
• Market data subscription: POST /orders/v1/create_market_data_subscription
• List instruments: POST /orders/v1/list_instruments
• Trade stats: POST /orders/v1/get_trade_stats

Relevant Documentation

For a full list of supported assets and instruments, please use the links below.

Supported Assets

• Production
• Certification

Supported Instruments

• Production
• Certification

Release Details

Release Date: December 31, 2025

Release Type

Informational, no action required from platforms

Summary

zerohash is pleased to announce the addition of the following new assets, expanding your trading and platform capabilities:

Availability

• Environments: Both assets are live in both CERT and PROD environments.
• Geographic Restrictions: Both assets are not enabled in New York at this time.
• Effective Date: Immediately available using the symbols listed above.

RFQ Endpoints Impacted

The following executable endpoints now support the above assets:

Buy/Sell

• Get quote: POST /liquidity/rfq
• Execute quote: POST /liquidity/execute

Convert Withdraw

• Get quote: POST /convert_withdraw/rfq
• Execute quote: POST /convert_withdraw/execute

Deposit

• Create deposit address: POST /deposits/digital_asset_address

Withdraw

• Create withdrawal request: POST /withdrawals/requests

Fund

• [SDK support]
• Get quote: POST /fund/rfq
• Get fund transactions: GET /fund/transactions

Relevant Documentation

For a full list of supported assets and instruments, please use the links below.

Supported Assets

• Production
• Certification

Supported Instruments

• Production
• Certification

Release Details

Release Date: December 22, 2025

Release Type

Informational, no action required from platforms

Summary

zerohash is pleased to announce enablement in NY for the following asset, expanding your trading and platform capabilities.

Availability

• Environments: Asset is live in both CERT and PROD environments.
• Effective Date: Immediately available using the symbols listed above.

RFQ Endpoints Impacted

The following executable endpoints now support the above assets:

Buy/Sell

• Get quote: POST /liquidity/rfq
• Execute quote: POST /liquidity/execute

Convert Withdraw

• Get quote: POST /convert_withdraw/rfq
• Execute quote: POST /convert_withdraw/execute

Deposit

• Create deposit address: POST /deposits/digital_asset_address

Withdraw

• Create withdrawal request: POST /withdrawals/requests

Fund

• [SDK support]
• Get quote: POST /fund/rfq
• Get fund transactions: GET /fund/transactions

Relevant Documentation

For a full list of supported assets and instruments, please use the links below.

Supported Assets

• Production
• Certification

Supported Instruments

• Production
• Certification

Release Details

Release Date: December 22, 2025

Release Type

Informational, no action required from platforms

Summary

zerohash is pleased to announce the addition of two new assets, expanding your trading and platform capabilities.

❗️

Please note these assets use non-standard precision. Custody precision is 18 for both USDC.BSC and USDT.BSC.

Availability

• Environments: Both assets are live in both CERT and PROD environments.
• Geographic Restrictions: Both assets are not enabled in New York at this time.
• Effective Date: Immediately available using the symbols listed above.

RFQ Endpoints Impacted

The following executable endpoints now support the above assets:

Buy/Sell

• Get quote: POST /liquidity/rfq
• Execute quote: POST /liquidity/execute

Convert Withdraw

• Get quote: POST /convert_withdraw/rfq
• Execute quote: POST /convert_withdraw/execute

Deposit

• Create deposit address: POST /deposits/digital_asset_address

Withdraw

• Create withdrawal request: POST /withdrawals/requests

Fund

• [SDK support]
• Get quote: POST /fund/rfq
• Get fund transactions: GET /fund/transactions

Relevant Documentation

For a full list of supported assets and instruments, please use the links below.

Supported Assets

• Production
• Certification

Supported Instruments

• Production
• Certification

Overview

zerohash currently acts as the Central Counter Party (CCP) for trades that match on the Central Limit Order Book. We are transitioning away from acting as CCP and trades will now be directly booked against the counterparty of the trade which will remain anonymous.

As part of this transition, we are updating the CLOB trade-booking structure such that the counterparty on each trade will appear as an anonymous participant, rather than the zerohash participant's inventory account.

Non Material Update to GET /trades Endpoint

Scenario 1: Customer Fills Against External Party

The shape of the parties attribute will not change, however, the participant_code field will now always display Anonymous. The full payload remains the same, as seen below:

{
    "parties": [
        {
            "settling": true,
            "participant_code": "CUST01",
            "side": "buy",
            "asset": "BTC",
            "amount": "0.0001",
            "liquidity_indicator": null,
            "execution_id": "execution-id",
            "order_id": "order-id",
            "obligations_outstanding_timestamp": 1762201548140,
            "current_obligations_met_timestamp": null,
            "settlement_state": "settled",
            "client_order_id": "client-order-id",
            "collateral_percentage": null,
            "account_label": "label",
            "account_profile": "prefunded",
            "trader": "PLAT01",
            "commission": "0.11",
            "commission_asset": "USD"
        },
        {
            "participant_code": "Anonymous",
            "side": "sell",
            "asset": "USD",
            "amount": "10.67",
            "liquidity_indicator": null
        }
    ]
}

Scenario 2: Customer Fills Against Internal Party

Where two parties of the same platform execute against one another, the two parties will show in the same parties object. In the sample response below, execution_id should be used for either party to identify the trade.

{
  "parties": [
    {
      "settling": true,
      "participant_code": "CUST01",
      "side": "sell",
      "asset": "USD",
      "amount": "10",
      "liquidity_indicator": null,
      "execution_id": "6XRHR4TG003Y",
      "order_id": "6WW50NV1862G",
      "obligations_outstanding_timestamp": 1765456952163,
      "current_obligations_met_timestamp": null,
      "settlement_state": "obligations_outstanding",
      "client_order_id": "1167639010536696210000",
      "collateral_percentage": null,
      "account_label": "0ca185ce-392b-4814-9eae-add8e629bdd4",
      "account_profile": "nonprefunded",
      "trader": "CUST01",
      "commission": "0",
      "commission_asset": "USD"
    },
    {
      "settling": true,
      "participant_code": "CUST02",
      "side": "buy",
      "asset": "ETH",
      "amount": "0.0001",
      "liquidity_indicator": null,
      "execution_id": "6XRHR4TG203Y",
      "order_id": "6WW50NV1662G",
      "obligations_outstanding_timestamp": 1765456952163,
      "current_obligations_met_timestamp": null,
      "settlement_state": "obligations_outstanding",
      "client_order_id": "1166639010536259566000",
      "collateral_percentage": null,
      "account_label": "dc087f25-0bd3-4b3d-9f40-b36607550149",
      "account_profile": "nonprefunded",
      "trader": "CUST02",
      "commission": "0",
      "commission_asset": "USD"
    }

Release Details

Release Date: December 9, 2025

Release Type

Informational, no action required from platforms

Summary

zerohash is pleased to announce the addition of three new assets, expanding your trading and platform capabilities.

These assets are now available to buy, sell, deposit, withdraw and Fund:

Availability

• Environments: All assets are live in both CERT and PROD environments.
• Geographic Restrictions: All assets are not enabled in New York at this time.
• Effective Date: Immediately available using the symbols listed above.

RFQ Endpoints Impacted

The following executable endpoints now support the above assets:

Buy/Sell

• Get quote: GET /liquidity/rfq
• Get quote: POST /liquidity/rfq
• Execute quote: POST /liquidity/execute

Convert Withdraw

• Get quote: POST /convert_withdraw/rfq
• Execute quote: POST /convert_withdraw/execute

Deposit

• Create deposit address: POST /deposits/digital_asset_address

Withdraw

• Create withdrawal request: POST /withdrawals/requests

Fund

• [SDK support]
• Get quote: POST /fund/rfq
• Get fund transactions: GET /fund/transactions

Relevant Documentation

For a full list of supported assets and instruments, please use the links below.

Supported Assets

• Production
• Certification

Supported Instruments

• Production
• Certification

Release Details

Release Date: December 3, 2025

Summary

zerohash now supports a formal Customer Accounts model, enabling platforms to create and manage multi-participant CLOB trading accounts, including custodial (UTMA), trust, joint (JTIC / JTWROS), and accounts with an added financial advisor.

New customer-account identifiers use the ZRN schema zrn:zh:<geo>:accounts:customer:<id>
Legacy unqualified IDs continue to be supported for full backward compatibility.

Multi-tenant accounts now include configurable tenant roles (primary / secondary participants) and authorization levels (full-trading, limited-trading, or view-only). Platforms may also attach a financial advisor with controlled access.

No Action for Platforms

No mandatory migration. Existing integrations keep working. But you may now support joint, custodial, or trust-based accounts by adopting the new account-type schema when calling POST /accounts.

Related Endpoints

• Create customer account: POST /accounts
• Get account details: GET /accounts/{zrn}/details
• Update customer account: PATCH /accounts/{zrn}
• Add tenant to customer account: POST /accounts/{zrn}/tenants
• Remove tenant from customer account: DELETE /accounts/{zrn}/tenants/{tenant}
• Add advisor to customer account: POST /accounts/{zrn}/advisors
• Remove advisor from customer account: DELETE /accounts/{zrn}/advisors

For more information and example use cases, see our Customer Accounts Guide