Мульти-акаунт на криптобіржі — Посібник з безпечного налаштування

Why Traders Run Multiple Exchange Accounts

Cryptocurrency traders and professional market participants operate multiple exchange accounts for several strategic and operational reasons. Understanding these use cases helps frame the infrastructure requirements.

Risk Distribution: Concentrating all assets on a single exchange creates a single point of failure. Exchange hacks (Mt. Gox, FTX, WazirX), regulatory freezes, and insolvency events have collectively cost users billions of dollars. Distributing funds across Binance, Bybit, OKX, Coinbase, Kraken, and other platforms reduces exposure to any single platform's risk. This is not multi-accounting in the traditional sense — it is using one account per exchange — but maintaining proper isolation between these accounts is still important.

Arbitrage Operations: Price discrepancies between exchanges create arbitrage opportunities. A trader might buy ETH on Bybit where it is $0.50 cheaper and simultaneously sell on Binance. This requires active accounts on both platforms, each with pre-positioned capital. For high-frequency arbitrage, minimizing latency is critical, and having accounts on multiple exchanges with different proxy connections enables parallel execution.

P2P Trading at Scale: Peer-to-peer trading on Binance P2P, Bybit P2P, and OKX P2P is a substantial business for many traders. Each exchange limits the number of active P2P ads per account and imposes trading volume limits. Professional P2P traders may operate multiple merchant accounts (often through legitimate business entities) to serve different fiat currencies, different payment methods, or different customer segments.

Trading Strategy Isolation: Sophisticated traders isolate different strategies on different accounts. One account runs a trend-following strategy on BTC/USDT, another runs a mean-reversion strategy on altcoins, and a third handles long-term spot holdings. This prevents interference between strategies and provides cleaner performance tracking.

Referral and Affiliate Programs: Exchange referral programs offer rebates on trading fees for referred users. While operating referral schemes with fake accounts violates terms of service, legitimate referral income from actual users requires separate tracking and management.

Regulatory Compliance: Traders operating in multiple jurisdictions may need separate accounts with different KYC documentation to comply with local regulations. A trader with dual citizenship might maintain accounts in different regulatory jurisdictions.

Regardless of the specific use case, each account must be completely isolated from others at the network, device, and behavioral levels. Exchanges actively detect and penalize multi-accounting, so proper infrastructure is essential.

How Exchanges Detect Multi-Accounting

Major exchanges invest millions of dollars in compliance and fraud detection systems that identify multi-accounting. Understanding their detection methods is the foundation for effective countermeasures.

IP Address Fingerprinting: This is the primary detection method. Exchanges log the IP address of every login, API call, withdrawal request, and trading action. If Account A and Account B are both accessed from the same IP address, they are flagged for review. Exchanges maintain historical IP databases — even if you used the same IP for two accounts months apart, the correlation can be detected retroactively.

Advanced IP analysis goes beyond simple matching. Exchanges analyze: - IP subnet proximity: Are the IPs on the same /24 subnet? This suggests the same ISP customer. - IP type classification: Datacenter IPs, VPN IPs, and shared proxy IPs are flagged as high-risk. Mobile carrier IPs receive the lowest risk score. - IP geolocation consistency: If Account A always logs in from Poland and suddenly logs in from Singapore, this triggers a security review.

Device Fingerprinting: Exchanges collect browser fingerprints similar to what sybil detection tools use — canvas hash, WebGL renderer, screen resolution, installed fonts, timezone, language headers, and more. Browser fingerprint matching across accounts is a strong multi-accounting signal.

Binance and OKX are known to use sophisticated device fingerprinting SDKs that collect hardware-level identifiers when possible, including device MAC addresses, hardware serial numbers (through WebUSB in some cases), and installed application lists (through protocol handlers).

Cookie and Storage Analysis: Some exchanges set persistent tracking cookies or use browser local storage to identify returning devices. If you visit Binance on Account A, log out, and log into Account B in the same browser, tracking cookies from the Account A session may still be present, linking the two sessions.

KYC Document Cross-Referencing: Exchanges share KYC data through compliance networks and industry databases. The same identity document (passport, national ID, driver's license) submitted to multiple accounts on the same exchange will be caught immediately. More advanced: facial recognition matching across different KYC submissions can identify the same person using different names or documents.

Behavioral Analysis: Machine learning models analyze trading behavior, login patterns, IP usage patterns, withdrawal addresses, and interaction sequences to identify accounts that behave similarly. Two accounts with similar trading schedules, similar instrument preferences, and similar order sizing may be flagged even without shared IPs or fingerprints.

Phone Number and Email Correlation: Using the same phone number recovery method, the same email domain pattern, or email addresses that follow the same naming convention across accounts is detectable.

Step 1: KYC and Identity Separation

KYC (Know Your Customer) separation is the foundational requirement for multi-account operations on regulated exchanges. Each account must be associated with a genuinely different identity to pass document verification and avoid cross-referencing detection.

Legitimate Multi-Account Approaches:

1. Personal + Business Accounts: Most exchanges allow both a personal account (verified with your personal ID) and a corporate/business account (verified with business registration documents). Binance, Bybit, and OKX all support separate personal and institutional accounts. This is the most straightforward and legitimate multi-account setup. The corporate account uses business documents (certificate of incorporation, articles of association, director ID), while the personal account uses your personal ID.

2. Family Member Accounts: Accounts belonging to different family members are legitimate separate accounts, provided each person genuinely controls their own account. Each person submits their own ID, uses their own email, and makes their own trading decisions. From a technical perspective, these accounts must still be fully isolated (separate IPs, separate devices) because the exchange cannot know that Family Member B lives at the same address — the IP overlap would flag both accounts.

3. Multi-Jurisdiction Accounts: Traders with residency in multiple countries may maintain accounts on different exchanges in different jurisdictions, each verified with the appropriate local documentation.

KYC Documents per Account: - Unique government-issued photo ID (passport, national ID, or driver's license) - Unique selfie (exchanges use facial recognition to match the selfie with the ID photo) - Unique phone number (VoIP numbers are increasingly rejected; use physical SIM cards) - Unique email address (use different email providers — do not use john1@gmail.com and john2@gmail.com) - Unique residential address proof (utility bills, bank statements)

Critical Rules: - NEVER submit the same document to multiple accounts on the same exchange. The document hash, number, and facial biometrics will be cross-referenced. - NEVER use obviously related email addresses. Automated systems flag email addresses with similar patterns. - Use different phone numbers from different carriers. Some exchanges check if phone numbers are on the same carrier account. - If using family member accounts, each family member should independently manage their own account. Unauthorized control of another person's exchange account may violate both exchange terms and financial regulations.

Note: Creating exchange accounts with fraudulent identity documents is illegal in most jurisdictions and can result in criminal charges. This guide assumes you have legitimate reasons for maintaining multiple accounts with proper KYC documentation.

Step 2: IP Isolation with CryptoProxy Mobile Proxies

IP isolation is the second critical requirement. Each exchange account must exclusively access the exchange from a dedicated IP address that is never used for any other account on the same exchange.

Setup Process:

1. Purchase one CryptoProxy mobile proxy per exchange account. For a setup with 2 Binance accounts, 1 Bybit account, and 1 OKX account, you need 4 proxies.

2. Create a proxy-to-account assignment map and NEVER deviate from it: - Proxy 1 (T-Mobile, SOCKS5 port 10501) → Binance Account A - Proxy 2 (Orange, SOCKS5 port 10502) → Binance Account B - Proxy 3 (Play, SOCKS5 port 10503) → Bybit Account - Proxy 4 (Plus, SOCKS5 port 10504) → OKX Account

3. Configure each proxy in a dedicated anti-detect browser profile (see Step 3). The proxy credentials are entered in the browser profile settings, not at the system level. This ensures isolation — each browser profile routes traffic through its assigned proxy exclusively.

Why Mobile Proxies Are Essential for Exchange Accounts:

Exchanges categorize IP addresses by type and assign risk scores: - Datacenter/Hosting IPs: HIGH RISK. Immediately trigger enhanced verification. Many exchanges require additional selfie verification or impose withdrawal delays for datacenter IPs. Some exchanges block datacenter IPs entirely. - VPN IPs: MEDIUM-HIGH RISK. Known VPN IP ranges are maintained in databases. While not always blocked, VPN IPs receive elevated scrutiny. - Residential IPs: LOW RISK. Standard residential ISP IPs are considered normal. However, shared residential proxies (where many proxy users share the same IP) may be flagged if the IP appears in abuse databases. - Mobile Carrier IPs: LOWEST RISK. Real mobile carrier IPs are the most trusted category. Exchanges cannot restrict them without blocking millions of legitimate mobile users. CryptoProxy's Polish carrier IPs fall into this category.

CryptoProxy's dedicated allocation ensures your IP has not been used by other proxy customers for exchange operations. On shared proxy services, hundreds of users may access Binance from the same IP, causing that IP to be flagged. CryptoProxy's dedicated modem slots eliminate this risk.

IP Consistency: Unlike airdrop farming where you rotate IPs between sessions, exchange accounts benefit from IP consistency. A Binance account that always logs in from the same Polish mobile IP builds a consistent location profile. Sudden IP changes trigger security alerts (you may receive 'new device detected' emails). Rotate IPs sparingly — only when necessary (e.g., if the current IP gets flagged for unrelated reasons).

API Trading Considerations: If you use exchange APIs for automated trading, configure your trading bot to route API calls through the same CryptoProxy proxy assigned to that account. Most trading bots support SOCKS5 proxy configuration. Binance requires API calls to come from whitelisted IPs — whitelist your CryptoProxy IP for each account's API key.

Step 3: Anti-Detect Browser Profile Configuration

Each exchange account needs its own isolated browser profile with a unique fingerprint. This prevents device fingerprint correlation between accounts.

Profile Setup for Exchange Accounts:

Step 1 — Create a new profile in your anti-detect browser (AdsPower, GoLogin, Multilogin, or Dolphin Anty). Name it clearly: 'Exchange_Binance_AccountA' or 'Bybit_Corporate.'

Step 2 — Assign the dedicated CryptoProxy SOCKS5 proxy. Enter the host, port, username, and password. Click 'Check Proxy' to verify the connection. The IP should show a Polish mobile carrier.

Step 3 — Configure the fingerprint settings for each profile. Critical parameters:

- Operating System: Choose a common OS. Use the same OS across sessions for a given account (consistency matters more for exchange profiles than for farming profiles). If you start with Windows 10, keep it as Windows 10.

- Screen Resolution: Select a common resolution (1920x1080 is the safest). Once set, do not change it — exchanges expect device consistency from legitimate users.

- Timezone: Set to Europe/Warsaw to match the Polish IP geolocation. This is critical for exchange accounts because timezone mismatches trigger security reviews.

- Language: Set to Polish (pl-PL) or English (en-US). Match the language to what you selected during exchange registration.

- WebRTC: Set to 'Disabled' or 'Replace.' Exchanges may use WebRTC to detect your real IP. If WebRTC leaks your home IP while the proxy shows a Polish IP, the mismatch flags the account.

- Canvas/WebGL: Set to 'Noise' — the anti-detect browser will generate a unique but consistent fingerprint for this profile.

Step 4 — Install required browser extensions inside the profile. For exchange access, you may want: - MetaMask (for DeFi interactions linked to the exchange account) - Google Authenticator extensions (or use a mobile authenticator) - No other extensions (minimize fingerprint surface area)

Step 5 — Access the exchange website for the first time from this profile. Complete the login process. The exchange will register this device fingerprint as your 'trusted device.' Future logins from this same profile will match the trusted device, avoiding security alerts.

Step 6 — Bookmark the exchange URL in this profile's browser. Always access the exchange through this profile's browser — never through any other browser or profile, even 'just to check prices quickly.'

Profile Maintenance: Anti-detect browser profiles save their state (cookies, local storage, login sessions). When you close and reopen a profile, the browser resumes exactly where you left off. This is essential for exchange accounts — maintaining a continuous session history makes the account appear as a legitimate, consistent user.

Exchange-Specific Configuration: Binance, Bybit, OKX

Each major exchange has specific technical requirements and detection capabilities. Tailoring your setup to each exchange optimizes your protection.

Binance Configuration: Binance has the most sophisticated multi-account detection among major exchanges. Their compliance team uses advanced device fingerprinting, IP analysis, and behavioral modeling.

- API IP Whitelist: Binance requires whitelisting specific IPs for API access. Add your CryptoProxy proxy IP to the API whitelist. If you rotate the IP, you must update the whitelist. - Security Verification: Enable Google Authenticator 2FA, anti-phishing code, and withdrawal address whitelist. These security features are expected of legitimate users — not having them is itself a risk signal. - Login History: Binance shows login history including IP and device. Periodically review this to confirm all logins are from your CryptoProxy proxy IP. - Binance App: If you use the Binance mobile app, configure your phone's network through the same CryptoProxy proxy (using OpenVPN or a SOCKS5-compatible app). Never access a Binance account from both a proxied desktop and an un-proxied mobile device — the IP difference links the unproxied device to your real location.

Bybit Configuration: Bybit has moderately aggressive multi-account detection. Their system is strong on IP analysis but less sophisticated on fingerprinting than Binance.

- Subaccount Feature: Bybit offers subaccounts that allow you to create multiple trading accounts under one master account. If your use case supports it, subaccounts are a legitimate and exchange-approved way to run multiple strategies. - API Access: Bybit API supports SOCKS5 proxy configuration through most trading frameworks. Ensure your bot routes through the assigned CryptoProxy proxy. - Withdrawal Limits: Bybit has different withdrawal limits based on KYC level. Ensure each account has appropriate KYC for your volume.

OKX Configuration: OKX has strong multi-account detection, particularly around IP and device fingerprinting.

- Unified Account: OKX uses a unified account system where spot, margin, futures, and options share a single account. This reduces the legitimate need for multiple OKX accounts. - API Trading: OKX API supports proxy configuration. Use the dedicated CryptoProxy proxy for each account's API calls. - P2P Verification: OKX P2P has additional merchant verification. Merchant accounts undergo enhanced review, including IP history analysis. - Device Management: OKX allows you to view and manage trusted devices in account settings. Periodically review and remove any unexpected devices.

General Recommendations: - Enable the highest level of 2FA on every account (hardware key > authenticator app > SMS) - Use a unique email address per account (different providers if possible) - Use unique, strong passwords per account (password manager recommended) - Set up withdrawal address whitelists to protect against unauthorized withdrawals - Review account security settings monthly

Behavioral Separation for Exchange Accounts

Exchange multi-account detection goes beyond IP and device analysis. Behavioral analytics can identify accounts that are operated by the same person based on usage patterns.

Login Timing Patterns: If Account A always logs in at 9:00 AM UTC and Account B always logs in at 9:05 AM UTC, the consistent 5-minute offset is suspicious. Legitimate separate users have uncorrelated login times.

Solution: Do not access your exchange accounts sequentially. If you need to check multiple accounts, access them at different times throughout the day. Account A in the morning, Account B in the afternoon. Vary the specific times daily.

Trading Pair Preferences: If both accounts trade BTC/USDT, ETH/USDT, and SOL/USDT with similar allocation ratios, this behavioral similarity is a correlation signal.

Solution: Diversify trading activity per account. Account A focuses on BTC and ETH majors. Account B trades altcoins. If you must trade the same pairs, use different order types (limit vs market), different order sizes, and different trading frequencies.

Deposit and Withdrawal Patterns: The most dangerous behavioral signal. If Account A deposits 1 ETH, then Account B deposits 1 ETH five minutes later from the same blockchain address, the accounts are trivially linked through on-chain analysis.

Solution: NEVER fund multiple exchange accounts from the same blockchain wallet or bank account. Use different funding sources for each account. Space deposits by hours or days. Use different deposit amounts. Never withdraw from one account and deposit into another on the same exchange.

Order Placement Patterns: Professional detection systems analyze order book data. If Account A places a buy order at 14:32:05 and Account B places a sell order at 14:32:08 (potentially a wash trade or cross-account arbitrage), this is flagged immediately.

Solution: Never coordinate trades between your own accounts on the same exchange. This constitutes market manipulation (wash trading) and can result in account termination and potential legal consequences.

Session Duration: If both accounts have identical session durations (login at 9:00, logout at 9:23, every day), this consistency is a signal.

Solution: Vary your session durations. Some days spend 5 minutes on an account, other days 30 minutes. Do not follow a rigid pattern.

UI Interaction Patterns: Some exchange frontends track mouse movement patterns, typing speed, and navigation sequences. These behavioral biometrics can identify the same person across different accounts.

Solution: This is the hardest signal to mitigate. Awareness helps — consciously vary how you navigate the exchange interface. Use keyboard shortcuts for one account and mouse for another. Navigate to different sections in different orders.

Mobile Device Isolation for Exchange Apps

Many traders use exchange mobile apps alongside desktop access. Mobile apps introduce additional detection vectors that must be managed.

Mobile Device Fingerprinting: Exchange apps collect extensive device data: - Device model and manufacturer - OS version and build number - IMEI (International Mobile Equipment Identity) — unique per device - Advertising ID (IDFA on iOS, GAID on Android) — can be reset but is collected on first launch - SIM card ICCID and phone number - Installed app list (Android) — can reveal which other exchange apps are installed - WiFi BSSID — identifies your WiFi network - Battery level and charging state (used as a fingerprint component)

Isolation Options:

1. Separate Physical Devices: The most secure approach. Use a different phone for each exchange account. Each phone has a unique IMEI, unique advertising ID, and unique SIM card. Use different CryptoProxy OpenVPN connections on each phone to ensure IP isolation.

2. Work Profile / Dual Space (Android): Android supports work profiles (Android for Work) that create an isolated environment on the same device. The work profile has separate app instances, separate storage, and a partially separate device identity. Install the exchange app in the work profile and main profile for two-account isolation on one device. Limitations: the IMEI is shared, so this is not as strong as separate devices.

3. App Cloners (Android): Some Android apps like Parallel Space or Dual Space allow cloning an app to create a second instance. However, cloned apps may not have full fingerprint isolation, and some exchanges detect cloner environments.

4. Avoid Mobile Apps Entirely: The most conservative approach. Use only desktop access through anti-detect browser profiles. This eliminates all mobile device fingerprinting vectors. The downside is losing access to mobile-specific features (push notifications, mobile-only promotions, faster access).

Mobile Proxy Configuration: If you use exchange mobile apps, route the phone's traffic through CryptoProxy:

- OpenVPN: Install OpenVPN Connect on the phone. Import the CryptoProxy .ovpn configuration file. Connect before opening the exchange app. All traffic, including the exchange app, routes through the Polish mobile IP.

- SOCKS5 (Android): Use apps like SocksDroid or Drony to route specific app traffic through a SOCKS5 proxy. This allows you to proxy only the exchange app while other apps use the direct connection.

- WiFi Proxy (iOS): iOS allows SOCKS5 proxy configuration per WiFi network. This routes all traffic through the proxy when connected to that WiFi network.

Critical Rule: NEVER open an exchange app without the proxy active. A single direct connection (without proxy) reveals your real IP to the exchange, permanently associating your real location with that account. If the proxy drops, the phone may fallback to a direct connection before you notice.

API Trading Through Proxies

Automated trading through exchange APIs introduces specific proxy configuration requirements. Each trading bot or script must route API calls through the correct CryptoProxy proxy for the associated account.

Python (ccxt library — the most popular crypto trading library): CCXT supports SOCKS5 proxy configuration directly. When initializing an exchange object, pass the proxy parameters. Configure the SOCKS5 proxy URL as: socks5://username:password@host:port. The aiohttp session for async operations must also be configured to use the same proxy. This ensures all API calls — placing orders, checking balances, fetching market data — route through your CryptoProxy mobile IP.

Node.js (node-binance-api or ccxt): Similar to Python, pass the SOCKS5 proxy URL in the exchange configuration. For Node.js, you may need the socks-proxy-agent package to enable SOCKS5 support in HTTP libraries.

API IP Whitelisting: Binance, Bybit, and OKX all support (and Binance requires for withdrawal-enabled API keys) IP whitelisting for API access. Add your CryptoProxy proxy IP to the whitelist. Important considerations:

- CryptoProxy IPs can change when you rotate. If you rotate the IP, you must update the API whitelist. For trading bots, either disable auto-rotation or update the whitelist programmatically after rotation. - For trading bots that run continuously, avoid IP rotation entirely. Use a stable CryptoProxy IP and only rotate if the IP is flagged or has connectivity issues. - Keep the previous IP in the whitelist for a few hours after rotation, in case cached connections still use the old IP.

Rate Limiting: Exchange APIs impose rate limits (e.g., Binance: 1200 requests/minute for trading endpoints). These limits are per IP. Since each account uses a different CryptoProxy proxy (different IP), rate limits are independent. Account A's trading bot does not consume Account B's rate limit.

WebSocket Connections: Real-time market data feeds use WebSocket connections. SOCKS5 proxies support WebSocket tunneling, so CryptoProxy works seamlessly with exchange WebSocket APIs. Ensure your WebSocket client is configured to use the same SOCKS5 proxy as the REST API calls. In Python, the websocket-client library supports SOCKS5 proxies.

Fail-Safe Configuration: Configure your trading bot to halt trading if the proxy connection drops. Without the proxy, API calls would go through your real IP, exposing it to the exchange and potentially linking the account to your other accounts. Implement connection health checks that verify the proxy is active before sending API requests. Check the apparent IP periodically (e.g., by hitting an IP check API through the proxy) to confirm traffic is routing correctly.

Multiple Bot Instances: If you run trading bots for multiple accounts, each bot instance must use a different proxy. Run each bot in a separate process or container, each configured with its own CryptoProxy SOCKS5 credentials. Do not use a single bot instance that switches between accounts and proxies — this creates timing correlations between accounts.

Withdrawal and Fund Movement Safety

Fund movements between exchange accounts are the highest-risk activity for multi-account detection. On-chain transfers create permanent, public evidence of account linkage.

Golden Rule: NEVER transfer funds directly between your own accounts on the same exchange. A withdrawal from Account A's address that deposits into Account B's address creates an immutable on-chain link. Exchange compliance teams actively monitor for circular fund flows between their own accounts.

Safe Fund Movement Patterns:

1. CEX → DEX → CEX: Withdraw from Account A to an external wallet. Swap on a DEX (Uniswap, SushiSwap) to change the token and amount. Deposit a different token and different amount to Account B from a different external wallet. This breaks the direct on-chain link and changes the asset trail.

2. CEX → Bridge → CEX: Withdraw from Account A on Ethereum. Bridge to a different chain (e.g., Arbitrum via Orbiter). Deposit to Account B from the Arbitrum address. The cross-chain bridge breaks the direct tracing path, though sophisticated analysis can sometimes track through bridges.

3. CEX → Privacy Protocol → CEX: Use a privacy-preserving protocol (like Tornado Cash on supported chains, or Aztec Connect) to break the on-chain link. Note: some exchanges flag deposits from privacy protocols, so use intermediate wallets between the privacy protocol and the exchange deposit.

4. Time Separation: Even with intermediary steps, withdraw and deposit at different times. A withdrawal from Account A at 2:00 PM followed by a deposit to Account B at 2:15 PM (even through intermediaries) creates temporal correlation. Space movements by at least 24 hours.

Withdrawal Address Management: - Each account should withdraw to a unique external wallet that is never reused across accounts. - Never add Account A's deposit address as a whitelisted withdrawal address on Account B. - If the exchange shows 'recently used addresses,' ensure addresses from other accounts never appear.

Fiat On/Off Ramps: - Each account should use a different bank account or payment method for fiat deposits/withdrawals. - Never use the same credit card for multiple accounts. - P2P purchases should use different payment accounts per exchange account.

Internal Transfer Detection: Exchanges monitor for patterns where Account A withdraws X amount of Token Y, and Account B deposits approximately X amount of Token Y within a short timeframe. Even if the exact addresses differ (due to intermediary wallets), the amount and timing correlation is suspicious. Always change the amount and token when moving funds between account ecosystems.

Risk Management and Legal Considerations

Operating multiple exchange accounts carries significant risks that must be understood and managed. This section covers the practical risk landscape and mitigation strategies.

Detection Consequences:

If an exchange determines that you operate multiple accounts in violation of their terms of service, the consequences can be severe:

1. Account Suspension: All linked accounts may be suspended pending investigation. During the suspension, you cannot trade, withdraw, or access your funds.

2. Fund Freezing: The exchange may freeze funds in all linked accounts. Depending on the jurisdiction and the exchange's policies, this freeze can last weeks or months. In extreme cases (suspected money laundering or fraud), funds may be permanently seized.

3. KYC Blacklisting: Your identity documents may be flagged in the exchange's internal database, preventing you from creating new accounts in the future. Some exchanges share KYC blacklists through compliance networks, which could affect your ability to open accounts on other platforms.

4. Legal Action: In jurisdictions where multi-accounting violates financial regulations (not just exchange terms of service), you may face legal consequences. This is particularly relevant for accounts used for market manipulation (wash trading between your own accounts).

Risk Mitigation:

- Never conduct wash trading or market manipulation across your accounts. Beyond being detectable, it is illegal in most jurisdictions and can result in criminal charges.

- Maintain legitimate justification for each account. Personal account + business account is easily justifiable. Multiple personal accounts with no clear business purpose are harder to defend if questioned.

- Keep detailed records of each account's purpose and activity. If an account is questioned, you want to be able to explain its legitimate use case.

- Do not concentrate critical funds in a single account. If one account is suspended, your exposure is limited.

- Monitor exchange regulatory announcements. Exchanges periodically update their policies on multi-accounting, IP monitoring, and KYC requirements. Stay informed about changes that could affect your setup.

CryptoProxy's Role: CryptoProxy provides network infrastructure — dedicated mobile proxies with unique IPs per account. This infrastructure ensures that each account appears to access the exchange from a different network location, which is a fundamental requirement for maintaining account isolation. How this infrastructure is used is the customer's responsibility. CryptoProxy does not facilitate violations of exchange terms of service — it provides privacy infrastructure that has many legitimate applications, including protecting your personal IP address, maintaining geographic consistency for accounts in different jurisdictions, and ensuring network-level security.

Disclaimer: This guide is provided for informational and educational purposes. Multi-accounting on exchanges may violate the terms of service of those platforms. Users are responsible for complying with applicable laws and platform policies in their jurisdiction. CryptoProxy recommends consulting with a legal professional familiar with cryptocurrency regulations before implementing multi-account strategies.

Operational Security Checklist

Use this checklist to verify your multi-account setup is properly isolated. Review it periodically — security degrades over time as habits slip and configurations drift.

Network Isolation: - Each exchange account has a dedicated CryptoProxy mobile proxy (unique IP) - Proxy-to-account assignments are documented and never changed - Proxy credentials are stored securely (password manager, not sticky notes) - Proxy connection is verified before every exchange access session - API trading bots route through the correct proxy per account - Mobile exchange apps are proxied (OpenVPN or SOCKS5) - No exchange account has ever been accessed without its assigned proxy

Device Isolation: - Each account has a dedicated anti-detect browser profile - Browser fingerprints are unique per profile (verified at browserleaks.com) - WebRTC is disabled or masked in every profile - DNS queries route through the proxy (verified at dnsleaktest.com) - Timezone matches IP geolocation (Europe/Warsaw for Polish IPs) - No cookies or local storage leak between profiles - No clipboard data is shared between profiles

Identity Isolation: - Each account has unique KYC documents - Each account has a unique email address (different providers) - Each account has a unique phone number (different SIM cards) - Each account has unique 2FA secrets (different authenticator entries) - Account passwords are unique and stored in a password manager

Behavioral Isolation: - Accounts are accessed at different times (not sequentially) - Trading activities are diverse across accounts - No direct fund transfers between accounts - Withdrawal addresses are unique per account - Fiat payment methods are unique per account

Ongoing Maintenance: - Proxy health checked weekly (CryptoProxy dashboard) - Anti-detect browser updated to latest version monthly - Exchange security settings reviewed monthly - Login history reviewed for unexpected access - This checklist reviewed quarterly

Incident Response: - If an account receives a security alert: access ONLY from that account's profile/proxy, never from another account's environment - If an account is suspended: do NOT contact support from another account's profile or mention other accounts - If a proxy goes offline: do NOT access the account from another proxy or without a proxy — wait for the proxy to recover - Document any incidents and adjust procedures to prevent recurrence

This checklist should be treated as a living document. Update it as your operation grows, as exchange policies change, and as new detection methods emerge. The discipline to follow these procedures consistently is more important than the technical sophistication of any individual measure.