Release Date

Thursday, March 21, 2024

Release Type

Action Required – Please recreate wallets and deposit addresses on CERT now that the Goerli ETH testnet is changed to Sepolia ETH and balances may have reset to 0. PROD is not impacted.

Summary

Zero Hash has updated the CERT environment to use the Sepolia ETH testnet and removed Goerli support. Balances for ETH and ERC20 tokens in CERT will reset to zero. Below are some provided faucets to top up balances of Sepolia ETH and some tokens.

Impacted Assets

Please refer to the Assets FAQ to see the latest assets with CERT support. Some ERC20 tokens that previously had older testnet support now have CERT support, while others do not. Balances for ETH and ERC20 tokens will reset because they will now point to a different test network.

Removed CERT testnet support:

• BAT.ETH
• BUSD.ETH
• ZUSD.ETH
• GYEN.ETH
• GRT.ETH
• MKR.ETH
• ZRX.ETH

The Assets FAQ will be updated if additional testnet contracts for ERC20 tokens are found as they are deployed to Sepolia.

List of ERC20 Token Contracts and Faucets

Sepolia ETH Faucets:

• Alchemy Faucet
• Infura Faucet
• QuickNode Faucet
• Sepolia Faucet
• Chainstack Faucet

ERC20 Sepolia Faucets:

• MATIC.ETH
• USDT.ETH

CERT Sepolia Token Contracts:

• AAVE.ETH: 0x88541670E55cC00bEEFD87eB59EDd1b7C511AC9a
• LINK.ETH: 0x779877A7B0D9E8603169DdbD7836e478b4624789
• DAI.ETH: 0xFF34B3d4Aee8ddCd6F9AFFFB6Fe49bD371b8a357
• KNC.ETH: 0xD701e3e1A327d13564ba072e6C0806129Fea4671
• MATIC.ETH: 0x3fd0A53F4Bf853985a95F4Eb3F9C9FDE1F8e2b53
• SHIB.ETH: 0x9f885f12cb3179817324839a035288b0d74d24fa
• UNI.ETH: 0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984
• USDC.ARBITRUM: 0x75faf114eafb1BDbe2F0316DF893fd58CE46AA4d
• USDC.BASE: 0x036CbD53842c5426634e7929541eC2318f3dCF7e
• USDC.ETH: 0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238
• USDC.OPTIMISM: 0x5fd84259d66Cd46123540766Be93DFE6D43130D7
• USDC.Polygon: 0x41e94eb019c0762f9bfcf9fb1e58725bfb0e7582
• USDP.ETH: 0x513421d7fb6A74AE51f3812826Aa2Db99a68F2C9
• USDT.ETH: 0xaA8E23Fb1079EA71e0a56F48a2aA51851D8433D0
• WBTC.ETH: 0x29f2D40B0605204364af54EC677bD022dA425d03
• WETH.ETH: 0xfFf9976782d46CC05630D1f6eBAb18b2324d6B14

Related Links

• Zero Hash Supported Assets
• Ethereum Foundation Dencun blog post
• Sepolia testnet github

Release Date

Friday, March 15, 2024

Release Type

Action Required – Your platform will be required to recreate wallets and deposit addresses on CERT after the Goerli ETH testnet is changed to Sepolia ETH. PROD is not impacted.

Summary

The Ethereum Dencun update went live on March 13, 2024, marking the beginning of the one-month countdown to the sunset of the Goerli ETH Testnet. Some tools have already ended support for the network, such as certain block explorers.

The Ethereum Foundation recommends projects migrate to the Sepolia test network for most use-cases. Zero Hash plans to point the CERT environment to this test network on Thursday, March 21, 2024. PROD is not impacted and will be available during this time.

Sepolia Testnet

Ethereum has moved to a model where an older testnet will sunset and a new one will be added every two years. Goerli is being sunsetted in April 2024, and Sepolia is now the recommended ETH testnet, which itself will sunset sometime in 2026. Holesky is a longer-term testnet planned to sunset in 2028.

Despite the shorter lifespan, Zero Hash will move to Sepolia to support a majority of testnet assets, including Circle’s USDC, which are only supported on Sepolia. Options are also being considered to support multiple testnets simultaneously for future transitions.

Cutover Schedule

Zero Hash will open a maintenance window on Thursday, March 21st at 10am ET for CERT to have approximately one hour of downtime. After the maintenance window, using ETH blockchain assets in the CERT environment will point to the Sepolia network.

After the cutover, no prior Goerli balances, transactions, or deposit addresses will be available through Zero Hash systems.

Impacted Assets

Any tokens on the ETH blockchain, including Level 2 Ethereum chains, will be impacted. This change does not impact PROD, and the maintenance window will only apply to CERT. Impacted CERT assets include:

• ETH base token
• ERC20 Assets
  • Assets ending in .ETH such as USDC.ETH and ENJ.ETH
• Ethereum Level 2 networks like ETH.Arbitrum

Preparation

You should prepare a plan to recreate deposit addresses for CERT ETH/ERC20/ETH L2 wallets once the CERT environment is brought online after the maintenance window. Sepolia faucets can be used to add free testnet funds to those wallet addresses.

Endpoints Impacted

Any CERT endpoint where a digital asset symbol like “ETH” or “USDC.ETH” is input will be impacted (for example /withdrawals/, /convert_withdraw/, and /deposits/digital_asset_addresses). Prior Goerli balances will not carry over, so new deposit addresses will need to be created, and Sepolia faucets may need to be used to replenish the testnet assets to those wallets.

Related Links

• Zero Hash Supported Assets
• Ethereum Foundation Dencun blog post
• Sepolia testnet github

Release Details

• Release Date: Feb 12, 2024

Release Type

Informational – Optional action from platforms

Summary

Zero Hash is pleased to announce adding support for the Aptos Blockchain including the ability to buy, sell, deposit, and withdraw the native APT token.

If you would like to enable this token on your platform, you can begin submitting your existing API requests using the Aptos symbol found in our Assets page in the supported environments.

Action Required

No action required.

Endpoints Impacted

There are no changes to existing endpoints as a result of this launch. Use the new APT symbol to create or view deposit addresses, initiate a withdrawal, request a quote, or execute a trade. Feel free to reach out to your client team for assistance.

Relevant Documentation

• Zero Hash Assets FAQ

Release Details

• Release Date: Dec 15, 2023
  • Updated 4/15/24 for the addition of RFQ support (see notes in Summary and Endpoints sections below)
• Release Type: Informational – Optional action from platforms.

Summary

Zero Hash has released trading and custody support for Circle's Euro-backed stablecoin: EURC. This support will be initially provided on the Stellar blockchain using the EURC.XLM symbol.

Update 4/15/24: RFQ support has been added for this asset available via the RFQ endpoints for buys and sells. A EUR account is required for buys and sells due to the trading pair denomination in Euros.

Our asset support page has been updated to reflect this.

Action Required

No action required.

Endpoints Impacted

• POST /trades
• GET /deposits
• GET /deposits/digital_asset_addresses
• POST /deposits/digital_asset_addresses
• GET /withdrawals/requests
• GET /withdrawals/requests/:id
• POST /withdrawals/requests
• DELETE /withdrawals/requests/:id
• GET /withdrawals/digital_asset_addresses
• GET /withdrawals/locked_network_fee
• POST /withdrawals/execute

Updated 4/15/24

• GET /convert_withdraw/rfq
• POST /convert_withdraw/rfq
• GET /liquidity/rfq

Release Details

• Release Date: Dec 5, 2023
• Release Type: Informational – No immediate action required from platforms

Summary

The Zero Hash compliance team consistently monitors network risk. At times, platform customers may undergo enhanced due diligence (EDD) to authenticate the identity and/or transactional activity of the customer. Platforms may be asked to submit additional details about the end customer to Zero Hash for review via PATCH /participants/customers/:participantCode.

Zero Hash has added new fields to the participants database to accommodate EDD instances.

Action Required

No immediate action required from platforms.

Zero Hash contacts platforms directly if EDD information is required for submission.

Endpoints Impacted

• PATCH /participants/customers/:participantCode – If EDD information is requested by the Zero Hash compliance team, it must be submitted to the PATCH endpoint. Note: You must also include <platform_updated_at> as per the PATCH endpoint guidelines.

• POST /participants/customers/new – Platforms are not yet expected to pass EDD information when creating a participant; however as these fields (employment_status, industry, source_of_funds) are now a part of the Zero Hash participants database, platforms can expect to see the new fields included in the POST response with a null or unknown designation.

Please see the PATCH documentation for implementation guidelines.

Related Documentation

Release notes for the PATCH endpoint here.

Release Details

• Release Date: Dec 5, 2023
• Release Type: Informational – Optional action from platforms

Summary

We have released the Transaction Fees feature to Production. Platforms configured to use this feature of the Convert Withdraw product will be able to specify the fees that were assessed on the order.

NOTE:

• This feature is only offered to Platforms who use Zero Hash Liquidity Services. A future release will be made to open this up to our Trade Settlement (/trades) product.
• We are adding a new endpoint called POST /convert_withdraw/rfq. It functions the exact same as the GET /convert_withdraw/rfq version. Both of them will continue to be supported indefinitely until stated otherwise. See 1-pager below, section “Flow” to see an example.
• See dedicated 1-pager here for technical details, use cases, and more.

Action Required

If interested in the feature, please reach out to your Zero Hash representative.

Endpoints Impacted

• POST /convert_withdraw/rfq
• GET /trades
• GET /trade/:trade_id
• GET /accounts/:account_id/movements

Release Details

• Release Date: Dec 5, 2023
• Release Type: Informational – Optional action from platforms

Summary

We have released the Custom Spreads feature to Production. Platforms configured to use this feature of the Convert Withdraw product will be able to, on a per order basis, define the spread amount themselves programmatically. Previously, the spread configuration was only editable manually by a Zero Hash employee upon request.

NOTE:

• This feature is only offered to Platforms who use Zero Hash Liquidity Services
• We are adding a new endpoint called POST /convert_withdraw/rfq. It functions the exact same as the GET /convert_withdraw/rfq version. Both of them will continue to be supported indefinitely until stated otherwise. See 1-pager below, section “Flow” to see an example.
• With this release, we also began exposing 2 new fields on the GET /trades and trades/:trade_id:
  • spread_notional: notional value of the spread applied, expressed in terms of the quoted_currency
  • spread_bps: basis point value of the spread applied
    These fields are not only useful for Platforms who use the Convert Withdraw product, but any Zero Hash Liquidity Services products (excluding the Central Limit Order Book). For revenue reconciliation, Platforms can use these fields to determine the monthly amount of spread collected.

Action Required

If interested in the feature, please reach out to your Zero Hash representative.

Endpoints Impacted

• POST /convert_withdraw/rfq
• GET /convert_withdraw/rfq
• GET /trades
• GET /trades/:trade_id

Release Details

• Release Date: Nov 27th, 2023
• Release Type: Informational – Optional action from platforms.

Summary

Zero Hash is enforcing Maximum and Minimum thresholds on our RFQ system. We have set our Maximum limit of 500,000 USD and a Minimum of 0.01 USD per quote. We have updated our error responses returned to Platforms if they are in breach of our Maximum or Minimum thresholds. If a Platform wishes to adjust this maximum, please email [email protected].

Action Required

Platforms must be prepared to handle the new status 400 error that is returned when a RFQ Maximum or Minimum has been breached.

Sample Response - Maximum limit breached

{
    "errors": [
        "unable to obtain quote, above maximum quote notional"
    ]
}

 

Sample Response - Minimum limit breached

{
    "errors": [
        "unable to obtain quote, below minimum quote notional"
    ]
}

Endpoints Impacted

• Liquidity
  • GET /liquidity/rfq
  • GET /convert_withdraw/rfq
• POST /rewards
• POST /awards

Release Details

• Release Date: Nov 17th, 2023
• Release Type: Actionable – Platforms must share the configs to start using this feature.

Summary

It is possible to charge end customers fees to withdraw assets from their platforms to external wallets similar to traditional finance fees (wire fees, account closure fees, etc.). This is a separate configuration than the one used to manage custom spreads on liquidity quotes.

If enabled, a fee will be collected on every withdrawal execution and ledgered accordingly. The current feature works in NETTED (fixed sending amount) and ADDITIVE (fixed receiving amount) settings. Fee can be set in either a flat amount or spread (or both) per asset.

Action Required

To begin using this functionality, the following platform configurations must be set per ASSET with your Zero Hash team:

• "withdrawal_spread_type": 'NETTED|ADDITIVE'
  • Netted deducts a fixed amount from the participant and any fees will be deducted from the quantity that is sent
  • Additive deducts the sending quantity in addition to any fees, so that the sending quantity is received by the destination wallet
• "withdrawal_spread_fixed_fee": '0.000015'(This is defined in base currency and NOT in atomic units. So ETH and not WEI)
• "withdrawal_spread_percentage_fee": '3'(This is in absolute % so here 3 means 3%)
• "withdrawal_spread_platform_revenue_percentage": '60'(This is the revenue % based on agreement. In this scenario, the collected withdrawal fee account 60% to platform and 40% to ZH accounts)

Sample API Payload

{
  "message": {
    "request_id": "6a8c267b-2f9e-4cb1-a8ee-901311891722",
    "withdrawal_quote_id": "129f5825-1a1a-40b6-8770-fcf102125e2b",
    "withdrawal_request_id": "e4b1135a-a88f-45c0-93c0-eef5f7e62729",
    "participant_code": "1NY182",
    "account_group": "JB41VN",
    "account_label": "general",
    "withdrawal_address": "0xD4eD0e192c2DBb5594eDA4601f9403a8af64e7cF",
    "destination_tag": "",
    "no_destination_tag": false,
    "asset": "ETH",
    "amount": "0.01",
    "amount_notional": "20.52",
    "network_fee": "0.000031500000252",
    "network_fee_notional": "0.06",
    "on_chain_status": "PENDING",
    "withdrawal_fee": "0.0001"
  }
}

Endpoints Impacted

All impacted endpoints. Include code samples or json schema for publicly available changes.

• POST /withdrawals/requests
• POST /withdrawals/execute
• GET /withdrawals/requests
• GET /withdrawals/requests/:id
• GET /withdrawals/locked_network_fee

More info under each endpoint in our API documentation.

Related Documentation

Please see the Withdrawal Spreads Guide for the most up-to-date information.

Release date

• Sep 21, 2023

Release Type

• Information - Optional action from platforms.

Summary

General

Platforms using the Convert Withdraw product can now specify whether or not the network fee notional amount is included in the total notional amount or excluded. Examples:

• Fee inclusive: A platform requests a quote by notional for an amount of 100 USD and the breakdown is (assuming a $2 network fee):
  • asset_cost_notional: $98
  • network_fee_notional: $2
  • total_notional: $100
• Fee exclusive: A platform requests a quote by notional for an amount of 100 USD and the breakdown is (assuming a $2 network fee):
  • asset_cost_notional: $100
  • network_fee_notional: $2
  • total_notional: $102

Action required

There is a new optional Boolean query parameter called fee_inclusive that Platforms can use on the GET /convert_withdraw/rfq endpoint. A value of true means that the network fee is inclusive. A value of false or omitting this query parameter implies a fee exclusive-type call.

Endpoints impacted

• GET /convert_withdraw/rfq