Study guide
12.3 Wallet Types, Custody Architectures, and Counterparty Risks
ACAMS Certified AML FinTech Compliance Associate CAFCA
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CAFCA Exam Overview and Study Strategy
1.1 CAFCA Exam Format, Official Domains, and Study Strategy
2 Chapter 2: Domain 1: FinTech Business Models and Their Vulnerabilities
2.1 Neobanks, Challenger Banks, and Digital Banking Models 2.2 Payment Processors, Gateways, and Merchant Acquirers 2.3 Buy Now, Pay Later (BNPL) and Alternative Credit 2.4 BaaS Architecture, Embedded Finance, and Program Structures
3 Chapter 3: Domain 1: Financial Crime Types and the Regulatory Perimeter
3.1 Types of Financial Crime and Predicate Offences 3.2 Licensing, Registration, Charters, and Regulatory Sandboxes 3.3 Virtual Asset Service Provider (VASP) Framework & FinCEN MSB Rules
4 Chapter 4: Domain 1: Global AML Frameworks and Sources of Guidance
4.1 U.S. Regulatory Architecture: BSA, PATRIOT Act, and AMLA 2020 4.2 European Union Regulatory Framework: AMLD6, the AML Package, and MiCA 4.3 International Standards: UK FCA, Singapore MAS, and Hong Kong HKMA 4.4 Sources of Guidance for Building Anti-Financial Crime Processes
5 Chapter 5: Domain 1: Risk Management Framework, Risk-Based Approach, and Data Protection
5.1 Risk Management Framework: Lines of Defence, Policies, Assurance, and the MLRO 5.2 Risk-Based Approach, Risk Assessment, Risk Appetite, and Types of Risk 5.3 Handling Sensitive Information: PII, SPII, Privacy Laws, and Breach Reporting
6 Chapter 6: Domain 1: Bank Partners and Internal Threats
6.1 Regulatory Expectations and Enforcement on Sponsor Banks 6.2 How Banks Risk-Rate FinTechs: Onboarding, Ongoing Oversight, and De-Risking 6.3 Controlling Internal Threats: Insider Fraud, Collusion, and Data Misuse
7 Chapter 7: Domain 2: CIP, KYC, CDD, and EDD
7.1 Customer Identification Program (CIP) Under USA PATRIOT Act §326 7.2 The FinCEN CDD Rule & Beneficial Ownership Standards 7.3 KYC to EDD: Applying CDD and Enhanced Due Diligence Across Customer Types
8 Chapter 8: Domain 2: Identity Verification, Data Sources, and Device Data
8.1 Digital Onboarding & Electronic KYC (eKYC) Foundations 8.2 Biometric Face Matching and Liveness Detection 8.3 Verification Data Sources and How to Judge Their Reliability 8.4 Device Fingerprinting, Geolocation, and Behavioral Biometrics
9 Chapter 9: Domain 2: Onboarding Screening, Risk Ratings, and Fraud Red Flags
9.1 Screening at Onboarding: Sanctions Lists, PEPs, and Known Fraudsters 9.2 Customer Risk Ratings: Factors, Data Sources, and How Scoring Models Work 9.3 Detecting Synthetic Identity Fraud and Ineligible Applicants 9.4 Deepfakes, Generative AI Threats, and Scam Typologies
10 Chapter 10: Domain 3: Payment Screening
10.1 OFAC Sanctions Regimes & the 50 Percent Rule 10.2 Real-Time vs. Batch Screening Architecture in High-Velocity Rails 10.3 Screening Logic: Fuzzy Matching, Phonetics, and PEP Controls
11 Chapter 11: Domain 3: Transaction Monitoring Systems and Red Flags
11.1 Hybrid Transaction Monitoring: Rules Engines vs. Machine Learning 11.2 FinTech Typologies: Mule Networks, Funnel Accounts, and Rapid Pass-Through 11.3 Fraud-AML Convergence: BIN Attacks, ATO, and Credential Stuffing 11.4 Model Risk Management Under SR 11-7 & System Optimization
12 Chapter 12: Domain 3: Payment Methods and Transaction Risk Characteristics
12.1 Common Payment Methods, Crypto, and High-Risk Transactions Such as Aggregation 12.2 Transaction Risk Characteristics: Reversibility, Convertibility, Fund Integrity, and Privacy Coins 12.3 Wallet Types, Custody Architectures, and Counterparty Risks 12.4 Stablecoins, On/Off Ramps, and Asset-Referenced Tokens
13 Chapter 13: Domain 3: Monitoring Crypto Transactions
13.1 Blockchain Analytics & Transaction Tracing 13.2 The FATF Travel Rule for Virtual Assets 13.3 DeFi, Mixers, and Smart Contract Sanctions
14 Chapter 14: Domain 3: Alert Investigation, Audit Trails, and Monitoring MI
14.1 The Alert Investigation Process: From Unusual to Suspicious and When to Escalate 14.2 Building an Audit Trail for Suspicious Activity Reviews 14.3 Communicating Monitoring Results: KPIs, KRIs, OKRs, and Management Information
15 Chapter 15: Domain 4: Investigations and Customer Communication
15.1 Talking to Customers During Investigations and Offboarding: Financial Crime Risk vs Policy Breach 15.2 Reviewing KYC, Transactions, Open Sources, and Documents to Build an Investigation 15.3 Analytical Principles in Investigations: Avoiding Confirmation Bias and Other Traps
16 Chapter 16: Domain 4: SARs and STRs
16.1 SARs and STRs: What They Are, When and Where to File, and Why They Matter 16.2 Writing Effective SAR and STR Narratives
17 Chapter 17: Domain 4: Law Enforcement, Regulators, and Banking Partners
17.1 Operational AML Governance and Third-Party Risk Management 17.2 Working With Law Enforcement, Banking Partners, Regulators, and Other Third Parties 17.3 Types of Law Enforcement Requests: Subpoenas, Court Orders, 314(a), and International Requests 17.4 How Banking Partners' Terms of Service Relate to the FinTech's Own Terms
18 Chapter 18: Domain 5: Scaling Anti-Financial Crime Strategies
18.1 Assessing New Products and Features Before Launch 18.2 Refreshing the Financial Crime Risk Assessment as the Business Scales 18.3 Changes That Should Trigger a Financial Crime Risk Assessment Review 18.4 Record Retention Rules and Secure Data Storage 18.5 Outsourcing Controls: Surge Capacity, RegTech, and Independent Testing
12.3 Wallet Types, Custody Architectures, and Counterparty Risks
Key Takeaways Explain This Topic AI
The foundational distinction between custodial and unhosted (self-hosted) wallets centers on private key control: custodial wallets delegate cryptographic signing to an intermediary, and users' rights in an insolvency depend on the terms and applicable law, while unhosted wallets give the user exclusive key control without intermediary recourse.
Multi-Party Computation (MPC) secures private keys by mathematically distributing split key shares across multiple secure environments, generating standard single-signature transactions off-chain without ever assembling the complete private key in a single location.
Institutional custodians partition digital assets across storage tiers: hot wallets (internet-connected, 1%–5% of assets for immediate operational liquidity), warm wallets (semi-automated with multi-approval HSM gateways), and cold storage (air-gapped, offline FIPS-validated HSMs commonly holding most reserves).
Centralized exchanges execute trading on internal off-chain database matching engines with zero public blockchain footprint, sweeping user deposits into omnibus addresses and creating severe counterparty and commingling risks in corporate insolvencies.
Unhosted wallet control is verified by message signing or micro-transfer (Satoshi) tests; FinCEN's 2020 proposal for $3,000 recordkeeping and $10,000 reporting on unhosted wallet transactions was never finalized and was withdrawn in October 2026.
Last updated: October 2026
At the foundation of blockchain transactions and digital asset compliance lies cryptographic key management. Anti-Financial Crime ( AFC ) and compliance specialists must understand the structural differences between custodial and unhosted wallets, evaluate the security architectures governing institutional custody, identify counterparty exposures in centralized exchanges, and navigate regulatory requirements for verifying customer wallet control.
Custodial vs. Unhosted (Non-Custodial) Wallets
In digital asset ecosystems, a cryptographic wallet does not actually contain tokens. Rather, tokens reside as immutable ledgers on decentralized blockchains. A wallet is a software application, hardware device, or institutional service that creates, stores, and manages the public and private key pairs required to view balances and sign transactions.
The foundational compliance distinction centers on private key ownership:
Custodial Wallets
In a custodial arrangement, a third-party intermediary—such as a centralized digital asset exchange, broker-dealer, or specialized qualified custodian—holds and controls the cryptographic private keys on behalf of the user.
Account Mechanics : The customer interacts with the platform through a traditional digital interface using login credentials, two-factor authentication (2FA), or biometric mobile access. The user does not interact directly with the blockchain protocol when initiating transfers within the platform.
Legal and Counterparty Status : The user does not hold the keys. Whether the user owns the assets or is only an unsecured creditor in an insolvency depends on the platform's terms and the applicable law, which is why outcomes in crypto bankruptcies have varied.
Compliance and Enforcement : The custodian is a regulated financial intermediary (typically an MSB, trust company, or bank) subject to BSA/AML regulations. The custodian performs Customer Identification Programs ( CIP ), Customer Due Diligence ( CDD ), ongoing transaction monitoring, and Office of Foreign Assets Control ( OFAC ) sanctions screening. If presented with a lawful court order, subpoena, or regulatory freeze mandate, the custodian can immediately freeze, seize, or restrict the customer's account.
Unhosted (Non-Custodial / Self-Hosted) Wallets
In an unhosted wallet arrangement, the individual user retains exclusive, absolute possession and control over the private cryptographic keys and the underlying recovery seed phrase (typically a 12- or 24-word mnemonic phrase based on the Bitcoin Improvement Proposal 39, or BIP-39 standard).
Technical Forms : Unhosted wallets exist as open-source software applications installed on personal computers or smartphones (software wallets like MetaMask or Trust Wallet) or dedicated physical microcontrollers (hardware wallets like Ledger or Trezor).
Sovereign Operational Control : Transactions are signed locally on the user's device using the private key and broadcast directly to the decentralized blockchain network. No third-party intermediary validates, screens, or mediates the transfer.
Compliance Maxim : The industry aphorism "not your keys, not your coins" captures this reality. Because no intermediary sits between the user and the blockchain ledger, no central administrator possesses the technical ability to reverse a transaction, reset a forgotten password, recover stolen private keys, or freeze an unhosted wallet address.
Cryptographic Custody Architectures: Single-Key, Multisig, and MPC
Institutional digital asset custodians and FinTech platforms cannot rely on basic consumer wallet architectures. They deploy sophisticated cryptographic management schemes to safeguard billions of dollars in client assets against external cyberattacks, physical coercion, and rogue insider embezzlement.
1. Single-Key (Single-Signature) Custody
A single-key setup relies on a single private key to sign and authorize transactions from a given blockchain address.
Vulnerabilities : Single-key architecture creates an acute single point of failure . If an insider steals the key, an attacker compromises the server memory, or an employee misplaces the physical backup, the assets are permanently lost. Single-key custody is considered unviable for institutional asset management.
2. Multi-Signature (Multisig) Architecture
Multi-signature architecture distributes signing authority across multiple distinct private keys on-chain using smart contract scripts or protocol-level validation rules.
M M M -of- N N N Threshold : A multisig address is configured to require M M M out of N N N possible private keys to authorize a valid transaction (for example, a 2-of-3 scheme where signatures from two corporate executives, or one executive and an external security partner, are required to move funds; or a 3-of-5 scheme for large institutional treasury reserves).
Strengths and Limitations : Multisig offers transparent, auditable governance enforced directly by blockchain consensus rules. However, multisig is protocol-specific (Bitcoin uses native script opcodes, while Ethereum and EVM chains rely on complex smart contracts such as Safe). Multisig transactions also consume more block space, resulting in higher network gas fees, and publicly reveal the multisig structure and signer addresses on the public ledger.
3. Multi-Party Computation (MPC)
Multi-Party Computation (MPC) represents the cutting edge of institutional cryptographic custody, utilizing advanced cryptographic mathematics known as Threshold Signature Schemes ( TSS ).
Key Share Distribution : In an MPC architecture, a complete private key is never generated, stored, or assembled in a single location, device, or point in time. Instead, a mathematical protocol generates multiple distributed key shares (or secret shares). These shares are partitioned across isolated, independent environments—such as disparate cloud providers, offline servers, and hardware security modules held by separate corporate officers.
Off-Chain Quorum Computation : When a transaction is authorized, the key-share holders interact through an off-chain cryptographic protocol to compute a valid digital signature. The final signature broadcast to the blockchain is indistinguishable from a standard single-key signature.
Compliance and Security Advantages : MPC eliminates single points of failure, is completely blockchain-agnostic (functioning identically across Bitcoin, Ethereum, Solana, and novel protocols), incurs standard low gas fees, and keeps the internal organizational signing structure completely private from public blockchain observers. Furthermore, MPC supports key share refreshing , allowing institutions to rotate key shares periodically without changing the public blockchain address.
Storage Tiering: Hot, Warm, and Cold Wallet Infrastructures
Regulated institutional VASPs segregate digital assets across three primary architectural tiers to balance instant operational liquidity with absolute security:
Storage Tier Connectivity & Environment Typical Asset Allocation Primary Operational Purpose Attack Surface & Security Defenses
Hot Wallet Online, internet-connected servers directly linked to automated API gateways 1% to 5% of total platform assets Immediate automated customer withdrawals and exchange liquidity Highest attack surface; defended by automated rate limits, IP whitelisting, HSMs, and anomaly monitoring
Warm Wallet Semi-connected systems; automated transaction generation with isolated signing 5% to 15% of total platform assets Intermediate liquidity buffer to replenish hot wallets without accessing cold storage Moderate attack surface; requires multi-party approvals, MPC quorums, or time-locked smart contracts
Cold Storage 100% air-gapped, offline environments completely isolated from the internet 80% to 95%+ of total platform assets Long-term safekeeping of the vast majority of customer and institutional assets Minimal attack surface; FIPS 140-3 Level 3/4 HSMs, deep underground physical vaults, biometric dual-control access
Institutional cold storage generates and retains private keys inside Hardware Security Modules (HSMs) validated under Federal Information Processing Standard ( FIPS ) 140-3 (or legacy FIPS 140-2 validations, which moved to historical status in September 2026) at Level 3 or Level 4. Cold storage workflows require manual physical intervention: multiple designated key custodians must physically travel to geographically dispersed, access-controlled vault facilities, pass biometric scans, and execute dual-custody ceremony procedures to authorize batched asset movements.
Omnibus Exchange Deposit Addresses and Internal Off-Chain Ledgers
Understanding the internal accounting mechanics of centralized virtual asset exchanges (CEXs) is vital for financial crime investigators and compliance officers. Centralized exchanges do not record user-to-user trades on public blockchains.
1. Inbound Deposit Routing and Sweeping
When a user opens an exchange account, the platform assigns a unique blockchain deposit address or provides a shared omnibus address paired with a mandatory destination identifier:
Unique Address Mapping : On blockchains like Ethereum or Bitcoin, the exchange assigns each customer a unique public address generated via hierarchical deterministic ( HD ) derivation paths (under BIP-32/44).
Destination Tags and Memos : On blockchains like XRP Ledger, Stellar, or TON, all platform users deposit into a single, shared corporate omnibus address. The user must include a unique destination tag or memo in the transaction payload to allow the exchange's internal database to attribute the deposit to their specific account.
Omnibus Sweeping : Once deposited crypto arrives, the exchange's automated backend sweeps the funds from thousands of individual user deposit addresses into massive, consolidated corporate omnibus wallets (hot, warm, or cold).
2. Off-Chain Matching Engine Execution
Once funds are credited to a user's account balance, all subsequent trading—buying Bitcoin, selling Ether, executing derivatives trades—occurs entirely off-chain on the exchange's private, centralized database matching engine.
Speed and Efficiency : Internal trades execute in microseconds with zero blockchain transaction fees, processing tens of thousands of orders per second.
The Blockchain Blind Spot : During internal trading, zero transactions are broadcast to the public blockchain . A user can deposit $100,000 in Bitcoin, trade it for USDT, swap it for Ethereum, and execute fifty high-frequency trades over six months without a single on-chain transaction occurring. To an external blockchain analytics tool (such as Chainalysis, TRM Labs, or Elliptic), the Bitcoin simply entered an exchange deposit address and remained in an omnibus pool.
Investigative Reality : Public blockchain explorers cannot see internal exchange trading counterparties, trade timestamps, or account holders. Law enforcement obtains the exchange's internal records through legal process such as grand jury subpoenas, court orders, or mutual legal assistance requests, while other financial institutions can seek information through channels such as 314(b) sharing or Travel Rule messaging.
3. Commingling and Counterparty Bankruptcy Risk
Because centralized exchanges sweep assets into omnibus wallets, customer funds are physically and digitally commingled with the platform's proprietary operational revenues and capital reserves. In catastrophic corporate failures (as demonstrated in the historic collapses of FTX, Celsius Network, and Mt. Gox), omnibus accounts lacking formal, bankruptcy-remote trust documentation leave customers classified as general unsecured creditors . During bankruptcy proceedings, customer assets are frozen and absorbed into the debtor's estate, subjecting depositors to severe losses and multi-year recovery delays.
AML/Sanctions Implications of Unhosted Wallets & Proposed Rulemaking
Transactions interfacing with unhosted wallets present heightened money laundering, terrorist financing, and sanctions evasion risks because the counterparty is not a regulated financial institution subject to mandatory KYC or CIP programs.
FinCEN Proposed Rulemaking on Unhosted Wallets
In December 2020, FinCEN published a Notice of Proposed Rulemaking ( NPRM ), Requirements for Certain Transactions Involving Convertible Virtual Currency or Digital Assets . It was never finalized, and FinCEN formally withdrew it in October 2026. Its proposals still show how regulators viewed the risk:
$3,000 Recordkeeping Threshold : For transactions between a covered financial institution (bank or crypto MSB) and an unhosted or non-custodial wallet exceeding $3,000 , the institution would be mandated to verify and record the identity of the customer and the counterparty, including legal name, physical address, asset type, amount, transaction hash, and unhosted wallet address.
$10,000 Reporting Threshold : For transactions between a covered institution and an unhosted wallet aggregating more than $10,000 in a day under CTR-style aggregation, the institution would have filed a CTR-like report directly with FinCEN.
Under FATF's updated guidance, VASPs are expected to apply a risk-based approach to unhosted wallet interactions: conducting automated blockchain analytics on originating and destination addresses, evaluating whether the unhosted wallet has interacted with darknet marketplaces, mixers, or sanctioned entities, and determining whether enhanced due diligence ( EDD ) or transaction blocking is required. Without a specific U.S. rule, this risk-based approach is what supervisors and partner banks expect.
Verifying Proof of Wallet Control
When customers transfer funds between an unhosted wallet and a regulated VASP, compliance teams often must verify whether the customer actually owns or controls the private keys of the external wallet. This control verification prevents illicit pass-through funnels, third-party money mule exploitation, and unauthorized third-party transfers.
Three primary methodologies exist for verifying wallet control:
Cryptographic Signature Verification (Nonce / Message Signing) :
Technical Mechanism : The VASP generates a unique, pseudo-random, time-stamped string of characters called a nonce (or a structured authorization message). Within the VASP portal or mobile application, the customer is prompted to connect their unhosted wallet (via Web3 browser extensions or hardware signers) and sign the nonce using their private key.
Validation : The VASP applies the corresponding public key to verify mathematically that the digital signature was generated by the private key controlling that specific blockchain address.
Evaluation : Highly secure, instantaneous, completely free of blockchain gas fees, and provides irrefutable mathematical proof of key control without exposing the underlying private key or recovery seed phrase.
Micro-Deposit / "Satoshi Test" :
Technical Mechanism : The VASP instructs the customer to send a specific, non-round micro-amount of digital currency (for example, exactly 0.0001842 BTC or a precise small fraction of an asset) from their unhosted wallet to a designated VASP deposit address within a narrow time window (e.g., 30 minutes). Alternatively, the VASP sends a micro-amount to the unhosted wallet and requires the user to return a specified portion.
Validation : The VASP confirms that the exact micro-amount was received from the claimed unhosted address within the authorized timeframe.
Evaluation : Effective for legacy or multi-signature wallets that do not natively support arbitrary message signing protocols. However, it is slow (requiring blockchain block confirmations) and forces the customer to incur on-chain network transaction fees.
Visual Proof / Screenshot Submission (Legacy & Discouraged) :
Technical Mechanism : The customer captures and submits a screenshot of their software or hardware wallet interface displaying their public address and account balance.
Evaluation : Extremely vulnerable to digital alteration, photo-editing tools, HTML code inspection spoofing, and social engineering. Regulated institutions strongly discourage or prohibit visual proof as an acceptable verification methodology for institutional compliance.
Comparative Custody & Wallet Matrix
The following table contrasts the core operational and compliance dimensions of digital asset wallet architectures:
Custody Dimension Custodial Hot Wallet Custodial Cold Storage Unhosted Hardware Wallet Unhosted Software Wallet
Private Key Custodian Institutional VASP / Custodian Institutional VASP / Qualified Trust Individual End-User Individual End-User
Internet Connectivity Continuously online / API-integrated Completely air-gapped / 100% offline Offline storage; connects via USB/Bluetooth only when signing Device connected to internet during operation
Counterparty Insolvency Risk High; subject to custodian bankruptcy Low-to-moderate; safeguarded if under bankruptcy-remote trust Zero; completely independent of third-party balance sheets Zero; completely independent of third-party balance sheets
Blockchain Visibility of Internal Trades Completely invisible; trades occur on off-chain databases Completely invisible; long-term reserve safekeeping Fully transparent; every transaction broadcast to public ledger Fully transparent; every transaction broadcast to public ledger
Mandatory CIP/CDD at Creation Yes; fully enforced by regulated institution Yes; institutional onboarding agreements and CDD No; open-source software, zero identity requirements No; open-source software, zero identity requirements
Primary Risk & Attack Surface Server compromise, API key theft, zero-day vulnerabilities Rogue insider collusion, physical vault breach, key ceremony failure Physical theft of device, compromised seed phrase backup, supply chain attack Malware, clipboard hijackers, phishing, fraudulent smart contract approvals
Realistic Exam Scenario
A compliance investigator at Horizon Digital Assets, a licensed U.S. cryptocurrency exchange, reviews an onboarding transaction: a newly registered business customer, Vanguard Logistics LLC, initiates a deposit of 420 ETH (valued at approximately $1,300,000) from an external wallet address.
Before crediting the funds to the corporate account, the exchange's automated risk engine flags the inbound transaction:
Blockchain forensics indicates that two hops prior to reaching the depositing address, 150 ETH originated from an unhosted address that had interacted with a non-custodial decentralized privacy mixer.
The external depositing wallet is an unhosted address that has never previously interacted with Horizon Digital Assets.
Compliance Action and Analysis :
Step 1: Wallet Control Verification : Horizon requires Vanguard's designated corporate officer to execute a cryptographic message-signing challenge (nonce test) using their Web3 wallet. The signature is mathematically verified within 60 seconds, proving Vanguard holds operational control of the depositing wallet and ruling out accidental deposit routing or third-party redirection.
Step 2: Blockchain Provenance Tracing : The compliance team utilizes blockchain analytics to map the complete transaction path. While 150 ETH touched a mixer two hops back, the remaining 270 ETH originated directly from a regulated institutional OTC desk.
Step 3: Enhanced Due Diligence (EDD) : Under its risk-based AML program (31 CFR § 1022.210 for MSBs), Horizon requests documented Source of Wealth ( SoW ) and Source of Funds ( SoF ), including corporate financial statements, vendor settlement invoices, and written explanations regarding the historical mixer exposure.
Step 4: Suspicious Activity Assessment : If the client provides verifiable commercial documentation demonstrating that the mixer-adjacent funds were acquired legitimately through a bona fide commercial trade without knowledge of the prior mixer activity, the platform may clear the deposit with ongoing enhanced monitoring. However, if the client provides evasive answers, fabricated invoices, or cannot explain the privacy mixer nexus, Horizon must file a Suspicious Activity Report (SAR) under the $2,000 MSB threshold within 30 days and restrict outbound withdrawal capabilities.
Common Exam Traps
Trap 1: Believing Internal Exchange Trading Occurs On-Chain : Candidates often assume that when customers buy, sell, or trade cryptocurrencies on centralized exchanges like Coinbase or Kraken, every trade is recorded on the Bitcoin or Ethereum blockchain. In reality, internal trading occurs entirely on private, centralized off-chain databases with zero public blockchain footprint. Public ledgers only reflect deposits and withdrawals across the exchange's omnibus boundary.
Trap 2: Conflating Multi-Party Computation (MPC) with Multi-Signature (Multisig) : Candidates frequently confuse MPC with on-chain multisig. Multisig requires multiple on-chain signatures defined by protocol smart contracts, revealing the signing structure and incurring higher gas fees. MPC distributes mathematical key shares off-chain and produces a standard single signature that looks completely normal on-chain.
Trap 3: Assuming Proof of Wallet Control Proves Source of Wealth : Successfully verifying that a customer controls an unhosted wallet (via a cryptographic nonce signature or Satoshi test) proves only that the customer possesses the private key. It provides zero evidence regarding the legitimate origin of the funds, the customer's source of wealth, or the absence of prior illicit laundering hops.
Trap 4: Treating Unhosted Wallets as Categorically Illegal : Candidates often mistakenly believe that holding cryptocurrency in an unhosted wallet is illegal or prohibited under U.S. or international regulations. Unhosted wallets are fully legal; compliance obligations apply to regulated institutions when funds transition across the perimeter between unhosted wallets and regulated VASPs.