Исследование с проверкой источников: Binance / OKX

Verified source facts

1. OKX stated that USDC deposits and withdrawals on Arc opened at 04:00 UTC on September 16, 2026. 2. Binance announced that USDC deposits on Arc were open on September 16, 2026. 3. Binance said Arc withdrawals would open after sufficient deposits without a further announcement. 4. A USDC transfer must match the exact network supported by both sending and receiving services.

Comparison at a glance

1. Rights analysis: Asset

Tokenization analysis must follow the legal and operational chain, not the visual token. The asset question asks about USDC. Identify the issuer, tokenization sponsor, recordkeeper, custodian, broker or platform, and every agreement connecting them. Then match ticker and issuer. A wallet balance alone cannot answer which person or system has the enforceable obligation.

Test the arrangement under a disagreement. If the chain record and master securityholder file diverge, which one controls? If an intermediary fails, is the holder a customer, beneficial owner, secured claimant, or unsecured creditor? If a transfer is technically possible but legally restricted, what process reverses or freezes it? The available sources frame these questions, while lookalike remains outside the evidence set.

Turn the asset finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Match ticker and issuer before comparing yield, speed, or interface quality. Because lookalike is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

2. Rights analysis: Network

The network question asks about Arc. Then select exact chain.

The available sources frame these questions, while wrong route remains outside the evidence set.

Turn the network finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Select exact chain before comparing yield, speed, or interface quality. Because wrong route is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

3. Rights analysis: Deposit state

The deposit state question asks about venue-specific. Then check live page.

The available sources frame these questions, while stale notice remains outside the evidence set.

Turn the deposit state finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Check live page before comparing yield, speed, or interface quality. Because stale notice is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

4. Rights analysis: Withdrawal state

The withdrawal state question asks about may differ from deposits. Then verify separately.

The available sources frame these questions, while one-way assumption remains outside the evidence set.

Turn the withdrawal state finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Verify separately before comparing yield, speed, or interface quality. Because one-way assumption is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

5. Rights analysis: Address

The address question asks about generated by recipient. Then copy fresh.

The available sources frame these questions, while address reuse remains outside the evidence set.

Turn the address finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Copy fresh before comparing yield, speed, or interface quality. Because address reuse is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

6. Rights analysis: Contract

The contract question asks about official identity. Then verify source.

The available sources frame these questions, while spoof token remains outside the evidence set.

Turn the contract finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Verify source before comparing yield, speed, or interface quality. Because spoof token is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

7. Rights analysis: Minimum

The minimum question asks about venue threshold. Then check amount.

The available sources frame these questions, while uncredited transfer remains outside the evidence set.

Turn the minimum finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Check amount before comparing yield, speed, or interface quality. Because uncredited transfer is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

8. Rights analysis: Fee

The fee question asks about live withdrawal fee. Then capture before send.

The available sources frame these questions, while cost surprise remains outside the evidence set.

Turn the fee finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Capture before send before comparing yield, speed, or interface quality. Because cost surprise is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

9. Rights analysis: Test transfer

The test transfer question asks about small proof amount. Then wait for credit.

The available sources frame these questions, while irreversible loss remains outside the evidence set.

Turn the test transfer finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Wait for credit before comparing yield, speed, or interface quality. Because irreversible loss is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

10. Rights analysis: Stop rule

The stop rule question asks about network or status mismatch. Then do not send.

The available sources frame these questions, while support confirmation remains outside the evidence set.

Turn the stop rule finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Do not send before comparing yield, speed, or interface quality. Because support confirmation is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

Decision scenarios

Scenario 1: when asset becomes decisive

Consider a reader whose main constraint is USDC. The correct response is not to infer a universal platform or product winner. It is to match ticker and issuer, 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 Arc. It is to select exact chain, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when deposit state becomes decisive

Consider a reader whose main constraint is venue-specific. It is to check live page, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when withdrawal state becomes decisive

Consider a reader whose main constraint is may differ from deposits. It is to verify separately, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when address becomes decisive

Consider a reader whose main constraint is generated by recipient. It is to copy fresh, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when contract becomes decisive

Consider a reader whose main constraint is official identity. It is to verify source, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• USDC support on Arc — OKX
• USDC integration on Arc — Binance Support
• USDC overview — Circle