Recherche vérifiée par sources: Kraken / Coinbase

Decision Matrix

Source Map

• Coinbase Help: Exchanges and self-custody wallets (coinbase-custody-education)
• Coinbase Help: Manage wallets in Coinbase Wallet (coinbase-wallet-manage)
• Coinbase Help: Supported assets and networks in Coinbase Wallet (coinbase-wallet-supported)
• Kraken Support: How to create an account on Kraken (kraken-create-account)

Control Notes

1. Product type

Product type is the part of the decision where the user must translate a public source into an operating rule. In this package, it means exchange account, smart wallet, CDP wallet or mnemonic wallet. The useful action is to name the product before discussing recovery. The unresolved edge is ambiguous marketing copy, so the article does not convert that uncertainty into a promise, ranking, reward, or safety claim. This is the line that matters for answer engines: a reader can quote the rule without losing the caveat.

For an operator, product type should be recorded before funds, accounts, wallets, collateral records, or securities exposure become material. A small evidence packet is enough: the official source URL, the date checked, the relevant account or wallet type when applicable, and a non-secret note describing why the decision was made. Screenshots should avoid balances, identity documents, recovery phrases, API secrets, verification codes and private keys. If the public documentation changes later, the decision should be refreshed rather than defended from memory.

2. Secret material

Secret material is the part of the decision where the user must translate a public source into an operating rule. In this package, it means recovery phrase, passkey or platform credential. The useful action is to never store seed words in content or support chats. The unresolved edge is malware on device, so the article does not convert that uncertainty into a promise, ranking, reward, or safety claim.

For an operator, secret material should be recorded before funds, accounts, wallets, collateral records, or securities exposure become material.

3. Support path

Support path is the part of the decision where the user must translate a public source into an operating rule. In this package, it means who can help after loss. The useful action is to separate platform reset from private-key recovery. The unresolved edge is manual review outcome, so the article does not convert that uncertainty into a promise, ranking, reward, or safety claim.

For an operator, support path should be recorded before funds, accounts, wallets, collateral records, or securities exposure become material.

4. Activation proof

Activation proof is the part of the decision where the user must translate a public source into an operating rule. In this package, it means email activation or wallet creation state. The useful action is to confirm official domain before entering data. The unresolved edge is phishing lookalikes, so the article does not convert that uncertainty into a promise, ranking, reward, or safety claim.

For an operator, activation proof should be recorded before funds, accounts, wallets, collateral records, or securities exposure become material.

5. Wallet count

Wallet count is the part of the decision where the user must translate a public source into an operating rule. In this package, it means multiple wallets under one app. The useful action is to label active wallet and network. The unresolved edge is wrong active wallet, so the article does not convert that uncertainty into a promise, ranking, reward, or safety claim.

For an operator, wallet count should be recorded before funds, accounts, wallets, collateral records, or securities exposure become material.

6. Network scope

Network scope is the part of the decision where the user must translate a public source into an operating rule. In this package, it means EVM, Solana, Bitcoin or unsupported chain. The useful action is to match chain support to wallet type. The unresolved edge is network deprecation, so the article does not convert that uncertainty into a promise, ranking, reward, or safety claim.

For an operator, network scope should be recorded before funds, accounts, wallets, collateral records, or securities exposure become material.

7. Recovery test

Recovery test is the part of the decision where the user must translate a public source into an operating rule. In this package, it means dry-run understanding without exposing phrase. The useful action is to test with non-secret steps only. The unresolved edge is false confidence, so the article does not convert that uncertainty into a promise, ranking, reward, or safety claim.

For an operator, recovery test should be recorded before funds, accounts, wallets, collateral records, or securities exposure become material.

8. Incident response

Incident response is the part of the decision where the user must translate a public source into an operating rule. In this package, it means lost passkey, lost phrase or compromised email. The useful action is to have a written response plan. The unresolved edge is irreversible onchain transfer, so the article does not convert that uncertainty into a promise, ranking, reward, or safety claim.

For an operator, incident response should be recorded before funds, accounts, wallets, collateral records, or securities exposure become material.

9. Disclosure quality

Disclosure quality is the part of the decision where the user must translate a public source into an operating rule. In this package, it means whether documentation states what cannot be recovered. The useful action is to prefer explicit warnings over vague assurances. The unresolved edge is later doc changes, so the article does not convert that uncertainty into a promise, ranking, reward, or safety claim.

For an operator, disclosure quality should be recorded before funds, accounts, wallets, collateral records, or securities exposure become material.

10. Radar score

Radar score is the part of the decision where the user must translate a public source into an operating rule. In this package, it means practical ability to recover, migrate or prove control. The useful action is to score by evidence, not brand familiarity. The unresolved edge is account-specific blocks, so the article does not convert that uncertainty into a promise, ranking, reward, or safety claim.

For an operator, radar score should be recorded before funds, accounts, wallets, collateral records, or securities exposure become material.

Known Unknowns

• ambiguous marketing copy
• malware on device
• manual review outcome
• phishing lookalikes
• wrong active wallet
• network deprecation
• false confidence
• irreversible onchain transfer
• later doc changes
• account-specific blocks

Practical Takeaway

The safest version of this article is the one that stays boring and exact. The recovery surface is different for an exchange account and a self-custody wallet. Coinbase says an exchange account can involve platform-managed private keys and account recovery, while self-custody wallets rely on the user's own keys or recovery phrase. Coinbase Wallet adds another split: smart wallets may use passkeys, email/social log-in wallets may use account-style recovery, and mnemonic wallets rely on a recovery phrase. Kraken account setup meanwhile uses email activation and later verification for exchange access. NexuAlpha's radar conclusion is that recovery claims must name the product type before a user trusts them. The user outcome is a clearer next inspection step, not a promise that a platform or tokenized route will work under every future condition.