출처 검증 리서치: Coinbase

Decision Matrix

Source Map

• Coinbase Help: Set up your 2-step verification (coinbase-2fa)
• Coinbase Help: Address book allowlist (coinbase-allowlist)
• Coinbase Help: Address book and crypto withdrawal address whitelisting (coinbase-exchange-whitelist)
• Gemini Support: What is two-factor authentication? (gemini-2fa)
• Gemini Support: Using passkeys (gemini-passkeys)
• Gemini Support: How do I add an approved address? (gemini-approved-address)
• Gemini Support: What is Withdrawal Protection (gemini-withdrawal-protection)

Control Notes

1. Authentication baseline

Authentication baseline is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means required 2FA or passkey/security-key setup. The useful action is to record active and backup methods. The unresolved edge is account-specific recovery state, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, authentication baseline should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material. The record can stay simple: the official source URL, the date checked, the product or network under review, and a non-secret note describing why the next step is acceptable. Screenshots should avoid balances, identity documents, API keys, recovery phrases, private keys, passphrases, verification codes and support-ticket private data.

2. Backup method

Backup method is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means how access survives device loss. The useful action is to configure before changing phones. The unresolved edge is cloud sync or device-bound passkey limits, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, backup method should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

3. Address control

Address control is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means allowlist, whitelist, approved address or withdrawal protection. The useful action is to turn policy wording into a checklist. The unresolved edge is jurisdiction-specific naming, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, address control should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

4. Waiting period

Waiting period is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means 48-hour or 7-day address availability window. The useful action is to add destinations before urgent need. The unresolved edge is case-specific compliance holds, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, waiting period should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

5. API boundary

API boundary is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether automation can change destination policy. The useful action is to separate UI policy from API action. The unresolved edge is product-specific API rules, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, api boundary should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

6. Approval role

Approval role is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means single-user hold or multi-user approval. The useful action is to name the required role without exposing identity. The unresolved edge is organization permission drift, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, approval role should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

7. Recovery trigger

Recovery trigger is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means lost key, lost device or suspicious address change. The useful action is to document support path before incident. The unresolved edge is private support result, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, recovery trigger should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

8. Destination scope

Destination scope is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means asset, network, portfolio or account scope. The useful action is to check asset and network together. The unresolved edge is wrong-chain address risk, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, destination scope should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

9. Evidence packet

Evidence packet is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means official URL, date and non-secret configuration summary. The useful action is to retain without keys or codes. The unresolved edge is private balances and IDs, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

10. Stop rule

Stop rule is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means when the setup is not decision-quality. The useful action is to stop on unknown recovery, rushed address wait or broad withdraw API. The unresolved edge is future policy changes, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

Known Unknowns

• account-specific recovery state
• cloud sync or device-bound passkey limits
• jurisdiction-specific naming
• case-specific compliance holds
• product-specific API rules
• organization permission drift
• private support result
• wrong-chain address risk
• private balances and IDs
• future policy changes

Practical Takeaway

The safest version of this article is the one that stays boring and exact. Coinbase and Gemini both push users toward stronger authentication and destination controls, but they package the risk differently. Coinbase says 2-step verification is required, recommends multiple backup methods, supports passkeys and security keys, and uses address-book allowlisting to restrict sends to saved addresses after a 48-hour availability period. Coinbase Exchange documentation separately says whitelisting only allows withdrawals to addresses already in the Address Book and that API users cannot enable or disable whitelisting through the API. Gemini says 2FA is required and cannot be disabled, passkeys become the default 2FA method after opt-in, and approved-address or Withdrawal Protection flows can require a 7-day waiting period or multi-user approval before a wallet address can be used. The useful comparison is not which brand is safer in the abstract; it is whether the user's recovery method, address wait, API boundary and approval role are documented before funds move. The user outcome is a clearer next inspection step, not a promise that a platform, API, transfer route or tokenized asset will work under every future condition.