Waves.Exchange

Key facts about Waves.Exchange compiled from verified market data and CoinGecko's exchange registry. These metrics help you evaluate liquidity, regulatory footprint and operational maturity before connecting a portfolio.

Score de Confiance

0/10

Available in

1 jurisdictions

Trading incentives

Not offered

CCXT integration

Supported

wavesexchange

Waves.Exchange is wired into Mantapex through the CCXT integration layer, so importing balances and trade history into a read-only portfolio requires an API key and a secret that you generate inside your own Waves.Exchange account. Because Mantapex never custodies your funds, the keys you create should be scoped to read access only — withdrawal, transfer and trading permissions are unnecessary for portfolio tracking and should remain disabled.

Connection metadata is read directly from Mantapex's CCXT integration manifest — credential requirements reflect what Waves.Exchange itself exposes to read-only API consumers and may evolve as the venue updates its API.

Waves.Exchange operates as a custodial trading venue: when you fund an account, the deposited assets are held in wallets controlled by the exchange and credited to your balance as a book-entry until you withdraw them. That trade-off — convenience and order-book liquidity in exchange for counterparty risk — is the central design choice of every centralised exchange and is what makes platform-level security so important to evaluate. Year of incorporation is not published in our index for Waves.Exchange, so we cannot quote an exact operational tenure here — the venue's own About page is the authoritative reference.

Almost every major centralised exchange — including Waves.Exchange — operates under some form of KYC ("Know Your Customer") and AML ("Anti-Money-Laundering") obligations imposed by the jurisdiction it serves. Jurisdictional details for Waves.Exchange are not surfaced in our index, so consult the exchange's own Terms of Service and Help Centre for the canonical KYC matrix. Expect to provide a government-issued ID document and a recent proof-of-address at minimum; higher verification tiers may add liveness checks, source-of-funds questionnaires and accredited-investor confirmations.

For the specific case of connecting Waves.Exchange to Mantapex, the additional hardening layer is straightforward: generate a dedicated API key for read-only portfolio sync, label it clearly (for example "Mantapex read-only sync"), disable every permission except the minimum the exchange exposes for balance and trade-history queries, and store the secret in a password manager so you can rotate it on a schedule. If Waves.Exchange supports IP whitelisting and you connect from a stable address, restrict the key to that address. If you ever stop using Mantapex — or any other third-party dashboard — revoke the key on the exchange side rather than just deleting it from the dashboard, because the credential continues to authenticate against Waves.Exchange's API until Waves.Exchange itself invalidates it.

Security guidance on this page is generic exchange hardening that applies to every centralised crypto venue. For Waves.Exchange's exchange-specific policies — fund-segregation model, proof-of-reserves cadence, insurance coverage and incident-response history — the canonical references are Waves.Exchange's own Help Centre and any audit reports or attestations the venue publishes directly.

Connecting Waves.Exchange as a read-only portfolio source on Mantapex relies on the credentials defined by Waves.Exchange's own API. The matrix below mirrors exactly what the CCXT integration layer asks for — ticked rows mean the field is required to authenticate, untouched rows mean Waves.Exchange doesn't ask for that field at all.

In short, Waves.Exchange requires 2 credentials to authenticate API requests: Clé API and Secret API. All of these are generated from inside the exchange's own dashboard — Mantapex never asks you to share your account password or to set up an API key with withdrawal permissions enabled.

When you create the key on Waves.Exchange for use with Mantapex, restrict its permissions to read-only access (sometimes labelled "view", "read", "query" or "info"). Mantapex only needs to fetch balances, trade history and open positions. Withdrawal, trade-execution and transfer scopes should remain disabled. If Waves.Exchange offers a granular permission model, the safest combination is: enable "Read" or "View", disable "Trade" or "Spot trade", disable "Withdraw" or "Universal Transfer", and leave any margin / futures permission switched off unless you specifically want those positions visible inside your portfolio dashboard.

Some exchanges — Binance, OKX, Bybit, Bitget, KuCoin and several Asia-Pacific venues — offer an optional IP whitelist when you create the API key. Leaving the whitelist empty lets the key authenticate from any address, which is the simplest setup for use with a cloud-hosted dashboard such as Mantapex. If Waves.Exchange forces you to enter at least one IP and you don't have a static address, you can usually use a placeholder value the exchange recognises (for example "0.0.0.0/0" or the wildcard option) — consult Waves.Exchange's API documentation before relying on that workaround. Either way, the credentials remain in a read-only scope and cannot be used to move funds off the venue.

Credential schema sourced directly from the CCXT integration manifest used by Mantapex. Waves.Exchange may rotate or extend its API in the future — if the exchange asks for a credential not listed here when you create the key, you can safely ignore it for the purpose of a read-only Mantapex import.

The links below point to first-party Waves.Exchange properties. We track them so you can verify announcements, support channels and operator-published policies directly at the source rather than from third-party copies. External destinations open in a new tab and are marked nofollow per our resource-link policy.

• Site officiel de Waves.Exchange

  wx.network

Meilleurs exchanges par score de confiance

Binance

Cayman IslandsConfiance 10.0/10234.6K BTC

Bybit

British Virgin IslandsConfiance 10.0/1049.6K BTC

Gate.io

PanamaConfiance 10.0/1047.4K BTC

Coinbase

United StatesConfiance 10.0/1043.7K BTC

Coinbase

United StatesConfiance 10.0/1043.7K BTC

Bitget

SeychellesConfiance 10.0/1035.4K BTC

Kraken

United StatesConfiance 10.0/1024.5K BTC

MEXC

SeychellesConfiance 9.0/1070.2K BTC

Peer sets sourced from CoinGecko's trust-score ranking and CCXT's exchange manifest. Inclusion here is not an endorsement — it simply means Mantapex tracks the venue with current trust / volume data.