بحث موثق بالمصادر: Binance / Kraken / Coinbase

Verified source facts

1. Binance Capital API deposit address response includes an address field and a tag field, and its coin metadata can include networkList and withdrawTag. 2. Binance coin metadata includes network fields such as depositEnable, withdrawEnable, addressRegex, memoRegex and minConfirm. 3. Kraken warns users to select the correct asset and network and says withdrawing from the wrong network can result in loss of funds. 4. Coinbase missing-transaction support asks users to verify that the transaction was sent on the right network for the asset. 5. Coinbase send guidance separates destination address, network choice and preview confirmation before sending crypto.

Comparison at a glance

1. Control test: Asset symbol

A trading-control disclosure is meaningful only when converted into a testable rule. For asset symbol, inspect coin or token selected by the sender. Use a sandbox, non-production context, or the smallest reversible test available, then match the asset at both ends. Capture configuration and event evidence without recording credentials, and verify the documented cancel, reject, decrement, or history behavior.

Model the failure path, not just the setup path. Ask which strategy owns the maker and taker orders, which account boundary the venue evaluates, which message reveals intervention, and how reconciliation behaves after a partial fill or disconnect. Platform documentation describes supported settings; it cannot prove that an operator configured them correctly. In this dimension, ticker collisions across chains is therefore an explicit audit gap.

The asset symbol row should end with a concrete monitoring rule tied to coin or token selected by the sender. Make the operator match the asset at both ends, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; ticker collisions across chains remains a separate production risk until observed.

2. Control test: Network

For network, inspect chain or rail used for settlement. Use a sandbox, non-production context, or the smallest reversible test available, then confirm sender and receiver support the same network.

In this dimension, recovery after wrong-network transfer is therefore an explicit audit gap.

The network row should end with a concrete monitoring rule tied to chain or rail used for settlement. Make the operator confirm sender and receiver support the same network, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; recovery after wrong-network transfer remains a separate production risk until observed.

3. Control test: Address

For address, inspect destination string and format. Use a sandbox, non-production context, or the smallest reversible test available, then copy and paste the full address.

In this dimension, clipboard compromise is therefore an explicit audit gap.

The address row should end with a concrete monitoring rule tied to destination string and format. Make the operator copy and paste the full address, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; clipboard compromise remains a separate production risk until observed.

4. Control test: Tag or memo

For tag or memo, inspect extra routing field for shared-address systems. Use a sandbox, non-production context, or the smallest reversible test available, then enter the exact memo/tag when required.

In this dimension, manual credit policy is therefore an explicit audit gap.

The tag or memo row should end with a concrete monitoring rule tied to extra routing field for shared-address systems. Make the operator enter the exact memo/tag when required, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; manual credit policy remains a separate production risk until observed.

5. Control test: Confirmation count

For confirmation count, inspect chain confirmations before credit. Use a sandbox, non-production context, or the smallest reversible test available, then wait for both chain and platform credit.

In this dimension, platform screening delay is therefore an explicit audit gap.

The confirmation count row should end with a concrete monitoring rule tied to chain confirmations before credit. Make the operator wait for both chain and platform credit, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; platform screening delay remains a separate production risk until observed.

6. Control test: Status field

For status field, inspect pending, success, rejected or waiting user confirmation. Use a sandbox, non-production context, or the smallest reversible test available, then log the status without secrets.

In this dimension, future status-code changes is therefore an explicit audit gap.

The status field row should end with a concrete monitoring rule tied to pending, success, rejected or waiting user confirmation. Make the operator log the status without secrets, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; future status-code changes remains a separate production risk until observed.

7. Control test: Regex metadata

For regex metadata, inspect addressRegex or memoRegex guidance. Use a sandbox, non-production context, or the smallest reversible test available, then validate format before sending.

In this dimension, semantic correctness is therefore an explicit audit gap.

The regex metadata row should end with a concrete monitoring rule tied to addressRegex or memoRegex guidance. Make the operator validate format before sending, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; semantic correctness remains a separate production risk until observed.

8. Control test: Small test

For small test, inspect low-value transfer before a larger move. Use a sandbox, non-production context, or the smallest reversible test available, then test with an amount above minimums and fees.

In this dimension, future route availability is therefore an explicit audit gap.

The small test row should end with a concrete monitoring rule tied to low-value transfer before a larger move. Make the operator test with an amount above minimums and fees, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; future route availability remains a separate production risk until observed.

9. Control test: Support packet

For support packet, inspect txid, asset, network, time and non-secret account evidence. Use a sandbox, non-production context, or the smallest reversible test available, then prepare evidence without private keys or codes.

In this dimension, support outcome is therefore an explicit audit gap.

The support packet row should end with a concrete monitoring rule tied to txid, asset, network, time and non-secret account evidence. Make the operator prepare evidence without private keys or codes, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; support outcome remains a separate production risk until observed.

10. Control test: Radar use

For radar use, inspect field disclosure across exchanges. Use a sandbox, non-production context, or the smallest reversible test available, then turn fields into a checklist.

In this dimension, hidden internal crediting rules is therefore an explicit audit gap.

The radar use row should end with a concrete monitoring rule tied to field disclosure across exchanges. Make the operator turn fields into a checklist, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; hidden internal crediting rules remains a separate production risk until observed.

Decision scenarios

Scenario 1: when asset symbol becomes decisive

Consider a reader whose main constraint is coin or token selected by the sender. The correct response is not to infer a universal platform or product winner. It is to match the asset at both ends, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when network becomes decisive

Consider a reader whose main constraint is chain or rail used for settlement. It is to confirm sender and receiver support the same network, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when address becomes decisive

Consider a reader whose main constraint is destination string and format. It is to copy and paste the full address, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when tag or memo becomes decisive

Consider a reader whose main constraint is extra routing field for shared-address systems. It is to enter the exact memo/tag when required, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when confirmation count becomes decisive

Consider a reader whose main constraint is chain confirmations before credit. It is to wait for both chain and platform credit, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when status field becomes decisive

Consider a reader whose main constraint is pending, success, rejected or waiting user confirmation. It is to log the status without secrets, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• Wallet REST API - Capital — Binance Developer Docs
• How to withdraw cryptocurrencies from your Kraken account — Kraken Support
• Why is my transaction missing? — Coinbase Help
• Send crypto — Coinbase Help