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.
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:
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.
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.
zerohash is pleased to announce the addition of two new assets, TRON (TRX) and Tether on TRON (USDT.TRX), expanding your trading and platform capabilities.
Asset Name
Symbol
Notes
TRON
TRX
Not enabled in NY.
Tether on TRON
USDT.TRX
Not available on CLOB; Not enabled in NY.
Availability
Asset
RFQ
CLOB
Fund
Payments
TRX
✔️
✔️
✔️
✔️
USDT.TRX
✔️
❌
✔️
✔️
Environments: TRX is live in both CERT and PROD environments. USDT.TRX is only live in PROD.
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: