Waves.Exchange 交易所 — 信任评分 0/10

Waves.Exchange

CoinGecko·N/A rank·0 BTC vol 24h·N/A

连接 Waves.Exchange

登录以连接您的交易所并自动追踪您的投资组合

Waves.Exchange at a Glance

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.

信任评分: 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.

兼容 CCXT 需要 API 密钥需要 API 密钥串提供设置指南

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.

Getting Started with Waves.Exchange

Log In to Your Waves Exchange Account

Navigate to Waves Exchange and sign in with your credentials.

Obtain an Access Token

Waves Exchange uses OAuth2 for authentication.
You can obtain an access token by using the POST /v1/oauth2/token endpoint.
This token allows your application to make requests on behalf of your account.

Use the Matcher API for Market Data

The Matcher API provides endpoints to access market data, such as order books and trade history.
For example, you can use GET /matcher/orderbook/{amountAsset}/{priceAsset} to retrieve the order book for a specific trading pair.

Access Account Information

With the access token, you can retrieve account-related information, such as balances and transaction history.
Ensure that your application securely stores and manages the access token to prevent unauthorized access.

LEARN MORE

Required Credentials: API 密钥私密密钥

Waves.Exchange 的账户、托管与安全

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.

如何安全地连接任何交易所

Enable two-factor authentication on the exchange account itself before generating any API keys. The strongest options are hardware security keys (FIDO2 / WebAuthn devices such as YubiKey or Solo) where supported, followed by an authenticator app on a dedicated device (Aegis, Raivo, 1Password, or Google Authenticator); SMS-based 2FA is the weakest common method because of SIM-swap risk. Keep the recovery phrase or backup codes in offline cold storage rather than the same password manager you sign in with. Where the venue offers a withdrawal-address whitelist, turn it on: it shrinks the blast radius of a stolen key or hijacked session because funds can only leave to a pre-approved address after a cool-down. Pair that with anti-phishing codes, a dedicated email account, and alerts for new logins, withdrawal requests and API-key creation — most exchange-related losses originate from compromised individual accounts, not platform-wide breaches.

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.

Waves.Exchange 的 API 访问详情

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.

API 密钥

Public identifier that pairs your read-only access with your exchange account.

API 密钥串

Private signing string used to authenticate each request — never share it.

API 口令

Additional passphrase set when the key is created (KuCoin, OKX-style models).

账户 UID

Numeric account identifier that some venues require alongside the API key.

子账户 ID

Used when the venue scopes API access to a specific sub-account.

登录名

A separate username distinct from email, used by a small number of CCXT-supported venues.

TOTP / 2FA 密钥

Time-based one-time-password seed for endpoints that demand a fresh 2FA code.

钱包私钥

Self-custody signing key — required only by DEX / on-chain integrations.

钱包地址

On-chain address tied to the private key for DEX-style integrations.

Bearer 令牌

OAuth-style bearer token, occasionally used in place of an HMAC API key pair.

In short, Waves.Exchange requires 2 credentials to authenticate API requests: API 密钥 and 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.

Waves.Exchange 的官方资源与社区

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.