Исследование с проверкой источников: Coinbase Exchange Prime Onchain

Decision Matrix

Source Map

• Coinbase Help: Address book and crypto withdrawal address whitelisting (coinbase-exchange-whitelist)
• Coinbase Help: How does whitelisting in the address book work? (coinbase-exchange-hold)
• Coinbase Help: Trusted Address Book Protection (coinbase-prime-trusted)
• Coinbase Help: Onchain Trusted Address Book (coinbase-prime-onchain)

Control Notes

1. Account surface

Account surface is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means which Coinbase product controls the transfer path. The useful action is to identify Exchange, Prime portfolio or Prime Onchain Wallet first. The unresolved edge is cross-product account mapping, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, account surface 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. Destination set

Destination set is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means the approved or whitelisted withdrawal destinations. The useful action is to confirm the exact address book before transfer. The unresolved edge is hidden legacy entries, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

3. Approval model

Approval model is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means 2FA toggle, consensus approval or onchain policy governance. The useful action is to match approvals to organization roles. The unresolved edge is private role assignments, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, approval model 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 the time before a new address or disable action becomes effective. The useful action is to plan transfers around the documented timer. The unresolved edge is account-specific security review, 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. Network scope

Network scope is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether an address applies to one network or compatible networks. The useful action is to verify asset and network together. The unresolved edge is future network support, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

6. Onchain policy

Onchain policy is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means Prime Onchain-specific transaction policies and browser extension use. The useful action is to separate onchain policies from vault rules. The unresolved edge is policy inheritance, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

7. Deletion and edits

Deletion and edits is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means how address changes are approved or removed. The useful action is to record non-secret change evidence. The unresolved edge is historical approval state, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

8. User role

User role is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means who can initiate or approve address changes. The useful action is to check administrator and trader authority. The unresolved edge is private organization permissions, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, user role 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, setting name and non-secret destination label. The useful action is to avoid balances and full personal data. The unresolved edge is support-case privacy, 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 address governance is not decision-quality. The useful action is to stop if wallet type, address book or approval route is unclear. The unresolved edge is future UI changes, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

Known Unknowns

• cross-product account mapping
• hidden legacy entries
• private role assignments
• account-specific security review
• future network support
• policy inheritance
• historical approval state
• private organization permissions
• support-case privacy
• future UI changes

Practical Takeaway

The safest version of this article is the one that stays boring and exact. Coinbase publishes three different address-governance surfaces that should not be merged into one generic withdrawal-safety claim. Coinbase Exchange whitelisting restricts withdrawals to Address Book entries, gives an initial 8-hour window, then applies 48-hour holds for new addresses and disabling whitelisting. Coinbase Prime Trusted Address Book Protection is automatically enabled for portfolios and routes updates through consensus approvals. Coinbase Prime Onchain Wallet has a separate Onchain Trusted Address Book where Destination Protection is active by default and changes are governed by the General Consensus setting. The decision is which wallet, account type and approval model controls a transfer before any 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.